• Resolved IltikA

    (@iltika)


    WordPress 4.3.1
    Mailchimp 6.0.1
    Fresh install of the plugin (never been installed before)

    When I enter a fresh API key from Mailchimp (free account):
    We received an unexpected error: null

    Debug Log: We Received An Unexpected Error: Null Page: Settings Page/General Settings || Type: Connecting to MailChimp || Time: 2015-10-10 15:05

    Any idea on what I can do to get it to work?

    Thanks

    https://wordpress.org/plugins/yikes-inc-easy-mailchimp-extender/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Evan Herman

    (@eherman24)

    Hi IltikA,

    I’m not entirely sure. Are you using a newly generated API key? It doesn’t look like their is any error returned from MailChimp to help better understand what might be going on.

    Can you try generating a new API key, maybe the old key is expired?

    Thread Starter IltikA

    (@iltika)

    Hi,
    It is a newly generated API key,
    In fact I am also new to Mailchimp!

    Plugin Author Evan Herman

    (@eherman24)

    Hi IltikA,

    Have you set up any lists yet on your account? It’s possible API access hasn’t been granted yet, or something else is going on(.

    If you log in to your account, and go to the page that lists your API key (https://admin.mailchimp.com/account/api), just below that you’ll see a small table of API data titled: “Last 24 hours of API calls”. Do you see any errors listed there?

    Thanks,
    Evan

    Thread Starter IltikA

    (@iltika)

    I have a list created!
    And no API call logged on mail chimp.

    The log I posted on my first post is also the only log on the Plugin side!
    all the time I add more API or change it back and forth, it doesn’t even add any log like if it doesn’t even want to try to connect to it.

    Anything I can output to make it easier for you to find the issue?
    Server config or php code to temporary add to the plugin to see something?

    Thread Starter IltikA

    (@iltika)

    So the way I fixed it!
    I first deleted completely the API key that was in the field. and saved. Of course I had a error log saying I had to enter one,
    And then I added the new one and saved and it worked!

    Deleted it again, and entered the oldest API key and saved and it worked!

    At least it’s a fix, but I dunno what caused it to no work if I dont fully reset the field to nothing! Chrome autofill?

    Good luck trying to reproduce it if it’s a bug from the plugin!

    And thanks for the support

    Plugin Author Evan Herman

    (@eherman24)

    No problem and I’m glad that you were able to get things resolved. and thanks for posting a solution here!

    If you run into any other issues along the way feel free to drop us a line.

    Have a great rest of the day!
    Evan

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘We received an unexpected error: null’ is closed to new replies.