Warning messagem on 6.x-2.x-dev
dougn7 - August 24, 2009 - 18:31
| Project: | MailChimp |
| Version: | 6.x-2.x-dev |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Ive gotting a message after instal 6.x-2.x-dev:
"warning: Invalid argument supplied for foreach() in /home/acrimato/public_html/novosite/sites/default/modules/mailchimp/mailchimp.module on line 651."
Ive installing this because i did hope this version could syncronize with the acconts on my website when admin/user change/update user's information on mailchimp, but that doesnt work on either version (normal and dev). Could someone help with this? Thanks so much.
#1
Bi-directional updates, that is updating Drupal user information when the MC member is updated, is not on the road map for this module, sorry. The goal is to synchronize Drupal users with MC, not vice versa. To be honest, I'm not even sure that would be possible, since the email address is the only key to match up users.
As for the message, I'd like to know more about how to replicate that, thanks.
#2
Thanks for the fast answer. Ive got this on change "Sync Required Lists During Cron" on MailChimp Module settings page. Im sad that there isnt a way to update profile's Drupal page. Well, the way that i manage this is dont give users options to change their informations throwgh MailChimps Update Form... Thanks again =-)
#3
I had this message too, today.
I was working with mailchimp and it went offline for a while, so I guess it could be related to that...
I'm not sure though, just reporting my experience.
#4
There is a message, but the fix looks simple:
<?phpif (function_exists('token_get_list')) {
$tokens = token_get_list(array('user', 'order'));
foreach ($tokens['user'] as $token => $name) {
?>
After the $tokens = line, the foreach needs to be wrapped in an if is_array, empty, etc. check because token_get_list won't always have ['user'] set.
It's just a cleanup issue, doesn't appear to actually break anything.
#5
#6
Automatically closed -- issue fixed for 2 weeks with no activity.