Cookie and JavaScript Error on 6 Websites

Hi @svtx

Almost 100% of reports of this type of error have nothing to do with the plugin itself, but rather are due to a site config issue or conflict.

If you’re getting the issue on 6 sites, it’s definitely not a bug in the plugin.

Step 9 in our Troubleshooting Guide covers this specific issue, and gives the steps to resolve it:

One or more users on your site consistently receive a JavaScript and cookies related error message similar to this: “Sorry, there was an error. Please enable JavaScript and Cookies in your browser and try again.” (For comments, registrations, contact forms, or anything else.)

Please see the sticky post at the top of the forum: PLEASE READ BEFORE POSTING – Updated Jan 2017. (Or you can click on the support links on the plugin’s settings page.)

If you follow those steps, well definitely be able to help you resolve the issue.

– Scott

Given you needed to add this as a frequent issue kind of tells where the problem lies, many people have this problem so perhaps it’s time to take a closer look at it. Besides, there’s no solution offered at all..

Anyway, the error is gone on all websites with the plugin disabled.

I’ll look for a different solution so you don’t have to bother with people disagreeing with you..

Given you needed to add this as a frequent issue kind of tells where the problem lies, many people have this problem so perhaps it’s time to take a closer look at it.

We work extremely hard on compatibility, and have fewer conflicts that most plugins. In almost every single case where we receive this kind of report, the user has not worked through the Troubleshooting Guide, FAQs and Known Issues. As soon as they do, the issue gets resolved.

Besides, there’s no solution offered at all..

Well, you can interpret it as you like, but there are a ton of solutions in the Troubleshooting Guide, FAQs and Known Conflicts.

For example, if you’re using a plugin that is on the known conflicts list, it’s not going to work properly. Or if your site has a configuration issue, that would cause it not to work. Unfortunately we can’t make something work if these types of issues are in place — they would cause issues with any plugin. That’s why it’s important for users to read the plugin documentation fully.

If you want help diagnosing the issue, we can likely figure out what the issue is on your site within about 10 minutes if you’d like to submit a support request. (We don’t do our tech support here at the forums, because we can offer a better, more secure experience through our site.)

I’m sorry to hear that’s your decision, but you’re obviously free to do as you like. Take care.

– Scott

@svtx, I am another user who has also experienced the same problem with multiple web sites that I manage. It is a caching problem when there is 3rd party caching software installed. In my experience it only occurs when the SpamShield plugin is updated, but in order to stay effective against Spam, the plugin is updated quite regularly and frequently.

Because the plugin relies on javascript that is called from every page with a comment form, when the plugin updates, there ends up being a conflict between the cached page and the updated script.

I have experimented with a variety of different cache settings but nothing I tried seemed to resolve the problem.

I have recently changed to a different caching plugin on all of my sites, but the problem persists. (I was using WP Super Cache but am now using WP Fastest Cache) So it really isn’t specific to any one plugin.

Here is what I have done to keep full functionality:

1) Disabled auto-updates of WP SpamShield. (I manually update instead)
2) Manually clear cache immediately after the update.

I agree with you that this is an annoyance, particularly if you have a lot of sites to manage – and I would not install the SpamShield plugin on any site that I was not maintaining on my own for that reason.

I did submit a feature request for WP Fastest Cache about a week ago asking that the developer add the ability to automatically clear the cache whenever specified plugins update — and the reply was that the feature “may” be added — so you might want to follow that as well. (See https://www.ads-software.com/support/topic/feature-request-clear-cache-with-plugin-updates/)

I think it would also be possible for the SpamShield plugin to include a function in the script that would would automatically clear the cache on a site upon activation or update to the plugin, but of course each separate common caching program would need a separate function coded. (I know that it can be done for WP Fastest Cache, as that is documented at https://www.wpfastestcache.com/tutorial/delete-the-cache-by-calling-the-function/ — but I don’t know about other caching plugins.)

So yes .. this is an annoyance — but I don’t know any other anti-spam plugin that works as consistently well as SpamShield — so it’s come down to whether it is more annoying to have to deal with manually clearing caches on upgrade, or to have to deal with manually reading and deleting all the comment spam that other plugins allow through.

Hi and thanks for tuning in. I’ve read the Troubleshooting guide too and attempted all matching solutions but to no avail..

I’m not using any caching on two of these sites (still in development) and my browser clears its cache when I close it so that can’t really be the issue here.

If you search the forums you’ll find many people have the issue and for an online shop this is one of the worst annoyances we could throw at our users so we’re just gonna move on from here, there’s too much other stuff that works without a problem.

@abigailm:
We’ve already asked you multiple times not to troll our support threads, as the advice you provide is most often incorrect and counterproductive. Given the often negative tone of your commentary, it can only be taken as trolling. If cache settings are correct, there is no issue like you describe. That only happens if your settings are incorrect. So, now for close to the tenth time, please stop trolling.

@svtx:
As already mentioned:

If you want help diagnosing the issue, we can likely figure out what the issue is on your site within about 10 minutes if you’d like to submit a support request.

Seems like everyone here has had their say and you can agree to disagree. The author has offered continued assistance if you submit a support request, for which he has provided a link. Since this conversation is no longer productive I’m closing the topic to further replies.