This bothers me a lot: I see no confirmation page or message after entering an email address and clicking subscribe in the Mailchimp block. Any option for the list subscription (opt-in, out-out) doesn't trigger a message for anonymous subscriber.

What am I doing wrong?

Comments

Katharine_Gates’s picture

Same problem here. As anon user I try signing up with a valid email address. The form simply returns, no confirmation message.

levelos’s picture

Assigned: Unassigned » owenpaula
Katharine_Gates’s picture

For me the Boost module seems to be part of the problem. If you are using Boost, make sure that Boost does not cache pages with Drupal messages on them.

Po3t’s picture

I have the same problem with version 7.26. There doesn't appear to be any confirmation message that tells anonymous users that they've successfully signed up and I can't even redirect users through rules or triggers to a separate confirmation page. This seems like it should be a pretty standard feature. Are we missing something here or is it really not a feature currently available?

MrPeanut’s picture

Title: Confirmation page after anonymous subscribing via block » Boost prevents message after anonymous subscribing via block
Version: 6.x-2.6 » 7.x-2.10

As Katharine_Gates mentioned, this is incompatibility with the Boost module. The Boost maintainers have committed a patch that avoids caching when there's a Drupal message: #1242416: Avoid caching Drupal messages. This works on Webform, for example, when a message appears.

However, Mailchimp's message still doesn't seem to appear.

amytswan’s picture

Issue summary: View changes
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!”