Support » Plugin: WP-SpamShield » Too many warning in error log!

  • Resolved Salvatore

    (@darkwolf)


    Installed today, over 60.000 lines in error log.

    So, over 15MB in error log cause by this plugin :/

    No debug before release?

    I think is best to disable.

    [19-Jan-2017 09:45:58 UTC] PHP Warning:  preg_match() [<a href='0function.preg-match0'>function.preg-match0</a>]: No ending delimiter '~' found in /*/*/*/wp-content/plugins/wp-spamshield/includes/class.utils.php on line 637
    [19-Jan-2017 09:45:58 UTC] PHP Warning:  preg_match() [<a href='0function.preg-match0'>function.preg-match0</a>]: No ending delimiter '~' found in /*/*/*/wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639
    [19-Jan-2017 09:45:58 UTC] PHP Warning:  preg_match() [<a href='0function.preg-match0'>function.preg-match0</a>]: Delimiter must not be alphanumeric or backslash in /*/*/*/wp-content/plugins/wp-spamshield/includes/class.utils.php on line 637
    [19-Jan-2017 09:45:58 UTC] PHP Warning:  preg_match() [<a href='0function.preg-match0'>function.preg-match0</a>]: Delimiter must not be alphanumeric or backslash in /*/*/*/wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639
    [19-Jan-2017 09:45:58 UTC] PHP Warning:  preg_match() [<a href='0function.preg-match0'>function.preg-match0</a>]: Delimiter must not be alphanumeric or backslash in /*/*/*/wp-content/plugins/wp-spamshield/includes/class.utils.php on line 637
    [19-Jan-2017 09:45:58 UTC] PHP Warning:  preg_match() [<a href='0function.preg-match0'>function.preg-match0</a>]: Delimiter must not be alphanumeric or backslash in /*/*/*/wp-content/plugins/wp-spamshield/includes/class.utils.php on line 639

    edit: atm ill put some “@” in preg match (line 637, 639 and 665).
    isn’t a great way to work, but now my error log is clean.

    • This topic was modified 3 years ago by Salvatore.
