In my log files I see this:

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'fields, timestamp) VALUES ('subscribe', 'jp.strumane@skynet.be', 'f27aa544d7ab58' at line 1 query: INSERT INTO emf_request (type, mail, lid, fields, timestamp) VALUES ('subscribe', 'jp.strumane@skynet.be', 'f27aa544d7ab58d93a313807e10e64d1', 'a:0:{}', UNIX_TIMESTAMP()) in /var/www/html/sites/all/modules/contrib/emf/emf.db.inc op regel 45.

I have one block open for subscriptions, and in Drupal the mailing list says 26 people, while in CampaignMonitor it only says 3. So I've missed already 23 people...
Maybe (not) related: after list creation in CampaignMonitor, the name has been changed...

What else do you need from me to track this one down?

Comments

Wimmmmm’s picture

Wimmmmm commented

Aha: an error is posted on the status screen:
E-mail Marketing Framework list: List not found
Some lists could not be found on your e-mail marketing service anymore.

I've changed the name again of my public list, and after cron the modified name shows up nicely in Drupal. But still 26 people @ drupal, 3 @ CM.

Found another problem: CM has 9 lists, while Drupal holds 11 lists.
I've removed the 2 suppressed lists, ran cron again. Status warning is now gone.
I've added a new person to the public list, ran cron again: Drupal now says 27 people, CM still at 3.

??

davyvdb’s picture

davyvdb commented

Can you try delete the variable 'emf_last_sync_subscriptions' (don't forget to clear cache!) and resync? This should fetch all subscriptions.

Are you using the latest dev? Can you try that one?

Wimmmmm’s picture

Wimmmmm commented

Deleted var, cleaned cache, ran cron again.
Still lists out of sync.

Maybe we can check @ Copenhagen?

davyvdb’s picture

davyvdb commented

Sure. Let's fix this then ;)

Wimmmmm’s picture

Wimmmmm commented

Yo Davy,

apparently we didn't meet @ CPH...
Problem is still there. How could we proceed?

davyvdb’s picture

davyvdb commented
Status: Active » Fixed

Handled this offline with the reporter of the bug.

Status: Fixed » Closed (fixed)

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