Hi, I have a strange problem. I've looked through the issues but couldn't find anything similar. If this has been answered already, would appreciate it very much if you could point me to the right direction.
I inherited a site with 2 MC lists (not groups). The setup is that one list should show up in certain content areas and another in other content areas. So say, I subscribe to list A, I get subscribed properly. Now, if I go to a page with a subscription block for list B and I subscribe to that one too, what happens is, I get unsubscribed from list A and subscribed to list B (and vice versa). Now, if I'm subscribed to both lists and I unsubscribe from one of them using their specific block, I get unsubscribed from both lists. :o
BUT if I go to the subscription page which lists all my MC newsletters, I can un/subscribe to both with no problems -- one at a time or all at a time.
Afaik, we're using the MC module out of the box and no alterations have been made. I don't mind making changes to the code (to make it work, as we have a deadline for this project) but I was wondering if this is something that has been fixed already or if it is something peculiar to my setup alone.
Any help would be appreciated. Thank you!
Comments
Comment #1
tanjerine CreditAttribution: tanjerine commentedHunting down the problem some...
Under the function mailchimp_subscribe_auth_form_submit, there's a line inside a foreach ($lists as $list) loop:
So for list A and B, if you were subscribing to list A using the block created by the module (a block with a single list item), the module loops over the entire array of lists that are available for your particular account and for whichever lists aren't selected (in this case, list B), the account gets unsubscribed from assuming you were subscribed to them in the first place.
So my question (which I'm trying to figure out) is -- if you're on a block for a single list you should be able to subscribe/unsubscribe to that list _alone_ without affecting your subscriptions to other lists. So what should we check for?
Hope this makes sense.
Comment #2
tanjerine CreditAttribution: tanjerine commentedOkay, here's how I fixed my problem. This could be the wrong way to go about it, though. But it seems to work for me. Here's my updated code for the mailchimp.module
Comment #3
levelos CreditAttribution: levelos commentedThis was just fixed in http://drupal.org/cvs?commit=452678. Thanks for the help, I ended up taking a different approach which is more robust.
Comment #4
tanjerine CreditAttribution: tanjerine commentedThank you so much! :)