Hi there,
I have installed the latest version of the module on a new website and I encountered the following problem. I have created a field of type Mailchimp Subscription for the user entity and selected the list that it should relate. I named the field "field_mailchimp_list".
When the user submits their profile form, the value of the field is not being saved. If the user is not subscribed to the list, she remains unsubscribed no matter if I tick the checkbox and save the form.
I tried on a clean installation, at first it had the same behavior if I remember correctly, but then I uninstalled and installed/configured again and it works ok.
So I'm trying to debug why it doesn't work on the website. Where is the value of the field actually stored? It seems that the created field table field_data_field_mailchimp_list does not hold an actual value for the field.
Any ideas?
Cheers
Comments
Comment #1
krystalcode CreditAttribution: krystalcode commentedSeems that was just the batch processing setting that was not applying the change until it was processed.
Comment #2
matt.rad CreditAttribution: matt.rad commentedI am having the same problem, but not using batch processing. Any ideas of what might be going on?
EDIT: Disregard. Working fine.
Comment #3
nerdcore CreditAttribution: nerdcore at OpenConcept Consulting Inc. commentedI am experiencing this issue using mailchimp-7.x-3.4
Any guidance on what to test would be appreciated. Thank you.
Comment #4
nerdcore CreditAttribution: nerdcore at OpenConcept Consulting Inc. commentedUpgraded to 4.7 to address the upcoming API deprecation.
Still not able to save the value of this checkbox on user/edit pages.
Comment #5
nerdcore CreditAttribution: nerdcore at OpenConcept Consulting Inc. commentedI currently have "Use batch processing." turned Off, but even when I tried turning it on, saving the Subscription setting on user/%/edit/ and running cron, nothing changed; The setting remains Off.
Comment #6
nerdcore CreditAttribution: nerdcore at OpenConcept Consulting Inc. commentedCould this be the result of having the option "Require subscribers to Double Opt-in"? This is On for the site on which I am experiencing this issue. Would the Subscribe setting not be reflected until after the opt-in process is complete?
Comment #7
ArrowYes, the subscribe setting is not reflected until the opt-in process is complete and caches have been cleared on the Drupal side. Because the value is cached, it may appear that the field is not working. See the related issue.
Comment #8
ruscoe CreditAttribution: ruscoe at ThinkShout for Mailchimp commentedIf you're using double opt-in, then @Arrow's patch linked in #7 should fix it. It's committed to the dev branch now and will be in our next release.
If you're still seeing the problem, please reopen this ticket and I'll take a look.