mc_nate

Hey again —

I have a fix for this, but I’m waiting on our QA team to give me the thumbs up before I push this live.

If you want to test the fix in your local environment, it’s a pretty simple change. On line 70, you should see a line of code that looks like this:

$body = json_decode($request['body']);

Change that line to this:

$body = json_decode($request['body'], true);

That should fix the issue. I’ll be pushing this change live later on this morning, so if you can wait or don’t feel comfortable mucking around with that MailChimp library, a fix is coming. ??

Thanks again for the helpful bug ticket you provided!

Hey Kramarz —

I’m taking a look at this right now.

Thanks for the information!

Hey again —

I’ve installed as many of those plugins as I could (some of them are premium), but I can’t get it to fail in a similar way. My guess is that there’s some sort of conflict with one of the options or maybe even a function. But, just for due diligence, could you completely uninstall the plugin and then re-install 1.5 from scratch?

I’m curious where this might be going wrong, or if it’s just an outright conflict. :\

With plugin/theme conflicts, it’s really difficult to hammer down exactly where the problem is. And if that’s the case, you may be better off going with the MailChimp for WordPress plugin that’s installed already. We’re big fans of the ibericode folks here at MailChimp HQ, anyway. ??

All that said, I’m going to leave this thread open in case others have a similar issue. Maybe we can root out a specific plugin or theme issue.

Thanks again for your patience and help this morning.

Thanks so much, Dave.

I’m having a look now. I’ll let you know what I turn up.

Hey again Dave —

Thanks for the quick reply! If you could send over the WordPress version and maybe some example plugins, that’d be great. I’ll be happy to try and set up a similar environment and see if I can replicate.

Do you have any other MailChimp plugins installed, by chance?

Hey Dave —

Can you provide any additional details? I’m happy to dig in and see what’s happening.

Hey again Chap —

It has always been a double opt-in process. There is a way you can modify that in the source code, but you’ll need to really get in there and dig around. Any change made locally will also be destroyed when the plugin is updated again (whenever that is).

That said, happy to add that as a feature request for the future!

Pushed the update this afternoon.

Please feel free to reopen this ticket if you are still seeing issues after updating!

I should probably add, you’re better off setting that field as “not required” until the update is pushed out.

Hey Chap —

Just wanted to let you know that I think we’ve got a fix in place for this. We’re testing it out right now to make sure it doesn’t break anything else in the process.

Thanks for all of the information you provided!

Yep!

It’s stored in goalwp/scripts/*. Should be the only script in there.

It looks like this was a conflict with Autoptimize.

The functionality is still there, but it looks like the scrip it minimized and kept off-site. Going to look at how to best avoid that in the future, but for now I’ll mark this as resolved. ??

Please feel free to open another ticket if you see anything else weird!

Sure. If you don’t mind emailing apiconnect [at] mailchimp [dot] com with “WordPress” in the subject line, I’ll be on the lookout.

Hey again —

For security reasons, I try to stay out of folks’ WordPress installations. But if you can re-enable that plugin and send me a link to your site, I’ll poke around the source and see what I can turn up?

Hey there —

Sorry I’m so late on this response. Can you send me a link to your site? You definitely should see the code in the page’s source view.