I have installed this module and am having difficulty understanding how to add all my existing users to mailchimp. I used to use constant contact and I have a ton of users on my website who opted into my newsletter. I created a list in mailchimp and created a matching list in drupal. However this is when I run into a myriad of errors and problems. First off, when I try to map my user fields to mailchimp custom fields drupal gives me duplicate options like "field 1" field 1" "original user - field 1". No matter which one I select I get this error when I queue existing (I am assuming this is a sync your existing users to mailchimp, but can't find any documentation on it):

Notice: Undefined index: FNAME in mailchimp_lists_load_user_mergevars() (line 759 of /home/bkwinery/public_html/sites/all/modules/mailchimp/modules/mailchimp_lists/mailchimp_lists.module).
Notice: Undefined index: FNAME in mailchimp_lists_load_user_mergevars() (line 759 of /home/bkwinery/public_html/sites/all/modules/mailchimp/modules/mailchimp_lists/mailchimp_lists.module).
Notice: Undefined index: FNAME in mailchimp_lists_load_user_mergevars() (line 759 of /home/bkwinery/public_html/sites/all/modules/mailchimp/modules/mailchimp_lists/mailchimp_lists.module).
Notice: Undefined index: FNAME in mailchimp_lists_load_user_mergevars() (line 759 of /home/bkwinery/public_html/sites/all/modules/mailchimp/modules/mailchimp_lists/mailchimp_lists.module).
Notice: Undefined index: FNAME in mailchimp_lists_load_user_mergevars() (line 759 of /home/bkwinery/public_html/sites/all/modules/mailchimp/modules/mailchimp_lists/mailchimp_lists.module).
Notice: Undefined index: FNAME in mailchimp_lists_load_user_mergevars() (line 759 of /home/bkwinery/public_html/sites/all/modules/mailchimp/modules/mailchimp_lists/mailchimp_lists.module).

I found this patch,
https://drupal.org/node/2065289
but it doesn't work on the most recent dev version, the Hunk Fails. I applied manually and it got the error above to disappear, but I don't think it fixed anything because all I got was a WSOD when the cron ran. Nothing is updating in mailchimp either so other than visibly getting rid of the error, I don't think it is doing anything.

If I don't don't add any merge fields on my list, I don't get the above error. But when I run the cron I get this:

Notice: Trying to get property of non-object in commerce_recurring_rules_provide_order_properties() (line 393 of /home/bkwinery/public_html/sites/all/modules/commerce_recurring/commerce_recurring.rules.inc).
Notice: Trying to get property of non-object in commerce_recurring_rules_provide_order_properties() (line 393 of /home/bkwinery/public_html/sites/all/modules/commerce_recurring/commerce_recurring.rules.inc).
Notice: Trying to get property of non-object in mailchimp_lists_cron() (line 166 of /home/bkwinery/public_html/sites/all/modules/mailchimp/modules/mailchimp_lists/mailchimp_lists.module).
Notice: Trying to get property of non-object in mailchimp_lists_cron() (line 166 of
......

The error is much much bigger than this. I found an old thread on this issue:
https://drupal.org/node/1195860
but the patch doesn't apply to the most recent version.

I'm totally at a loss with this module. Am I doing something completely wrong with this module? I must be because this module is funded my Mailchimp and used by over 14K people.

Other issues I have:

What is the Mailchimp Activity Entitys"? There is no documentation on what this does. Also should be "Entities" not "Entitys"

When I click on "Import mailchimp activity entity" I get a WSOD.

Any help would be greatly appreciated.

Comments

amytswan’s picture

Status: Active » Closed (won't fix)

“And now our watch [for support of the 7.x-2.x version of the MailChimp module] has ended…” With the approaching deprecation of MailChimp’s API version 2.0, I’m sad to say we too must turn the page. This branch will become unsupported in early October and officially deprecated by the end of this year (2016).

Fret not! The 7.x-4.x and 8.x versions come highly recommended. Both are using Mailchimp’s new API 3.0 and are being actively maintained. If you find this issue still exists on either the 7.x-4.x or 8.x branches, let us know by opening a new ticket. “What is dead may never die, but rises again, harder and stronger!”