Title: Newest two versions causing major errors Last modified: January 18, 2017 --- # Newest two versions causing major errors * Resolved [Summer](https://wordpress.org/support/users/fpmsummer/) * (@fpmsummer) * [9 years, 4 months ago](https://wordpress.org/support/topic/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 664 ``` * This 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? Viewing 15 replies - 1 through 15 (of 27 total) 1 [2](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/page/2/?output_format=md) [→](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/page/2/?output_format=md) * Plugin Contributor [redsand](https://wordpress.org/support/users/redsand/) * (@redsand) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8670826) * Hi [@fpmsummer](https://wordpress.org/support/users/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](https://www.redsandmarketing.com/plugins/wp-spamshield/support/). Thank you. * Yes, you have full control over auto-updates. This is discussed in [FAQ 16](https://www.redsandmarketing.com/plugins/wp-spamshield/faqs/?faqs=16#faqs_16). * – Scott * PS. One recommendation is to set your PHP configuration to log errors instead of displaying them visually. - This reply was modified 9 years, 4 months ago by [redsand](https://wordpress.org/support/users/redsand/). * [comfortking](https://wordpress.org/support/users/comfortking/) * (@comfortking) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8670938) * Makes no difference if this is your “main support area” or not. WordPress has made it clear that if you want to host a free plugin on their site you MUST make their Support Forum available. * You have single handedly bricked thousands (? – maybe more?) of sites with one auto-update screwup. We lost 5 this morning. Your plugin is now history and dead to me forever. * We’re well past “we’ll look into it” stage. It’s time for the “begging for forgiveness and here’s what we’ve done to make sure this NEVER happens again” stage. * Plugin Contributor [redsand](https://wordpress.org/support/users/redsand/) * (@redsand) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8670980) * [@comfortking](https://wordpress.org/support/users/comfortking/), * 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 - This reply was modified 9 years, 4 months ago by [redsand](https://wordpress.org/support/users/redsand/). * [comfortking](https://wordpress.org/support/users/comfortking/) * (@comfortking) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8671028) * Great to see you’re manning up and taking full responsibility for your own actions Scott. /sarcasm * Blame it on whatever you want – your plugin bricked 5 of my BOSSES sites this morning. I don’t get to blame you. I took full responsibility for it myself with him which was not pretty. You should try it sometime. * Plugin Contributor [redsand](https://wordpress.org/support/users/redsand/) * (@redsand) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8671118) * [@comfortking](https://wordpress.org/support/users/comfortking/), * Tech support isn’t about placing blame, it’s about _fixing issues_. If you would like help resolving issues, _we are happy to provide it_. * I would say that we always do take full responsibility. If we cause an issue, we fix it as fast as humanly possible. I’m not sure what else you could ask for. It’s a free open source plugin. If you compare our response times to other plugin developers, we’re one of the fastest by far. * If you ever have an issue with the plugin, all you need to do is submit a support request, and we will always help fix the issue quickly. * – Scott * [comfortking](https://wordpress.org/support/users/comfortking/) * (@comfortking) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8671149) * And this is the very attitude that pisses me off about “free” plugin authors. * The “it’s free so shutup” attitude is exactly what is stifling WP development the most. You have a choice – support it or don’t. Charge or don’t. Update it or don’t. Give a crap – or don’t. * Don’t shove the “it’s free” attitude in everyone’s face. This is *exactly* why I’ve all but eliminated free plugins in favor of paid. Yours is the latest. I don’t need any of your help now or in the future. Thanks for making it an easy decision. * Plugin Contributor [redsand](https://wordpress.org/support/users/redsand/) * (@redsand) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8671187) * Ron, * We’ve had this exact discussion[ a few months ago on WP Tavern](https://wptavern.com/contact-form-7-passes-40-million-downloads#comment-190355). 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 - This reply was modified 9 years, 4 months ago by [redsand](https://wordpress.org/support/users/redsand/). - This reply was modified 9 years, 4 months ago by [redsand](https://wordpress.org/support/users/redsand/). * Plugin Contributor [redsand](https://wordpress.org/support/users/redsand/) * (@redsand) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8671333) * Hi [@fpmsummer](https://wordpress.org/support/users/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.ini` file, 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.ini` can 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 - This reply was modified 9 years, 4 months ago by [redsand](https://wordpress.org/support/users/redsand/). * Plugin Contributor [redsand](https://wordpress.org/support/users/redsand/) * (@redsand) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8671532) * Update: Version 1.9.9.8.4 has been released with the fix. Everything is working fine now. Please see the changelog for details. * Thread Starter [Summer](https://wordpress.org/support/users/fpmsummer/) * (@fpmsummer) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8671557) * Alas, this newest version, 1.9.9.8.4, now causes MORE errors. * ``` Warning: preg_match(): No ending delimiter '~' found in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): No ending delimiter '~' found in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): No ending delimiter '~' found in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): No ending delimiter '~' found in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): No ending delimiter '~' found in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639 Warning: preg_match(): No ending delimiter '~' found in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): No ending delimiter '~' found in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): No ending delimiter '~' found in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): No ending delimiter '~' found in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): No ending delimiter '~' found in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665 ``` * Plugin Contributor [redsand](https://wordpress.org/support/users/redsand/) * (@redsand) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8671590) * Hi [@fpmsummer](https://wordpress.org/support/users/fpmsummer/), * In my first response, I asked that you submit a support request at the [WP-SpamShield Support Page](https://www.redsandmarketing.com/plugins/wp-spamshield/support/). If you don’t do that, then it makes it tough to solve issues. There is a specific issue on your site that is not on every site, and to get to the bottom of it we need specific info. * if you go ahead and submit the support request, we can resolve issues quickly. * – Scott * Thread Starter [Summer](https://wordpress.org/support/users/fpmsummer/) * (@fpmsummer) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8671611) * 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. - This reply was modified 9 years, 4 months ago by [Summer](https://wordpress.org/support/users/fpmsummer/). * Plugin Contributor [redsand](https://wordpress.org/support/users/redsand/) * (@redsand) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8671639) * > 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 - This reply was modified 9 years, 4 months ago by [redsand](https://wordpress.org/support/users/redsand/). * Plugin Contributor [redsand](https://wordpress.org/support/users/redsand/) * (@redsand) * [9 years, 4 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8671708) * Hi [@fpmsummer](https://wordpress.org/support/users/fpmsummer/), * We dug through our site’s logs and found your raw POST request info. I’ve asked Steven to email you so please check your email. Be assured, we’re going to help you with this issue. * – Scott * Plugin Contributor [redsand](https://wordpress.org/support/users/redsand/) * (@redsand) * [9 years, 3 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/#post-8675781) * Update: Version 1.9.9.8.5 has been released with the fix. Viewing 15 replies - 1 through 15 (of 27 total) 1 [2](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/page/2/?output_format=md) [→](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/page/2/?output_format=md) The topic ‘Newest two versions causing major errors’ 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/) * 27 replies * 6 participants * Last reply from: [redsand](https://wordpress.org/support/users/redsand/) * Last activity: [9 years, 3 months ago](https://wordpress.org/support/topic/newest-two-versions-causing-major-errors/page/2/#post-8681926) * Status: resolved