Hi:
I am using beta 3 of this module and like it. But I noticed some odd behavior that may need to be modified to make it more useable. I have it set up to show signup box on register page, and also have the block enabled. I have a section in my profile called "personal information" in which I collect two fields (Last Name and First Name).

1. If a user checks signup during registration the email and first and last name are correctly sent to constant contact.

2. If a user does not check the signup box on registration, and subsequently goes back to the my account page to check it I see that the box shows up BOTH on the account section and under the personal information section. After checking the box, if you press save for the personal information category, nothing gets transmitted to constant contact. If you press save in the account section the email is transmitted but not the names.

I suggest the checkbox should only appear on the account view, since that is the view that needs to be saved in order to transmit to CC. In addition, the name variables are not being transmitted in this useage scenario, and I think that is probably a bug.

3. I also found the following bad useage case. Not sure how best to fix, but I report it here. User x registers and decides not to check the newsletter signup box on the registration form. A week later, user x decides he wants the newsletter, and signs up using the block. Information is correctly transmitted to Constant contact. Another week passes and user x goes into his account and updates some personal information. He does not notice that the "newsletter" checkbox is not checked (it was not changed as a result of him signing up via the block). He saves his modified profile, the unchecked box tells Constant Contact to unsubscribe him, and he is no longer a newsletter subscriber although he does not realize it and did not want that to happen.

Seems like there is some two way communication with Constant Contact required to synchronize the checkbox and the Constant contact record.

4. If I go to Constant contact and unsubscribe a user, that is not reflected in his checkbox, which continues to show "subscribed" in his account.

Comments

justphp’s picture

Hi,

Thanks for the detailed report, to answer your questions:

"2. If a user does not check the signup box on registration, and subsequently goes back to the my account page to check it I see that the box shows up BOTH on the account section and under the personal information section. After checking the box, if you press save for the personal information category, nothing gets transmitted to constant contact. If you press save in the account section the email is transmitted but not the names.

I suggest the checkbox should only appear on the account view, since that is the view that needs to be saved in order to transmit to CC. In addition, the name variables are not being transmitted in this useage scenario, and I think that is probably a bug."

I'm aware of problems on the account edit page but not sure how to fix this so may need help. The problem is the extra fields for the name etc are usually in a completely different tab to the signup checkbox and therefore a completely different form, due to the nature of drupal we have lots of different modules and methods to modify the registration form so this is something I feel that has to be improved over time. If you could let me know what module your using or how your modifying the registration form and account edit page to provide the extra fields that will be useful.

"3. I also found the following bad useage case. Not sure how best to fix, but I report it here. User x registers and decides not to check the newsletter signup box on the registration form. A week later, user x decides he wants the newsletter, and signs up using the block. Information is correctly transmitted to Constant contact. Another week passes and user x goes into his account and updates some personal information. He does not notice that the "newsletter" checkbox is not checked (it was not changed as a result of him signing up via the block). He saves his modified profile, the unchecked box tells Constant Contact to unsubscribe him, and he is no longer a newsletter subscriber although he does not realize it and did not want that to happen."

Ok thanks for reporting this, I can't say anyone else has reported this but see what you mean, this can be improved but the block and registration page methods obviously do not communicate with each other at all now, the block is so anyone can signup without an account and the registration page clearly requires an account to be created but the user is subscribed either way unless you enable double opt-in through the constant contact website (this is another issue we need to work around).

"4. If I go to Constant contact and unsubscribe a user, that is not reflected in his checkbox, which continues to show "subscribed" in his account."

This is actually quite hard to do but possible, for unsubscribed users to reflect on your drupal website we will need a scheduled script that exports all users in CSV format from the constant contact API then marks them as unsubscribed on your drupal website. I can't give an exact timeframe when this will be completed so suggest you always use the constant contact website to export your active subscribers for now.

justphp’s picture

Assigned: Unassigned » justphp
Priority: Normal » Critical
justphp’s picture

Priority: Critical » Normal
Status: Active » Needs work
entrepreneur27’s picture

With respect item 2 in post#1:
I have content profile enabled on my site. However I decided it was asking for trouble to try and use any of the fields from content profile in the constant contact signup process. So I created two new profile fields called First name and Last name in the normal core profile module. They have their own section in the core profile display called "Personal Information". This when you look at "My account" you see the "account" tab, the "personal information" tab and several other tabs created by content profile module.

My comments in the original post just apply to the fields relating to the core profile module. I do not think they are affected by the fact I am using Content profile module. But I have not tested turning that off.

justphp’s picture

Status: Needs work » Fixed

Everything here has now been fixed as of RC1 which has just been released, number 4 has not been fixed unfortunately however I've created a task so this will get done at some stage, see http://drupal.org/node/679062.

Thanks,
James

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.