You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: This bug report is for a feature that is coming soon, i.e., has not yet been released as of this writing.
Note: It is suspected that upgrading to v3 of the MailChimp API may allow this issue to be resolved; see also #311.
Steps to Reproduce
Setup MailChimp integration and Lists
Enable Auto-Confirm in dropdown , Yes, automatically auto-confirm everyone; i.e., never ask for email confirmation
Test and comment to auto-subscribe and receive the auto-confirmation email.
Unsubscribed Users cannot re-subscribe:
Click unsubscribe from the auto-confirmation email
Test and comment again with Auto-Confirm still enabled
Comment appears right away with no error prompt
No confirmation email is sent for "re-subscription" and MailChimp list will no longer add user/re-subscribe user who previously unsubscribed to the same list integrated with Comment Mail
No admin confirmation email is sent that a user has tried to subscribe and/or checked the subscription box. MailChimp Dashboard will no longer allow admin to add user/re-subscribe user who previously unsubscribed to the same List that was integrated with Comment Mail
@jaswsinc writes...
I have been unable to find a way around this problem given limitations in v2 of the MailChimp API that I have been working with. Once a user unsubscribes, the MailChimp API refuses to add them again no matter what settings I use in the API call.
Note: This bug report is for a feature that is coming soon, i.e., has not yet been released as of this writing.
Note: It is suspected that upgrading to v3 of the MailChimp API may allow this issue to be resolved; see also #311.
Steps to Reproduce
Yes, automatically auto-confirm everyone; i.e., never ask for email confirmation
Unsubscribed Users cannot re-subscribe:
@jaswsinc writes...
See also MailChimp API Upgrade Issue #311.
The text was updated successfully, but these errors were encountered: