Support » Plugin: s2Member Framework (Member Roles, Capabilities, Membership, PayPal Members) » EOT demotion doesn't always trigger removal from Mailchimp

  • Hi. This is a bit strange because usually everything works fine. But I have noticed that occasionally when members are demoted the removal from mailchimp just doesn’t happen. For example, all of my members that were demoted on May28th didn’t get removed from mailchimp. On other days it worked perfectly.

    I suspect there was just some communication error? Is there a way to force it to happen after the fact?

    Right now I find I have to manually go through all the members to make the two lists sync.

    Thanks for any help you can provide.

Viewing 7 replies - 1 through 7 (of 7 total)
  • I’d start by enabling logging to see if it shows something for MailChimp. WP Admin -> s2Member -> Log Files

    Then I’d review the settings here: WP Admin -> s2Member -> List Servers -> Automate

    Did those that weren’t removed from the list, have the same email address in MailChimp as in their WordPress profile? And were they in the list that you entered in s2Member for the level they were demoted from?

    When it happens, does it happen for everyone on the same time period, or just many of them but some get handled correctly? Where you able to reproduce this?

    Try to reproduce it. Also, if you haven’t yet, please do these:

    I hope that helps. 🙂



    Hi Christian,
    Sorry for the delay, but I had to wait for some people to be demoted.

    I found essentially nothing, but to answer your questions:

    1. I reviewed the mailchimp log. I can paste in the whole log if it would help but I found that on June 26th five people who had cancelled their subscriptions were demoted. Only two of them were removed from the mailchimp list. One of them happened at 12:48pm. The two that didn’t work should have happened at 12:48pm, but they did not happen. There is no mention of those two in the log file at all. The fourth person was demoted and removed from mailchimp at 1:01 and the last at 1:10pm.

    Is it possible that the problem is that the two that were missed had the same time stamp on them? I don’t know what I could do about that, but that’s the only suspicious thing I found.

    2. Yes, the two people who were not removed had the same email address in wordpress as they had in mailchimp.

    3. Yes, they were in the list for s2members at the “basic” membership level (it’s the only level) and were demoted to “free”.

    I really appreciate any help you can offer. Thanks.



    Sorry, three of them were removed from mailchimp and two were not.

    Did you find something in common between the ones that weren’t?

    Did you do the troubleshooting?

    You can test with 1 cent transactions, or free registrations to higher levels if you have the pro-forms.

    You can set it to 1 day to see the EOT happen sooner, or edit his profile an give him an EOT sooner, or try changing his role to demote him.



    Hi Christian,

    I wish it was feasible to test all the plugins, but there are 20 of them, and it’s a live site so I can’t just start removing stuff when people are using it. It wouldn’t work to test using the test site since it isn’t connected to mailchimp. Plus, it works half the time, so you would think if its a plugin conflict it wouldn’t work at all.

    I just had another set of demotions. There were 16 all together. 9 worked and 7 didn’t work.

    The only thing that stands out is that for every one that failed, there is one that worked at the exact same time. But then again I have 3 that worked at exactly 12:48 on the same day, so that rules out that too I think. I don’t know. It’s frustrating to have to check them all manually each time.

    Is there not some way I can force the lists to sync? Even if it doesn’t happen automatically like it should, can’t I run some kind of function to make it sync?

    What you can do to test, is create a separate clean WordPress installation in a directory, add just s2Member and configure it. Then try to reproduce the problem you’re having in the live site.

    If on the live site you can reproduce it following certain actions, but can’t on the clean installation, then start adding the other plugins one by one, testing after each.

    I wouldn’t discard a plugin conflict as a possible cause just because the problem is random.

    Talking about random, database and object caching are known to give random problems. Although I’m not sure how they’d cause the problem you’re having, it’s worth making sure you don’t have them enabled.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘EOT demotion doesn't always trigger removal from Mailchimp’ is closed to new replies.