Community Support Forums

Thanks for reporting back Ross.
~ MUCH appreciated buddy!

The issue resolved in that fix, was related to an invalid regular expression match against options configured within s2Member's UI panel for Auto-Unsubscribes. A permanent fix will be pushed out in the next release, but the patch I provided you with should resolve the problem as well, in its entirety.

Regarding the new issue you reported.

6.) Checked in Mailchimp to find the subscription to the PREMIUM list was GONE (deleted from list which is great).

7.) HOWEVER the user (now a subscriber) was not set to the FREE members list in mailchimp.

Did this person confirm the subscription to the new list yet?
Perhaps we need to NOT require a confirmation in this specific scenario?

Hi Jason,

The email account DIDN'T receive an opt in email for the NEW list that the member should be transferred to.

It would be great if there was a way to transfer them over without them having to opt in too. After all they have opted in once so I presume it should be okay to place them onto a different list when their subscription changes?

So yeah as of now, the issue seems to be that a new opt in email for the new list isn't triggered but if we could bypass that too that would be AWESOME!

Let me know what you think and if you would like me to test anything else also.

Thanks again,
Ross

I'm investigating this now Ross.

Great stuff Jason, if I can help in ANY way, let me know!

Thanks Ross. You're already a huge help. We really appreciate your assistance here in the forums. The more help we get in the forums, the more time we can devote to the next release.
~ We really appreciate your help!!

OK. Yes, this is a bug. Thank you so much for reporting this.
This does NOT affect modifications ( in the true sense of the word ), but rather, the bug here is that s2Member is not handling list server changes that occur as a result of an EOT demotion. In the current release ( i.e. s2Member v3.5.8 ), s2Member does not recognize this as a "modification" ( at least, not where list servers are concerned ). I'll have this updated in the next release though. No quick fix on this one, we'll need to rework things a bit in order to accomplish this. @TODO

Thanks for your patience.
* Again, this should only affect demotions that occur as a result of an Auto EOT being processed. s2Member WILL process list server removals, but it does not see this as a "modification", so the Member is not transferred to a new list at Level #0.

Great stuff Jason, at least we've found out what the issue is.

So I take it that modifications and list transfers WILL occur when someone uses a modification button to UPGRADE their subscription but will NOT be transferred to a new list upon demotion through a cancelled Paypal subscription and ultimately an EOT?

If I MANUALLY change someones level in the backend I presume that doesn't count either (I think I've tried it in the past)?

Lastly, do you think we'll be able to bypass the opt in for the new list that a member is transferred to.

And no worries about the help in the forums. I'll always give help where I can, you guys work so hard for us that it's the least I can do!

Yes, that's correct. This also affects manual Role changes.
~ thanks for making note of that too.

Cool, so do you think a fix may come in the next release so that users are transferred in all circumstances including EOT and manual promotion/ demotion?

No rush, I'll wait as long as it takes before I launch to have this fully operational. It's a complex plugin so I understand it may take time to get it right. Do you have an ETA of the next release?

Yes, should be end of the month.
We should be ready for beta testing around the 21st, or so.

Fantastic that ties in nicely with my timeframe for launching the new site!

Let me know as soon as you want me to test it out! I'll me more than happy to take it for a test drive!

This was included in the official release of s2Member v110605+ ( available now ).
http://wordpress.org/extend/plugins/s2member/changelog/

Hi Jason,

I've been following this thread closely, as I have the same problems that rossagrant was explaining; i.e. when a member upgrades from free subscription to level #1 using the paypal upgrade button, WP upgrades his role ok, but the communication with Mailchimp is failing. The member gets deleted from the list corresponding to free subscribers, but does not get included in the list for level#1. Other details:

- If I upgrade a user manually from WP, the same thing happens unless I check the "Re-process List Servers" box, in which case the user gets the double opt-in messages form Mailchimp and then gets included in the level#1 list (after I click on the links of the email)
- When a user subscribes to level#1 directly, everything works fine (he gets into the level#1 list)
- This is a screenshot showing my list servers config regarding double opt-in:


It looks like it's an issue related to double opt-in which is causing the problem. Do you think it can be a bug? What could I do?

I've upgraded to the latest s2member (110620) and s2member pro (110606) versions before testing the above situations.

Thank you for your help!!
Marcelo

Hi Marcelo,

Do you have the 'Allow list transitioning' box ticked in your List server settings?

I have just been playing with manually changing member roles on my site with the latest version installed and my subscribers are being moved from list to list.

@Jason
You haven't changed any code in this latest release have you Jason?

Ross

Hi Ross,

Thank you so much, that was it! It's silly, but I had just upgraded to the latest version and didn't check back these options, which have changed since the version I had before and were wrong... Now everything is working fine: manual and paypal upgrades and downgrades move users form one list to another in mailchimp.

I can't believe it, I've spent so much time on this and it was these 2 options.

Thanks for yor help!!

Marcelo

Hi Marcelo,

Really glad I could help!

It's a really powerful tool that Jason has put in for list building!
Enjoy!

Ross