I'm getting this error when a registered user tries to subscribe to a list. Unfortunately there is not much on this in the googleverse.

Comments

levelos’s picture

levelos commented
Status: Active » Closed (fixed)

Go to your list settings page and map the required merge field to a token value. If you set a field as required in MC, you must map to a token value in Drupal.

awolfey’s picture

awolfey commented
Category: bug » feature
Status: Closed (fixed) » Active

In case anyone else comes across this problem: I had the merge field mapped correctly, but the field was mapped to a newly created required profile field. Not all users, including my pre-existing test user, had a value set in this required field. So when attempting to subscribe, the pre-existing user was rejected without a user-facing message.

If you're interested in a patch that would notify a user that a required field is missing, I have some funding to work on this. If not, I'll just do my own hook_user check.

roam2345’s picture

roam2345 commented

Same issue here in 7.x version, problem for me is I have thousands of users where I am mapping first name field and last name, I cant go manually fill those fields. Watching this, is it possible to make these mapped fields optional if they are populated or not?

ryan.ryan’s picture

ryan.ryan commented
Component: Miscellaneous » General

Yea, same story here. Way to many users to manually update.

nrackleff’s picture

nrackleff commented
Issue summary: View changes
Status: Active » Closed (won't fix)

“And now our watch [for support of the 6.x version of the MailChimp module] has ended…” With the end of Drupal 6 support, I’m sad to say we too must turn the page.

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. “What is dead may never die, but rises again, harder and stronger!”