Newest two versions causing major errors

Version 1.9.9.8.5 displays exactly the same error. How can we roll back to a stable, working version?

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 8 years, 1 month ago by redsand.

So my Error Log says “PHP Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /home/wine/public_html/wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665” which makes me think that the problem is in class.utils.php in your plug-in.

Is there a second explanation?

It’s not something that is affecting most sites, and isn’t a universal issue. We’ve seen a couple others, but they are on PHP 5.4 and 5.3. None yet on PHP 5.5, 5.6, or 7 yet. We haven’t been able to recreate the issue. If you submit a support request, we can get some specifics that will help us fix it faster.

– Scott

This site uses PHP 5.6.29 on Centos 6.8, Apache 2.2.15, WordPress 4.3.7

This has been stable for over a year, then blew up following the plug-in upgrade.

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.

Same error, HUGE error logs on sites, entries like:

[20-Jan-2017 06:56:06 UTC] PHP Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /[path to wp]/wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665

Sites are all running WP 4.7.1, Centos 6.8, Apache 2.4.23, PHP 5.6.28

Multiple errors per minute so error logs are HUGE)

(I’m now reviewing all sites on the server and disabling plugin wherever error log problem is showing up)

POSTING HERE SO OTHER USERS WITH SIMILAR ISSUE CAN SEE IT. (I will either roll back to earlier version of spamshield or replace with a different antispam plugin where needed, so I am reporting the issue, not seeking support at this time).

Hi @abigailm,

Thanks for providing this info.

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).

This issue is not occurring on many sites, and we are working on a fix.

If you don’t mind me asking, what company is hosting your web site?

– Steven

Please note that the WP-SpamShield Support page is our main support venue, not the WordPress forums here, so that will always be the best way to get a quick response and resolve any tech support issues. Please direct any further support questions there.

Web host is Media Temple DV using CPanel.

I don’t have time to fill in the support request form right now– I have to fix all the sites first. Rolling back to version 1.9.9.8.1 and disabling updates on all sites, so you wouldn’t be able to see the error or use any of my sites for testing purposes.

Remember when Steve Jobs told his customers that they were holding the iPhone wrong? Best thing that ever happened to Samsung. Shooting the messenger never works out very well. Code breaks, that’s a given. How a provider responds when their code breaks says a lot.

I’m just changing plugins. I don’t have time to dodge bullets.

Just an update: We have identified the issue that has been affecting some 1.9.9.8.5 users, and have been working on a fix today. We plan to release an update in the next 6 hours or so. We also have a solution for auto-updates that should make everyone happy. Stay tuned.

Update: Version 1.9.9.8.6 has been released. Issues affecting a small subset of 1.9.9.8.5 users have been resolved. An option to disable auto-updates has been added to the settings page, along with an advanced option to force-disable automatic updates and remove the option from the settings page. (This would be useful for multisite admins.) To disable auto-updates in the settings page, just uncheck the box for “Enable Automatic Updates” and click “Save Changes”. To use the advanced option, add the following code to the wp-config.php file (before it says to stop editing):

define( 'WPSS_AUTOUP_DISABLE', TRUE );

That should make everyone happy. ??

– Scott