ryanhungate

@babelhalsupport are you by chance logged in as an “admin” or is it an actual customer account? If you’re an admin user it will not be tracking the carts. Can you please verify that for us?

@mouindi what version of the plugin do you have installed currently? Can you please enable the “remote support” option in the plugin and let us know your store domain when you’ve done that? We’ll see if there’s anything that pops out to assist better.

@mouindi the site requires the action scheduler to be running, which can be a little tricky in certain hosting environments. Is this a site that has a lot of live traffic? Does the site use heavy caching strategies? If so you might need to take a look at a cron scheduler to make sure the site is processing jobs the right way. It sounds as if you’ve got a situation related to caching and the scheduler not running as fast as it could be.

Please check out our github wiki for more details around the action scheduler settings.

@chvillanuevap thanks for writing in. Yes the integration should be keeping things in sync with the customer record via Mailchimp Webhooks. This is not saved on the order specifically because the subscription status is also at the “user” level. The order is a snapshot in time as they check out on your site, but the status should be updated. If you’ve found yourself in a spot where things are out of sync, you can view the user’s profile in WordPress and it should make a live request to the Mailchimp API to update any stale records you may have had.

If you have any other follow up questions please feel free to reach back out here.

@alijens honestly it’s very hard to see without a full stack trace – I totally understand what you’re saying though.

PHP versions are getting more strict. This seems like a logic bug in that code that should at minimum cast that key to a string:

return hash_equals( $this->get_order_key(), (string) $key );

Seems like a woocommerce issue, but you said when you deactivate the Mailchimp plugin, you don’t see this happen?

I know we’ve treaded pretty lightly when it comes to php versions above 7. There’s a lot of code out in the wild that will most certainly break with the strict usage it requires.

As a quick hack you can of course try what I recommended but who knows what else would break next. This is just where the logic was broken first.

Thanks, that memory limit seems very good, so I would be surprised if it’s hitting that limit. Do you happen to have any fatal logs indicating an issue that might be of help here?

Oh yeah 8GB is PLENTY… what about the PHP memory limit shown on your wordpress system report though?

@alijens can you please look at your “fatal logs” in WooCommmerce to see if anything is showing up? I would be surprised if this isn’t an “out ot memory” error. What is your current PHP memory limit set to? We’ll be glad to help you through this, obviously that’s not the desired functionality of the plugin and I’m sure we can help resolve it for you with a little effort.

@oneinamillion this function exists in wp 6.6, so if you update to that version you’ll have another fatal error trying to define the same function twice. We’ve patched the plugin to 4.3.1 yesterday that you should have been able to update and resolve that same problem the right way ??

@antonynz 4.3.1 should be ready – tested for that issue you brought up. Thanks so much for pointing that out.

@antonynz thank you for the heads up – it’s a core function that we were expecting to be there, and now that you’ve pointed that out we’re issuing a patch asap. The next one will be 4.3.1 and should be out right after a quick QA. We will report back here for you when it’s complete.

@quadlayers thanks so much for the detailed issue. This does make sense the way you describe your problem. As of now the cart record does not get deleted when an order status is pending and that’s most likely what the problem is right now. When these orders are created and not paid, is that the status they get left in? If so, there could most certainly be a solution for you:

We have a hook that gets fired during order transformation that might be of help. Inside this function, if you detect that the original woo order status is pending you might want to do something like this:

$email_hash = $order->getCustomer()->getId();
 $store_id = mailchimp_get_store_id();
 mailchimp_get_api()->deleteCartByID($store_id, $email_hash);

Before we put something in the plugin that goes out to a lot of stores, we first try to offer custom solutions to fix problems that might be specific to your use case.

Do you think something like this would work? To be able to use this custom hook for the order, right before sending it to Mailchimp, but give you the ability to delete the cart from Mailchimp so this doesn’t actually send?

Just to piggyback on what Kyle said, if you’re running into a problem and want to try to get records to sync faster, you can also use the --force option to get it to work. This is one of those situations where you might really need to consider a high performance action scheduler setup if you have lots of jobs in the queue that are not being handled properly. The documentation is on that wiki he mentioned too.

@juliemarie sorry to hear you’re having issues but it’s a little hard to know what the problem is from here. The “historical sync” you speak of is a very normal first step where you’re getting all your order and customer info into Mailchimp to be able to use this for segments and marketing etc. It’s not going to impact your site moving forward after completion, but yes we do understand it could be a little resource intense for some hosting environments. If you’ve got a large store to sync, it could be a good idea to look at your web hosting stack to see if it’s an appropriate size or if it needs to be adjusted.

The second concern seems like an email being sent from Mailchimp based on an order update? That should be something you are able to adjust inside your Mailchimp account. It sounds like you have an automation set up that you might not need?

As the plugin support side, we don’t have any insight to your Mailchimp account, but it would probably be best to reach out directly to your support while logged into your Mailchimp account and ask them to figure out which automation is firing and how to stop that. It should be a simple on/off/pause process that should fix that for you.

If we can help with anything plugin related please feel free to reach back out and we’ll be able to help.