Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
MailChimp API Errors | Event Espresso - Staging Server

Support

Home › Forums › MailChimp Integration › MailChimp API Errors

MailChimp API Errors

Posted: July 19, 2013 at 12:45 pm

Viewing 7 reply threads


Miguel Pinto

July 19, 2013 at 12:45 pm

I’m getting some integration errors after creating and assiging my MailChimp API key into the Event Espresso MailChimp plugin.

I’ve linked an event to a MailChimp list and I get the following API response errors upon attendee subscription:
(270) List_InvalidInterestGroup
(215) List_NotSubscribed
(232) Email_NotExists
The attendee contact is not submitted to my MailChimp list.
Thanks!


Jonathan Wilson

  • Support Staff

    •

July 19, 2013 at 2:18 pm

Hi Miguel,

Can you check to make sure you have no leading or trailing whitespace (spaces) in the MailChimp API key field in Event Espresso > MailChimp Settings? If there is, it could definitely cause errors.


Miguel Pinto

July 19, 2013 at 2:55 pm

Hi Jonathan,

Yes, I’ve checked that. No white spaces there. API key is clean.


Dean

  • Support Staff

    •

July 22, 2013 at 3:08 am

Hello Miguel,

What version of Event Espresso and the Mailchimp add on are you using?


Miguel Pinto

July 22, 2013 at 4:14 am

Hi, I’m using Event Espresso v3.1.33.3.P and MailChimp Integration v1.1.


Dean

  • Support Staff

    •

July 22, 2013 at 4:35 am

Hi,

Thanks, I tested those versions and found no errors. Did you set a Group correctly in Mailchimp? The (270) List_InvalidInterestGroup suggests thats where the error lies.


Miguel Pinto

July 22, 2013 at 5:14 am

Okay, I had an issue there actually. I’ve set a list but not a group in mailchimp. Now I’ve set a group within the list and it seems to be working. When I try to subscribe I get an email from mailchimp to confirm subscription. Is this something that we can override?


Dean

  • Support Staff

    •

July 22, 2013 at 5:29 am

Hi Miguel,

Glad you got that bit sorted.

The email from Mailchimp is called a double optin, and is highly recommended.

They themselves do not allow it to be turned off when using their forms – http://kb.mailchimp.com/article/can-i-shut-off-the-e-mail-that-asks-people-for-confirmation-that-they-want-

We dont as yet have an option in the Mailchimp add on to turn the double optin off, though it can be done if you modify the core code though we don’t recommend it.
Viewing 7 reply threads

The support post ‘MailChimp API Errors’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

This is the support forum for the Mailchimp integration for Event Espresso. You can get help with the add-on here from the Event Espresso team.

Status: closed

Updated by Dean 11 years, 6 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server