Title: Error message Last modified: August 30, 2016 --- # Error message * Resolved [photopro2000](https://wordpress.org/support/users/photopro2000/) * (@photopro2000) * [10 years, 10 months ago](https://wordpress.org/support/topic/error-message-443/) * I know my wordpress version is old but my desogner claims I will break the site if I upgrade. My issue is that when I install the anti spam plugin, it won’t let me log back into my admin section. I keep getting a error message saying to turn on cookies and Javascript. Cookies and Javascript are on. What should I do? * [https://wordpress.org/plugins/wp-spamshield/](https://wordpress.org/plugins/wp-spamshield/) Viewing 4 replies - 1 through 4 (of 4 total) * Thread Starter [photopro2000](https://wordpress.org/support/users/photopro2000/) * (@photopro2000) * [10 years, 10 months ago](https://wordpress.org/support/topic/error-message-443/#post-6325184) * the actual message is ERROR: Sorry, there was an error. Please be sure JavaScript and Cookies are enabled in your browser and try again. * I did read what you wrote in the FAQ about this instance * Plugin Contributor [redsand](https://wordpress.org/support/users/redsand/) * (@redsand) * [10 years, 10 months ago](https://wordpress.org/support/topic/error-message-443/#post-6325192) * Hi photopro2000, * I’m sorry to hear about the issue you’re having and I’ll be happy to help. * That’s a very strange issue that it would lock you out of your admin. WP-SpamShield normally isn’t even active for login pages. There were a couple specific versions a while back where you might have had an issue with a third party login page, but these issues were literally patched within a day, so if your plugin is up to date, even with a third party login, you shouldn’t have any issues like this. * It’s probably going to be a several step process to fix this. First, you will need to use an FTP program or your website’s cpanel file manager. Navigate to the “/wp-content/plugins/” folder and delete the entire “/wp-spamshield/” folder. That will remove the plugin from your site, and hopefully you can log in. * After that you’ll need to reinstall the plugin through your WordPress dashboard. When you do, please take a few minutes to work through the [Troubleshooting Guide](http://www.redsandmarketing.com/plugins/wp-spamshield/#wpss_troubleshooting) and [FAQs](http://www.redsandmarketing.com/plugins/wp-spamshield/#wpss_faqs), as these solve 90% of issues users have. * Please take special note of Troubleshooting Step 9 and [FAQ #9](http://www.redsandmarketing.com/plugins/wp-spamshield/#wpss_faqs_9) as they relate specifically to the issue you are dealing with, and will give you the steps to proceed forward. * From the Troubleshooting Guide: * > _If this message comes up consistently even after JavaScript and cookies are > enabled, then there most likely is an installation problem, site configuration > issue, plugin conflict, or JavaScript conflict._ * Whenever you have a login issue like this and you’re testing things, use a second web browser – something different that what you normally use – Chrome, Firefox, IE, Opera, etc, and have your WordPress account also logged in on that second browser. That way you won’t get locked out and have to delete the plugin manually again. * If those don’t solve the issue for you, we’ll need a bit more info from you on the specifics, and we’ll need to email back and forth, so please head over to the [WP-SpamShield Support Form](http://www.redsandmarketing.com/plugins/wp-spamshield/support/), and take a moment to fill out a support request. That will allow us to take care of this as quickly as possible for you (and anyone else who is experiencing the same issue). * Just a heads up, when a designer tells you that upgrading WordPress is going to break your site, it’s time to get a new designer. That’s code for “I don’t know how the newer versions work and I don’t want to take the time to learn.” * With WordPress 4.1.5 you have a bigger issue…security. A critical zero-day exploit was discovered in all versions of WordPress 4.2 and lower. See: [https://blog.sucuri.net/2015/04/critical-persistent-xss-0day-in-wordpress.html](https://blog.sucuri.net/2015/04/critical-persistent-xss-0day-in-wordpress.html) WP-SpamShield users are protected from this specific exploit, but another flaw was discovered that was patched in 4.2.2, so it’s still important to upgrade. * Security needs to be a priority to designers, and really everyone who is involved in any aspect of a website’s production. * Just my two cents there. * Hope that helps! * – Scott * Thread Starter [photopro2000](https://wordpress.org/support/users/photopro2000/) * (@photopro2000) * [10 years, 10 months ago](https://wordpress.org/support/topic/error-message-443/#post-6325305) * Thanks for the heads up about the security flaw. I’m still having the same issue so I’m going over to support now. * Plugin Contributor [redsand](https://wordpress.org/support/users/redsand/) * (@redsand) * [10 years, 10 months ago](https://wordpress.org/support/topic/error-message-443/#post-6325310) * No problem. Sounds good. We just got it, and I’ll be responding momentarily. We’ll help you get things fixed up. Viewing 4 replies - 1 through 4 (of 4 total) The topic ‘Error message’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/wp-spamshield_08293a.svg) * [WP-SpamShield](https://wordpress.org/plugins/wp-spamshield/) * [Frequently Asked Questions](https://wordpress.org/plugins/wp-spamshield/#faq) * [Support Threads](https://wordpress.org/support/plugin/wp-spamshield/) * [Active Topics](https://wordpress.org/support/plugin/wp-spamshield/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wp-spamshield/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wp-spamshield/reviews/) ## Tags * [enable cookies](https://wordpress.org/support/topic-tag/enable-cookies/) * [javascript](https://wordpress.org/support/topic-tag/javascript/) * 4 replies * 2 participants * Last reply from: [redsand](https://wordpress.org/support/users/redsand/) * Last activity: [10 years, 10 months ago](https://wordpress.org/support/topic/error-message-443/#post-6325310) * Status: resolved