redsand

There was a JavaScript issue in the jscripts.php file that affected certain sites. We fixed this in version 1.9.9.9.2. Updating should take care of the issue for you. I’m going to mark this thread as resolved, but if you have any further issues, please submit a support request at the official WP-SpamShield Support page, and we’ll be happy to help.

– Scott

To anyone else reading this, please ignore the advice above by @abigailm, as it is not accurate.

Please see our FAQs (esp FAQ 9) and Troubleshooting Guide (esp Step 9) as it deals specifically with JS + Cookies issues, and shows how to fix them. If those do not solve the issue for you, we can quickly help you fix things if you submit a support request at the WP-SpamShield Support Form (the plugin’s official support channel). We fix problems quickly. Thank you.

– Scott

Hi @abigailm,

As I mentioned yesterday in a different thread, I see that you responding to our reviews and support requests is becoming a regular thing, as this is the fourth or fifth time now. That’s actually not a very nice thing to do.

Again, I’m going to ask that you not jump in on our reviews and support threads to offer “support” to other users, as you’re not affiliated with the plugin, and the information you’re providing is inaccurate/confusing to other users, and contradicts our advice. You appear to have a single agenda that you want to get across, as you are being quite persistent about posting this info. To be honest, it seems a bit like trolling.

While you are correct that an uncleared cache plugin could cause an issue in some cases, it’s a bit more complex than that, and the rest of your response was not accurate, because if the cache plugin is set up correctly, manual intervention is not necessary. That’s not how recommend diagnosing things.

Also, we already have more extensive (and accurate) resources for how to deal with this specific type of issue, and resources to translate the info into different languages — that ability is not present here at the forums.

So, if you have any particular issues, please contact us directly, and we will be happy to help you. (We’ve said this before, many, many times to you.) But please don’t do it indirectly by jumping on other user’s reviews and support threads. I know you say you just want to help, but, that doesn’t seem to actually be true, as you’ve been doing it for quite a while now, you are offering contradictory advice, and are not respecting our multiple requests to stop.

Thank you.

– Scott

(To anyone else reading this, I apologize if my response to @abigailm seems less than impolite, but this is a situation with a user that we have been dealing with for quite some time now.)

Hi @timerewinder,

I’m sorry to hear you’re having this issue.

We don’t do our tech support at the forums here, so I’m going to refer you to the sticky post at the top of the forum. It provides all the info you need, including troubleshooting resources, and the link to get top-notch support from our tech support team. All of the info on our site can be translated into many languages as well, including German, so that may help. 🙂

The FAQs and Troubleshooting Guide cover what to do if you get a JavaScript and Cookies error, and how to fix it.

This issue would not have been caused by any changes in the recent update.

If those don’t take care of the issue, just follow the link to our official tech support page, and we’ll be happy to help you resolve any issues. 🙂

– Scott

@abigailm,

You’re being quite unfriendly.

I have WP Super Cache configured with default options. If there is a different set of options that should be used with SpamShield, perhaps you would be kind enough to post that information here.

If you’re having the issues that you claim to be having, then that can’t be true. We’ve been through this whole routine before though, so let’s just stop all that.

You’ve already multiple times that you don’t want to cooperate with our support process. We have an effective support process that most users absolutely love. If you don’t want to cooperate, that’s up to you.

@kennychw posted that he had tried unsuccessfully to use your site support form but experienced the same error on your site form that he say on his Contact form that I saw on several of my sites with the most recent upgrade, both with the comment function and with Contact Form 7.

The issue had nothing to do with Contact Form 7.

Your own support documents at your site reference the javascript error and advise clearing the cache.

We’ve already clarified that point for you in the past. We’re not going to keep repeating the same things over and over.

Since I spent about an hour today figuring out the most efficient way to fix the problem and complete upgrades on my sites, I shared my solution.

You could have reduced all of that to 15 minutes instead of an hour if you had simply contacted our support team. As we’ve said many times, we are happy to help you fix that.

And I subscribe to many WordPress support threads for plugins and themes that I use. You are the only developer I have encountered in the 6 years I have been using these forums that seems to have a problem with that.

Perhaps we’re the only ones that you’re trolling.

The reviews are an odd thing to subscribe to…that requires a bit of extra work.

Again, I would ask that you stop trolling, because that’s clearly all you’re doing.

– Scott

(Again, to anyone else reading this, I apologize if my reply to @abigailm seems less than cordial, but this is a user who has some history with us, and seems to only want to troll, and has been doing this for quite some time.)

Hi @kennychw,

Version 1.9.9.9.1 does not work with Contact Form 7 as it caused JavaScript errors.

