Newest two versions causing major errors
-
So far I have only seen this on one client site, but the number of others who are reporting problems also has me requesting a way to turn off auto-updates for WP-Spamshield.
This is the series of errors caused by v1.9.9.8.3:
Notice: Use of undefined constant RSSD_RGX_TLD - assumed 'RSSD_RGX_TLD' in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 577 Notice: Use of undefined constant RSSD_RGX_TLD - assumed 'RSSD_RGX_TLD' in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 578 Notice: Use of undefined constant RSSD_RGX_TLD - assumed 'RSSD_RGX_TLD' in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 579 Notice: Use of undefined constant RSSD_RGX_TLD - assumed 'RSSD_RGX_TLD' in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 582 Notice: Use of undefined constant RSSD_RGX_TLD - assumed 'RSSD_RGX_TLD' in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 583 Warning: preg_match(): No ending delimiter '~' found in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 638 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 638 Warning: preg_match(): No ending delimiter '~' found in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 664 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 664This series of errors still appears even when I downgrade back to version 1.9.9.8.2, so I had to go back to 1.9.9.8 (by deleting the newer version and all its data) to get the errors to stop and be able to keep WP-Spamshield active.
Is there a way to deactivate auto-updates for WP-Spamshield?
-
Hi @fpmsummer,
Thanks for reporting this. We’ll look into it.
Just a note, the forums here are not our main support venue, and when issues are reported here, it takes longer for us to fix issues. It would be most helpful if you could submit a support request at the WP-SpamShield Support Page. Thank you.
Yes, you have full control over auto-updates. This is discussed in FAQ 16.
– Scott
PS. One recommendation is to set your PHP configuration to log errors instead of displaying them visually.
First off, please be civil. Actually, you are incorrect. Plugin developers are not under any kind of requirement to provide support, nor are we obligated to use the forums as our support venue. However, we provide some of the best tech support of any plugin out there. Our support process is precise, and allows us to get to the bottom of issues quickly.
Unfortunately lashing out at developers does not solve anything. All it does is stifle innovation. Whenever a plugin developer adds new features or classes to a plugin, there is a risk of something breaking, even with the best testing processes. Issues usually only affect a subset of sites. This issue does not affect everyone. We test on a variety of sites and setups before releasing a new version, with a number of debugging tools. No issues came up in pre-flight, so these were impossible to predict.
What we can do, is fix issues as quickly as possible. We usually fix issues within an hour or two of receiving the initial report. Few plugin developers can say that.
– Scott
Ron,
We’ve had this exact discussion a few months ago on WP Tavern. I’m not going to re-hash it again. If you would like our help, that’s great, but you need to be civil. If you don’t want our help, or don’t want to use the plugin, that is your right as well. Take care.
– Scott
Hi @fpmsummer,
Just wanted to follow up. We’re going to release a fix soon.
In the mean time there is a workaround that you will likely want to use anyway.
The error messages you’re seeing could happen from any plugin/theme/core update, so the best practice is to log errors instead of having them displayed visually. If you make a tweak to your
php.inifile, you can avoid similar issues in the future. It’s also recommended for security to not display errors.Add this to your
php.ini:custom_error_logs_path = /your/secure/path/outside/web/root/ error_reporting = E_ALL display_errors = Off display_startup_errors = Off log_errors = On error_log = ${custom_error_logs_path}/custom_error_log.log;php.inican use variables, so replace “custom_error_logs_path” in both places with your custom variable name. Replace “/your/secure/path/outside/web/root/” with a secure folder outside the web root. Replace “custom_error_log.log” with whatever you like for the error log name. This way all your logs will be combined into one, and will be inaccessible to web traffic. You’ll need to grab it by FTP or by PHP script.Hopefully this will be useful info.
– Scott
Scott, I cannot submit a report on this via the Support page form because it repeatedly tells me there is a problem with my support request.
I’ve tried about 6 times to submit this information via your support page, but even when the required fields are filled out it still says “There’s a problem with your support request”. It’s nagging me saying that I haven’t visited the Troubleshooting Guide yet and worked through that yet, and that because I haven’t it won’t accept the form.
Seriously? These errors are not errors the Troubleshooting Guide can fix. And even after “visiting the guide page”, it still won’t accept my form.
So I have no choice but to post my information here.
Seriously? These errors are not errors the Troubleshooting Guide can fix.
Please don’t assume that. We do tech support on tens of thousands of sites, and it’s not always what people think.
No matter what the issue, we’re going to have to run through those steps. (Whether it’s you doing them, or us doing them.) Please follow them. It only takes a few minutes to work through the guides.
You do have a choice. We are very good at what we do. Let us show you. ??
We’ll get you taken care of.
– Scott
- The topic ‘Newest two versions causing major errors’ is closed to new replies.
