S2 transitioning to new Mailchimp list but not removing old!

[rossagrant]

Hi Jason,

I've noticed something new which you might want to take a look at.

List transitioning is playing up a tad in the latest version of S2 member v111105, and I've tested it on 2 seperate installs now with the same result.

When manually transitioning members from the backend in WP, a member does indeed get placed on the new Mail Chimplist for the new S2 level, but they DON'T get removed from the old list.

Could you guys test this out too and see if you get the same result.

Perhaps MC's API has changed a litttle, or S2 has changed in recent upgrades?

Ross


ALSO - Plugin conflict you might want to be aware of.


Just been testing some stuff out on my site and I've come up with a little confliction between the lister server setting in S@ and a plugin called Chimp Express. http://www.chimpexpress.com/

It appears with the CE plugin installed Mailchimp will not re=process the list server invites through the backend of WP or reassign list transitions.

No idea why but there is obviously a confliction there.

Deactivating CE doesn't help either, you have to delete it and remove the orphaned DB entries from WP_Options too.

Thought you might like to know just incase others are using this plugin and come across issues.

Hope you are well!

Ross

[rossagrant]

Duplicate post

[rossagrant]

Just bumping this as I've updated the issue above.

[cwiler]

I have no idea if this falls in the same category/issue....but I don't have that specific plugin installed, I just use the HTML coding from Mailchimp as a quick sign up on my home page....However, when I install the S2member plugin the function stops working. It appears to add the user and says a validation email is being sent however, none is ever sent...UNTIL...I deactivate the S2Member plugin and try to sign up again. Then I get hit with all the back verification emails that it seemed to be "holding".

[rossagrant]

Hmm... not sure but I think other plugins that use your Mailchimp API key might conflict. Is it possible to create 2 separate API keys in Mailchimp?

Perhaps using a different key for each plugin might stop the confliction?

[cwiler]

Hmmm...well I had no idea so I went to my Mailchimp acct and you can certainly create your API keys and it appears you can create multiple ones. I didn't have any created at all. Apparently with using the HTML code and inserting that into a widget I didn't need one?

[rossagrant]

You only need your API key so that S2Member can communicate with your list servers at Mailchimp. You set this up under the API/ Lister server options in S2 member.

If you are not allowing S2 member to deal with your sign ups for Mailchimp, you don't need to bother with your API key.

Your issue may be caused by a conflict with the HTMl code somewhere.

Not too sure, I'm sure Jason can shed more light on this I hope.

[cwiler]

Ahh...I haven't set up anything with S2Member yet. I didn't want to spend the time if it was going to conflict with my site. So right now it's just an active plugin that doesn't allow that Mailchimp code to work.

[Jason Caldwell]

@Ross. MailChimp log files requested via email.
We'll update this thread with any important discoveries.

[rossagrant]

Thanks Jason,

Logs just sent and I may have identified the issue, but not sure!

Thanks again!

Ross

[Jason Caldwell]

Hi Ross. Thank you. Your email was received, and I'll await your reply.
Note. The issue you were referring to is intentional. This is correct in your log file:

Code: Select all

'api_removal_delete_member' => false,

s2Member does not delete them, it only unsubscribes them.
See: http://apidocs.mailchimp.com/api/1.3/li ... e.func.php

[rossagrant]

Thanks for the reply Jason and patch. I've tried to implement it but am getting a server error.

Have dropped you an email, so we can get to the bottom of it!

Thanks,

Ross

[rossagrant]

Hi Jason,

I've upgraded my test server to WP 3.3

The issue still remains unfortunately and this is on a different server to my production site where the issue is the same.

I've just emailed you new logs which might have processed Gzip properly this time to give us more of a clue.

The WP admin bar issue in my other post seems to resolve in WP 3.3, so there must be a conflict in the old version somewhere.

Problem is, I can't upgrade the production site til January I don't think, so could still do with fixing that if there is anything you could suggest?

thanks buddy!

Ross

[Jason Caldwell]

