Thaddeous

I’ve solved this on my own by deleting the old key and generating a new one… thx

Solved

Nice. That was happening in the functions.php file. I’ve combined the action and am calling it once. Fixed. Thanks!

Hello. When is the next release? Still getting fatal error.

7.3

I should also add that we don’t use your image compression or cacheing. It’s all turned off.

Hello. Does the latest release (v 5.128.1) include the supposed fix to this issue (without having to uninstall/reinstall/reconfigure)? The changelog states that it is, but I am just ensuring so as you stated above that this particular fix wouldn’t be released until next week. Please clarify. Thank you.

Hello. Is there no other way around this? We’re using this plugin on over 20 websites… This method will take me an inordinate amount of time to update all.

We ARE using the latest version. And the static key for JS is and has been set to auto… yet still same issue. You have multiple people complaining about this exact issue. Why is this not fixed? We are losing registrations every day, and are a paying customer. This is not acceptable.

Hello? Does the new update fix this issue? The changelog doesn’t seem to address this issue. We are losing multiple registrations every day… Please respond.

Weird. I was never notified of this reply.

MailChimp for WooCommerce: Version 2.1.8
WooCommerce: Version 3.4.3

They are both up to date and have been… =/

Is there any update to this? I used to use WPML but now do not. I also have no duplicated/translated SKUS in the DB? AND my SKUS start with an alpha character (example: FPC-0601). But yeah… anytime I try and save a product I get the error: “Invalid or duplicate SKU”.

Awesome. The issues is fixed. Also, that line I added to my config file shaved 1.2 seconds off my load time (according to GTmetrix).

Thanks for the help.

1) I reactivated the plugin and took a screenshot of the error for you…

2) If I add the recommended snippet to my config file… how does this affect the internal AJAX setting that reads: “Use AJAX for Javascript Check – Option helps protect WordPress against spam with any caching plugins. Turn this option on to avoid issues with caching plugins.” Will I still be protected? Does the snippet render this setting useless? I don’t use caching plugins, but my host (WPEngine) does a ton of cacheing automatically. Please explain and advise. Screenshot attached below.

Hello.

1) I upgraded to the latest version and the problem still persists.

2) I am not quite sure what you mean when you say: “Different themes use different mechanisms of loading, so we use two methods for loading our script”

If I am not wanting to use Ajax, and just want the script to load after all other scripts in my footer alone – what do I do? I referenced you FAQ and didn’t find this answer… Please explain.