khungate

Hi @prettyboymp,

Thanks for the detailed report and for taking the time to dig into the code. I can see why the logic appears inverted at first glance.

This is actually intentional behavior rather than a bug. We bypass external object caching on purpose because we’ve encountered stability issues in the past with certain caching plugins (WP Rocket, for example) where cached values would persist incorrectly during specific operations, like disabling plugins in a particular order – causing our plugin to malfunction.

By reading directly from the database when external object caching is detected, we ensure we’re always working with the current, accurate option values, which is especially important for admin panel operations where configuration changes need to take effect immediately.

We understand this comes with a performance trade-off on sites running external object cache, and we appreciate you flagging it. If you’re seeing significant impact on your site, could you share a bit more about your setup? That would help us evaluate whether there’s a more targeted solution we could implement that addresses the edge cases without the broader performance cost.

Thanks again for the feedback!

Hi @inventivewebdesign, it sounds like you’re having an issue related to Mailchimp subscriptions through a WordPress plugin. The user not getting subscribed despite checking the checkbox could indeed be linked to a bug that was addressed in version 5.5.1 of the plugin.

To assist the user better, you might want to ask them the following:

1. Plugin Version: Confirm if they are using the latest version of the plugin (5.5.1). This version included bug fixes that may resolve their issue.
2. Subscription Settings: Ensure that their Mailchimp list settings are configured correctly and that all required fields are filled out in the form.
3. JavaScript Errors: Check the browser console for any JavaScript errors that might be interfering with the form submission.
4. Caching Issues: If they are using a caching plugin, suggest clearing the cache as it might prevent recent changes from reflecting.

Feel free to reach out if you need any more specific information or guidance!

Hi @pattyok, we just wanted to check back with you to see if this was still a problem with our latest plugin (v5.5.1 at the time of this post). Please let us know when you get a moment, we’ll be happy to help troubleshoot further if necessary.

Hi @walderstudio, we’re going to close out this ticket for now since it’s been a few weeks since we’ve been in touch.

Please let us know if you still need any help and we’ll be glad to reopen and troubleshoot further. Please note, that the best way to reach us is over at the GitHub plugin page: https://github.com/mailchimp/mc-woocommerce/. From there, you can receive direct responses from the development team, log new issues, download the latest version, and track existing support tickets.

Hi @apostnikov, we’re going to close out this ticket for now since it’s been a few months since we’ve been in touch.

Please let us know if you still need any help and we’ll be glad to reopen and troubleshoot further. Please note, that the best way to reach us is over at the GitHub plugin page: https://github.com/mailchimp/mc-woocommerce/. From there, you can receive direct responses from the development team, log new issues, download the latest version, and track existing support tickets.

Hi there, we’re going to close out this ticket for now since it’s been a few weeks since we’ve been in touch.

Please let us know if you still need any help and we’ll be glad to reopen and troubleshoot further. Please note, that the best way to reach us is over at the GitHub plugin page: https://github.com/mailchimp/mc-woocommerce/. From there, you can receive direct responses from the development team, log new issues, download the latest version, and track existing support tickets.

@stevkats sounds good! We’ll go ahead and close this post out for now, but feel free to reach out again if you need anything else—we’re happy to help.

Hi @espressivo, excessive webhook activity in the Mailchimp for WooCommerce plugin can occur due to several reasons, particularly when there are multiple webhooks generated from uninstalling and reinstalling the plugin. This can lead to increased traffic, especially during member updates, which can be problematic for server performance.

To address excessive webhook activity, consider the following steps:

1. Check Existing Webhooks: Review the number of webhooks currently associated with your Mailchimp list. If there are multiple webhooks, delete all of them.
2. Reinstall the Plugin: After clearing the existing webhooks, reinstall the Mailchimp for WooCommerce plugin. This should create only a single webhook, reducing excessive activity.
3. Hosting Provider Configuration: Ensure that there are no blocks placed by your hosting provider that could affect the webhook setup. If necessary, contact your hosting provider for assistance.
4. Plugin Deactivation: You may need to deactivate and then reactivate the plugin to ensure that the webhook is properly established.
5. Manage Bulk Updates: If you are performing bulk updates, consider slowing down the process or increasing your server resources to better handle the load.
6. Monitor Traffic: Keep an eye on the traffic generated by the webhooks to identify any further issues.

If problems persist, reaching out to the plugin support team for additional help is advisable.