If a user subscribes from EMF to a list and he or someone else unsubscribes from both MailChimp and drupal, the tables get out of sync.
The other way around the same problem arises.

Because the subscribe/unsubscribe returns an error from the MailChimp-API(the user already exists or already was removed), the requests are 'hanging' in the emf_requests table.
On a unsubscribe, the mailaddress isn't removed from the EMF_subscription table and the user cannot subscribe again (this could very well be the same issue as #867862: When removing an email address in CM, how can the authenticated user subscribe again?).

In the next comment a patch is added that fixes this problem for the MailChimp API plugin.

CommentFileSizeAuthor
#2 1049798-mailchimp_api-check-2.patch3.48 KBMaxWesten
#1 1049798-mailchimp_api-check-1.patch2.93 KBMaxWesten

Comments

MaxWesten’s picture

MaxWesten commented
Status: Active » Needs review
StatusFileSize
new 1049798-mailchimp_api-check-1.patch2.93 KB

The patch that fixes this issue (at least for me).

MaxWesten’s picture

MaxWesten commented
StatusFileSize
new 1049798-mailchimp_api-check-2.patch3.48 KB

There were some circumstances that generated errors in the watchlog. These are fixed in this new patch.

cyberwolf’s picture

cyberwolf commented

I think this gets solved by #1145704: Failing sync. requests are never cleaned as well. Anyone who can verify this?

pbuyle’s picture

pbuyle commented

I didn't test it with MailChimp but yes, this is the same kind of use case that led to #1145704: Failing sync. requests are never cleaned and its solution.