I’m sorry to hear that you had this issue. However we did not change anything in this version that would cause issues for Contact Form 7. Everything is working fine with the forms on our site.

Our support system keeps detailed logs of failed support requests, and I checked these thoroughly. I did not see any support requests (failed or otherwise) from someone named Kenny in the last 24 hours. If you got blocked, it would have been for other reasons.

There was one that had over 15 attempts in a short period of time…this would be seen by the system as brute force, and blocked for a period of time. In general, if a site does not accept your submission after a 2 or 3 times, don’t keep trying, as you might get locked out. Come back later, after a few hours, and try again. Just be sure to follow the warning messages if you get one, and you should be fine.

We did see one that was blocked that used a disposable email address. Most disposable email addresses are all blocked by WP-SpamShield as they tend to be heavily used by spammers. That wouldn’t have anything to do with JavaScript though, and would not have been new to this update.

None of the support requests that came in today (or incomplete requests in the log) mentioned anything about Contact Form 7. So unfortunately, you’re not giving us much to work with here.

If you would, please visit our support page, and submit a fresh support request. I’ll be monitoring it, and if I see one come in, even if it isn’t completed, I’ll reach out and help you out.

I hope this information helps! Take care. 🙂

– Scott

Hi @abigailm,

I see that you responding to our reviews and support requests is becoming a regular thing, as this is the third or fourth time now. That’s actually not a very nice thing to do.

I’m going to ask that you not jump in on our reviews and support threads to offer “support” to other users, as you’re not affiliated with the plugin, and the information you’re providing is inaccurate/confusing to other users. You appear to have a single agenda that you want to get across, as you are being quite persistent about posting negative info. To be honest, it seems a bit like trolling.

While you are correct that an uncleared cache plugin could cause an issue, the rest of your response was not accurate, because if the cache plugin is set up correctly, manual intervention is not necessary.

One of the reasons that SpamShield is so effective against spam is that it is a blunt instrument, requiring loading of specific javascript in order for visitors to post comments or submit to comment forms.

I’m not sure why you would say this at all. To say that it is a blunt instrument is far from the truth. This plugin is quite sophisticated, and has over 100 filters.

So that eliminates most spam coming from bots.

The plugin stops 100% of spam from bots, and most spam from humans.

But the problem is that when the plugin updates, the javascript changes but the older script gets loaded from cache – and then there is a mismatch which causes the plugin to throw off that error message.

Not if your cache settings are even remotely set up properly. Most popular cache plugins, out-of-the-box would not have this issue. The only way you would have this problem is if you have your cache expiration times waaaayyyyy too long.

So basically that is something that can be fixed, but it needs to be tested with every update.

Again, I’m sorry but this simply is not accurate either. These types of statements are just plain negative, and are not helpful.

So, if you have any particular issues, please contact us directly, and we will be happy to help you. (We’ve said this before, many, many times to you.) But please don’t do it indirectly by jumping on other user’s reviews and support threads. I know you say you just want to help, but, that doesn’t seem to actually be true, as you’ve been doing it for quite a while now.

Thank you.

– Scott

(To anyone else reading this, I apologize if my response to @abigailm seems impolite, but this is a situation with a user that we have been dealing with for quite some time now.)

You’re very welcome! 🙂

Hi Joep,

I’m sorry to hear about the speed issue you’re having. I can give you some tips to help.

If you want to use Compatibility Mode, it won’t load the jscripts.php file at all.

I can give a bit of insight into potential issues that might be in play to cause this type of issue on your server.

We’ve run extensive tests on all kinds of different servers, and have never seen any kind of result with a slowdown from the plugin. Third party auditors have tested it with the same results: No speed slowdown whatsoever.

WordPress site slowdowns are most often caused by undiagnosed PHP errors, configuration issues, memory issues, database issues, missing modules, old mySQL versions, and old PHP versions.)

This is causing it. When you test with Pingdom speed test you see in the waterfall a 857ms wait time for this file. So it is slowing down my site.

I know it may seem like it, but the plugin is most likely not causing the speed issue.

In this case, it is more likely related to the server. Especially since you mentioned that you have an 875 ms wait time…the file itself isn’t loading…that’s the server being slow to respond. (Any additional file would do this.) The server may be overloaded, for one of a number of reasons. That wouldn’t be caused by the plugin though.

We find the gtmetrix.com tools to be the most helpful for analyzing page speed.

It’s good that you visited the FAQs. If you haven’t yet, you may want to check the Troubleshooting Guide as well. After that, I’d recommend you get in touch with out tech support folks, and they can help you look into the server speed issue, and help you optimize it further. (There are tests we can run to check for internal errors and such.) We’ll be happy to help you get it sorted out, and we’re fast. 🙂

– Scott