redsand

Because you didn’t follow the requirements. From the support page:

IMPORTANT: If you have a Support issue, please follow the Troubleshooting Guide and FAQ’s in the plugin documentation, before submitting a support request.

We receive many support requests that are easily solved by reading the FAQs and Troubleshooting Guide. Being that this plugin is provided free, and support is provided free on a volunteer basis, we ask that you be respectful and take a few minutes to look into the issue on your own using the resources we have provided, before you submit a support request. We are more than happy to help those who are willing to take a few minutes to help themselves.

It’s simple. You went to the FAQs page, page but didn’t work through the Troubleshooting Guide, which is required to submit a support request. Even if you don’t work through the entire guide, you just have to visit the page. Apparently that is too much work for you. Then you clicked the checkbox that says, “Yes, I have already read the plugin documentation, and worked through the Troubleshooting Guide & FAQs.” Which is a lie. The requirements are very basic, yet you’re making it out to be a huge process. Just stop. Your complaints are ridiculous. If you don’t like the plugin, then just stop using it. I have a great deal of patience, but you’re pushing it.

– Scott

• This reply was modified 9 years, 5 months ago by redsand.

Onerous? We simply ask users to work through the troubleshooting guide, the FAQs, and the Known Conflicts page. That’s pretty fair and only takes a few minutes. It gets a bit old that users complain about taking a few minutes to do some basic troubleshooting when we are going to bend over backwards to help users. We’re going to spend much more time to solve problems, so please don’t complain about taking 5 minutes.

– Scott

Thanks but in order for us to look into it, you’ll need to submit a support request, as I mentioned previously. This isn’t our main support venue. It’s very difficult to get much done from here. We’ll need to get a little more specific info that you don’t want to post here on the forums.

However I would recommend upgrading your WordPress version to the latest ASAP. WordPress has had some significant code changes in the last year. The 4.4, 4.5, 4.6, and 4.7 branches have added new functions, changes, features, etc.

Hi @jhkoenig,

If you’re having issues after the last update, we’ll need you to submit a support request at the WP-SpamShield Support Page (the plugin’s main support venue).

Also, you will want to change the error display setting on your site to hide them instead.

The error messages you’re seeing could happen from any plugin/theme/core update or PHP error so the best practice is to log errors instead of having them displayed visually. At the very least you want to hide them. If you make a tweak to your php.ini file, you can avoid similar issues in the future. It’s also recommended for security to not display errors.

Add this to your site’s php.ini file (if it has one):

error_reporting = 0
display_errors = 0

If these variables already exist, just replace their value with these.

Another option is to add the following lines to your wp-config.php file:

@ini_set( 'display_errors', 0 );
@error_reporting( 0 );

Just be sure to place that before the line that says, “That’s all, stop editing! Happy blogging.”. php.ini is the better option. Whichever you edit, just be sure to make a backup of the file first, to be safe.

Hopefully this will be useful info.

– Scott

• This reply was modified 9 years, 5 months ago by redsand.

Update: Version 1.9.9.8.5 has been released with the fix.

Update: Version 1.9.9.8.5 has been released with the fix.

Hi @t2m,

I’m sorry to hear about the issue you’re having. There is an issue that we’re currently working on fixing, but it should not cause a white screen of death. If you’re having that happen, it’s likely something more specific to your site. If can submit a support request at the WP-SpamShield Support Page, it will help us fix this more quickly. If you wouldn’t mind, please work through the Troubleshooting Guide first to make sure that there isn’t a known conflict or issue.

– Scott