-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MailChimp transition affects non-s2 Interest Groups #757
Comments
Oh, a point of clarification: "Free Subscriber," "One Week Pass," "Premium Monthly Subscriber," "Premium Full Year Pass," "Administrator," and "pending" are s2/WordPress member labels. "newsletter" and "raffle" are not, nor are they CCAP labels. They are completely independent of the membership site, but otherwise related to the business. |
@bobeaston Thanks for the feature request :-) If I understand correctly, the issue is that there are Interest Groups that s2Member is unaware of, and so whenever a transition occurs, the Interest Groups that s2Member is unaware of are being removed in favor of only those which are listed in your MailChimp configuration for s2Member. Is that about right? The MailChimp API has a I take it that you cannot just give s2Member the additional Interest Groups in your configuration due to those being managed elsewhere. Do I have that right? I suppose a possible short-term solution would be to filter this setting in s2Member. I'm not entirely sure that will resolve the problem for you though. See: this line of code. To filter that setting off, create this directory and file:
<?php
add_filter('ws_plugin__s2member_mailchimp_replace_interests', '__return_false'); |
Yes Jason, you understand the problem correctly. The "Acnathus Book" group values are being cleared whenever s2Member updates that list members s2Member values. I'll try your suggestion and let you know. THANKS! |
Unfortunately... it still fails. I too thought that was the parameter causing problems and even modified s2Member code before you suggested the filter. No joy! However, don't lose any sleep over it. I think this is about my "last straw" with MailChinp. Don't get me wrong; it's not you. It's them. I find almost all of their processes rich with cuteness while being incredibly obtuse. Maybe one of their chimps wrote the documentation? :) I'm ready to switch to ConvertKit, even if it means writing my own hooks to s2Member. Thanks for taking a look and for the suggestion. |
Ah, bummer. Thanks for the follow-up! :-) I'll leave this issue open and perhaps we can take a closer look and try to improve upon this at some point in the near future. |
THANKS Jason! On Tue, Oct 27, 2015 at 1:48 AM, JasWSInc notifications@github.com wrote:
|
Just an update: I've been retracing previous steps to double check... Test method: First, an explanation from a person at MailChimp support: I re-tried the MU filter suggested above - same failure. On grepping all of s2member, I found 4 files that affect "replace_interests". I changed true to false in all of them as follows: (filename - line number(s) - change) Next, I'll inspect for possible "default to true" cases. |
Yet another test ... conducted exactly as above, with all of those "false" values still in place. I turned on logging for the duration of this single transaction. I changed the user known as "s2free" from "Free Member" to "One Week Pass" and then collected the mailchimp.api log file. The only mention of "replace_interests" in the log file is in what I believe is the return results from MailChimp, which shows no value for api_replace_interests. Log file:
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
) LOG ENTRY: Sun Nov 15th, 2015 @ precisely 1:02 pm UTC
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
RECURSION
) ---- Log file END ---- |
OK. Now, I see what is happening. It has NOTHING to do with the "replace_interests" setting. When a member transitions between membership levels, s2member handles the MailChimp change in two steps: The UNSUBSCRIBE is the root of this problem. I understand why s2member did it that way, and I also understand that transforming these two transactions into one update transaction is not trivial. Now that I understand why/how it is happening, I'll come up with another strategy for dealing with the additional interest group information I wanted to keep on the same list. It actually means maintaining a separate list for that information, and additional cost at MailChimp. |
Ah, that makes sense. Thanks for pointing that out! |
My MailChimp list has an Interest Group, "Member Level," for s2 member membership levels. s2member is configured to transition levels as people move from level to level. That works GREAT. Thank you!
However, I have another Interest Group in my list, "Acanthus Book," (and more to come). Values in that group get reset when transitions occur. Not good!
The two groups look like this:
I would like the s2 transitions to continue happening, but without touching the "Acanthus Book" group.
Yes, I suspect you might advise separating the two groups into separate lists, which is what we have now. However, there's about 80% overlap in members on those lists, inflating the number of MailChimp subscribers, and also defeating the oft recommended concept of having only one list for a business.
The text was updated successfully, but these errors were encountered: