• Resolved philcheese

    (@philcheese)


    This morning I’ve come back to a site I’ve been putting together which uses your plugin to sign people up to a Mailchimp mailing list. I’ve apparently made changes in the wrong order as:

    1. When I swapped an API key out I forgot that a pre-built form was associated with a list on a different key. This caused the form to break so that I couldn’t edit it. I didn’t realise there was a clear API cache function, I imagined this would be done automatically when an API key change was detected. I mean why wouldn’t you? The exact list is not going to exist on the new key.
    2. When I created a new form, it had no form tag *until* I set a form property, then it rendered the form tag.
    3. Now the plugin won’t set the submit button text.

    All a bit wobbly if you ask me.

    Thanks,

    Phil.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor yikesitskevin

    (@yikesitskevin)

    Hi @philcheese,

    1. We’re aware that the API cache is not being cleared when a new API key is entered. This should be fix with the next release.

    2. I am not sure what you mean. Do you mean the form didn’t have a field until you manually added one? If so, that is just how it works.

    3. What is happening with the submit button text? Is it being saved properly but then reverting later on?

    Let me know,
    Kevin.

    Plugin Contributor Tracy Levesque

    (@liljimmi)

    🏳️‍🌈 YIKES, Inc. Co-Owner

    Hi @philcheese,

    Are you able to answer any of Kevin’s questions above?

    Let us know.

    Thank you!
    -Tracy

    Plugin Contributor Tracy Levesque

    (@liljimmi)

    🏳️‍🌈 YIKES, Inc. Co-Owner

    Hi. @philcheese,
    We haven’t heard back from you in awhile, so I am going to close out this ticket.

    If you need further help, please reopen it and we will be happy to help you.

    Thank you!
    -Tracy

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Three plugin bugs’ is closed to new replies.