Closed (fixed)
Project:
Mass Contact
Version:
5.x-2.1
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
9 Aug 2007 at 03:01 UTC
Updated:
8 Mar 2008 at 01:51 UTC
I've been using 5.x-1.x and recently updated to 5.x-2.1 and have found that every account that was originally opted-in to accept group email is now reset and opted-out. I don't know if this is a bug, by design or if there is a configuration problem with my site.
On the site I'm running, all accounts are created manually and group email is opt-in by default. Once the user logs in, they can then choose to opt-out of group email. They way it is now, all previously created accounts will be opted-out unless they comeback and opt-in.
Comments
Comment #1
oadaeh commentedIt's possible I might have caused this by accidentally removing the option: http://drupal.org/node/165910. I will look into it as soon as I can.
Comment #2
b.hughes commentedI don't think it's because the option isn't there. I'm looking at the code for the function mass_contact_user and it looks like you changed the variable from "mass_contact_optout" to "mass_contact_accept" in version 5.x-2.1
The problem with this is that once I installed version 2, no account had this variable set. This makes everyone who had previously accepted email by default, now has to manually accept. Everyone who had opted out won't have to do anything but everyone who didn't optout (default opt-in) will have to opt-in.
I think I read an old post where you stated your intention to change the code to make it default opt-out. While I agree with your thinking, you need to create an install updater function that transfers the previous users intended preference from the old variable to the new variable.
Of course, I could be wrong.
Comment #3
oadaeh commentedI did some investigating, and what happened is that I started coding from the head of 5.x-1.x, but the code for 5.x-1.5 was not there. What I ended up doing was reverting the 5.x feature set then start adding new on from there. What I'm going to have to do is upgrade the 5.x-1.x head to match 5.v-1.5 and then re-do the bug fixes and feature add-ons for 5.x-2.x. Oye.
Comment #4
oadaeh commentedI've re-added the feature with the 5.x-2.2 release. Test it out and let me know if it corrects your problem.
Comment #5
oadaeh commentedComment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.