Hi Ross. Sorry for the delayed response.
I just replied to your previous email. However, I did not receive any additional log files. Can you please send those over again for review? Regarding the server error when implementing the WordPress v3.3 patch... it sounds like you might have missed a curly bracket.

In WordPress v3.2.1, open this file:
/wp-includes/class-http.php
At line #1638, find this function:

Code: Select all

    function compatible_gzinflate($gzData) {
        if ( substr($gzData, 0, 3) == "\x1f\x8b\x08" ) {
            $i = 10;
            $flg = ord( substr($gzData, 3, 1) );
            if ( $flg > 0 ) {
                if ( $flg & 4 ) {
                    list($xlen) = unpack('v', substr($gzData, $i, 2) );
                    $i = $i + 2 + $xlen;
                }
                if ( $flg & 8 )
                    $i = strpos($gzData, "\0", $i) + 1;
                if ( $flg & 16 )
                    $i = strpos($gzData, "\0", $i) + 1;
                if ( $flg & 2 )
                    $i = $i + 2;
            }
            return gzinflate( substr($gzData, $i, -8) );
        } else {
            return false;
        }
    } 

Replace this with the WordPress v3.3 version, which is coming soon.

Code: Select all

    function compatible_gzinflate($gzData) {

        // Compressed data might contain a full header, if so strip it for gzinflate()
        if ( substr($gzData, 0, 3) == "\x1f\x8b\x08" ) {
            $i = 10;
            $flg = ord( substr($gzData, 3, 1) );
            if ( $flg > 0 ) {
                if ( $flg & 4 ) {
                    list($xlen) = unpack('v', substr($gzData, $i, 2) );
                    $i = $i + 2 + $xlen;
                }
                if ( $flg & 8 )
                    $i = strpos($gzData, "\0", $i) + 1;
                if ( $flg & 16 )
                    $i = strpos($gzData, "\0", $i) + 1;
                if ( $flg & 2 )
                    $i = $i + 2;
            }
            $decompressed = @gzinflate( substr($gzData, $i, -8) );
            if ( false !== $decompressed )
                return $decompressed;
        }
    } 

[Jason Caldwell]

The WP admin bar issue in my other post seems to resolve in WP 3.3, so there must be a conflict in the old version somewhere.

I'll address this in our other post. See: viewtopic.php?f=4&t=16243&p=56443#p56443

[rossagrant]

Just sent you the MC logs from my WP 3.3 install with BP 1.5.2

Still experiencing this issue and no idea why.

cURL and F Open tests pass fine, it's worked in the past too.

I did have an issue with the list servers processing whilst I had another MC plugin installed.

I uninstalled it, and they went away. i wonder if anything was left behind that could cause an issue.

Let me know if you spot anything in my logs.

Cheers Jason!

[Jason Caldwell]

Hi Ross.

The last two entries in your log file, indicate a demotion from Level #1 back down to Subscriber as you explained. So this tells me that s2Member is working properly. I just ran through your list of actions in an effort to reproduce this, but everything worked properly. I tested against WordPress v3.3 with s2Member v111206.

Do you have any other plugins running that interface with MailChimp's API. Or any 3rd-party services interfacing with MailChimp?

[rossagrant]

Jason,

I AM AN IDIOT!

There is NOTHING wrong with S2 or my install, just me being really stupid.

It seems MC has changed the way it stores it's history of unsubscribed users.

Even when a user has unsubscribed from a list, he/ she will still be kept within the list, but at the bottom, under 'unsubscribed', thus when I was searching to see if the user remained on the list, they still show, but obviously under 'unsubscribed'.

I hadn't noticed this and presumed they were still on the active section of the list.

I am so sorry to have taken up your time, and once again really appreciate the support you have put in here yet again.

Can't apologise enough!

At least we got to the bottom of it though, and nothing was actually wrong.

Thanks again mate!

Ross

[Cristián Lávaque]

Thanks for reporting back, Ross! I'm glad you figured it out.