Viewing 15 replies - 16 through 30 (of 38 total)
  • Plugin Contributor Red Sand Media Group

    (@redsand)

    U have update yourself without my permission.

    I’m sorry, but that is not true. If you are not aware of the plugin’s properties, that is your responsibility. We have documented the plugin’s auto-update feature in FAQ 16: Q: Q: Can WP-SpamShield do Automatic Updates? Don’t blame the developer if you haven’t read the plugin documentation. You have full control over updates.

    – Scott

    I’m sorry: I’ll install from backend, read info present in backend, not entire documentation and/or source code present in,external website. Then, no imagine an autoupdate (usually not present in any plugin).

    A simple flag in plugin page, maybe… But no, my bad I don’t have read entire (giant) faq list.

    Next time, before to install a plugin, I read also source code, entire forum, search on google, etc, etc etc.

    Scott, I’m tired of these stupid arguments and games.

    I didn’t have a support request yesterday or today.

    Yesterday I had a feature request; today I reported an error message from my logs. I also confirmed that the error message that Kona reported from your site support submission form is the same that I got yesterday when I tried to comply with your demand that I submit my feature request there.

    These are things meant to help you debug and improve your product. If users are encountering errors on forms on my sites, I want to know, so I can fix them.

    Obviously you are reading these forums, given that you take the time to argue with and chastise everyone who posts .. so there’s no reason for me to want to mess with complicated forms on your web site anyway.

    You pushed out an upgrade last night with a serious conflict with a common and widely used plugin (Wordfence), and it brought down a lot of sites. Since then you have been trying to fix things but there are flaws in your fixed code so it just creates more problems.

    Your problem was bigger than it had to be because you have designed your plugin to auto-update without giving clear notice to users, when that is unusual behavior for a plugin. So instead of a few hundred users updating their sites today and reporting a bug back to you, you pushed the error out to thousands. That is why experienced developers generally don’t force updates.

    Now because you pushed out the bad update, you’ve been scrambling to fix it and rushing out one fix after another… and obviously don’t know how to fix the problem that is generating the repeated error message and clogging up server logs.

    And right now you are only dealing with the first wave of complaints, from those of us who are attentive to our web sites and sophisticated enough to quickly figure out what is going on. (For example, we have FTP access and know where to find wordpress error logs). There are a whole lot of users who aren’t paying attention and don’t even know yet that there is something wrong with their web sites; and some of them are on cheap hosting plans and are going to find out they have a problem when their error logs break their quota and their sites stop functioning.

    And you are spending time debating online with people who are rightfully annoyed at the problems you’ve created… for reasons I can’t fathom.

    I think you would be wise to issue a new update that is a rollback to version 1.9.9.8.1 (but numbered 1.9.9.8.6) — go ahead and push that out — and after that disable the automatic update feature until you can debug properly. After that, if you want to restore the automatic updated feature, I’d suggest that you make it a prominent option that users can toggle on when they activate the plugin.

    At least that is what I would do if I were in your shoe.

    But you don’t have to take my suggestions. I don’t care. I’ve already rolled back my sites and disabled the updates, and will implement and roll out other solutions to the sites I manage. The only reason that I haven’t already removed this plugin entirely from all the sites is that I want to have time to test whatever alternatives I decide on first.

    Good night.

    @ Abigailm : Short question – how did you disabled the automatic updates? I just downloaded the old 1.9.9.8.1 and want to wait until the things are settled until I will allow further updates.
    Thanks!

    One Website bricked (had to FTP to manually delete the plugin) other websites error_log going absolutely wild with warnings

    [20-Jan-2017 15:41:24 UTC] PHP Warning:  preg_match(): No ending delimiter '~' found in /home/checkedinco/public_html/wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665
    [20-Jan-2017 15:41:24 UTC] PHP Warning:  preg_match(): Delimiter must not be alphanumeric or backslash in /home/checkedinco/public_html/wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665
    [20-Jan-2017 15:41:24 UTC] PHP Warning:  preg_match(): Delimiter must not be alphanumeric or backslash in /home/checkedinco/public_html/wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665
    [20-Jan-2017 15:41:24 UTC] PHP Warning:  preg_match(): Delimiter must not be alphanumeric or backslash in /home/checkedinco/public_html/wp-content/plugins/wp-spamshield/includes/class.utils.php on line 665

    I think perhaps it’s time to stop playing the isolated incident card – and see these releases have a major flaw. Regressing is never good, but in this case I am sure many users would be grateful.

    • This reply was modified 2 years, 12 months ago by divemasterza. Reason: spelling
    Plugin Contributor RSMG Tech Support

    (@rsm-support)

    @abigailm: We are here to solve problems.

    If you don’t want help, then your posts are complaints, but if you do want help, then your posts are support requests.

    You have already registered your complaint, and we have heard you. There is no need to keep going on. If you post false information, we will respond to correct it.

    If you would like technical support, we are happy to provide it, but you need to follow our support process. If you don’t want to follow our support process then we can’t help you.

    Technical support requires a two-way conversation. You want to tell us to “fix things”, but do not provide us any information. You also do not take any steps to fix existing issues on your site that have been identified from our Troubleshooting Guide, but yet you want us to provide a specific recourse. This is like asking a doctor to cure an illness, but refusing to tell them the details of the symptoms, and then demanding specific medication.

    You claim to not want support, yet you keep posting to these forums, so that means you are just here to complain. That is not constructive, and does not help other plugin users. There is nothing we can do for those who just want to complain. We are here for those who want to solve problems.

    @divemasterza: No one is playing “the isolated incident card”. The issue you’re reporting does not affect a high percentage of version 1.9.9.8.5 users. Reverting to an older version is not necessary. To fix an issue, it has to be replicated, and the specific conditions of the issue have to be identified. We believe we have identified the specific issue you have mentioned. We’re running a few tests. We can solve issues more quickly though if plugin users work through the Troubleshooting Guide and FAQs, then submit a support request at the WP-SpamShield Support PageWP-SpamShield Support Page.

    @farbweiss — an easy way to disable plugin updates is to edit the main php file for the plugin file to some number higher than the current version number and any likely future version number. Then the WordPress update checker will not see the edited plugin version as being out-of-date. You can make these changes either using FTP or using the “Editor” function under the Plugin menu in the WordPress dashboard.

    So in the header section of the wp-spamshield.php file, you will find a line like this:

    Version: 1.9.9.8.1

    After rollback, I simply edited that line in each of the files as follows:

    Version: 999.1.9.9.8.1

    But any number higher than 1 at the beginning of the version number would do. I use the 999. because that also is something I would immediately recognize as being a faux version number, inserted to insulate the plugin from updates.

    Note that with this method, you won’t get notices of update availability within the WordPress dashboard either. WordPress just thinks that I have version 999x of the plugin installed, and it won’t suggest updating until the author pushes out a release with a higher number.

    However, in this case I don’t trust the updates, given that each successive “fix” appears to simply introduce a new set of problems, and the plugin author seems more interested in arguing than listening to customer feedback and suggestions. So for me, I just want to buy time while I consider other plugin options — and I don’t want to risk accidentally updating this plugin again because of a WordPress prompt. I could always manually update the plugin again if desired, and the WP-Rollback plugin will will still work to enable a roll-forward.

    I want try to update a my old test plugin by stopforumspam, but i need to test and check.

    ATM I don’t have found great valid alternative.

    Then, I prefer to turn back to recaptcha.

    Plugin Contributor Red Sand Media Group

    (@redsand)

    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.

    Plugin Contributor Red Sand Media Group

    (@redsand)

    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

    Hi Scott. I posted this on another thread at https://wordpress.org/support/topic/auto-updated-and-broke-many-sites/#post-8682557 but it seems there are still issues with Version 1.9.9.8.6.

    Fatal error: Class ‘WPSS_Utils’ not found in /wp-content/plugins/wp-spamshield/wp-spamshield.php on line 7323

    When I try to install this plugin to my local server, it fails generically:

    Plugin could not be activated because it triggered a fatal error.

    This is on a blank WP installation with *no* other plugins installed.

    • This reply was modified 2 years, 12 months ago by .

    I have the exact same issue. Are you guys using serverpilot.io by any chance? Because many of my domains are not resolving correctly on top of the WP SpamShield issue. (pinging them says could not find host, even though they are correctly setup).

    I am not sure if this is related to WP Spamshield or an update on serverpilot.io along with WP Spamshield.

    Either way, I have not touched any of my websites, and ALL 300+ websites show error 500, and some of them show DNS error.

    No, not using serverpilot.io.

    I had to just disable the WP-SpamShield plugin for the time being. It killed every site I had it running on too. I was unaware, but as outlined above, it has an auto-update feature (odd for a plugin, at least without an option to set it manually) and it updated itself yesterday. When our Cloudflare cache refreshed this morning, the new plugin version broke WordPress.

    Plugin Contributor Red Sand Media Group

    (@redsand)

    We’ve got a fix in the works.

    Flag as resolved (is the 3time i reflag as unresolved) seems to be most important than really resolved.
    I really can’t understood why an author can flag as resolved a topic open by user also if this is not resolved for this user (before some warnings, now – after two new release – we have fatal error with error 500. then, nothing is resolved here)!
    I hope, one day, WordPress can fix this behaviour!

    • This reply was modified 2 years, 12 months ago by Salvatore.
Viewing 15 replies - 16 through 30 (of 38 total)
  • The topic ‘Too many warning in error log!’ is closed to new replies.