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 4 years, 10 months ago by Salvatore.
Viewing 15 replies - 1 through 15 (of 38 total)
  • Plugin Contributor RSMG Tech Support

    (@rsm-support)

    Hi @darkwolf,

    I know, right! It’s ridiculous! Being serious though, we did do a thorough debug before release but this was an odd situation that didn’t show any errors in pre-flight. It’s not triggered on every site. We did get to the bottom of it though and will have a patch released soon.

    – Steven

    Thread Starter Salvatore

    (@darkwolf)

    ok but, if issue (warning) exists in some website for unknown reason, maybe – imho – some simple “@” is best than a giant error log.
    if i don’t see this i can go to some gigabyte of error-data in one/two week(s) and can be a problem.

    anyway, is first time with this plugin.
    i glad to continue to test and maintain, with akismet, in my community (without any captcha).

    please, report me if i can help with this issue.

    kind regards,
    S.N.

    Plugin Contributor Red Sand Media Group

    (@redsand)

    Update: Version 1.9.9.8.5 has been released with the fix.

    I’ve installed this fix and I’m still seeing this same “Delimiter must not be alphanumeric or backslash” preg_match() issue in the log file.

    WordPress 4.7.1, WP-SpamShield 1.9.9.8.5, PHP 5.6.5.

    Plugin Contributor Red Sand Media Group

    (@redsand)

    Hi @kona,

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

    – Scott

    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.

    Dear Scott,

    All I’m trying to do is to let you know that your fix for a recently introduced bug has not fixed the bug for me.

    Anyway, at your request I have duly gone to your website, gathered all the information you requested (including details of all plugins, etc etc) and attempted to send this to you.

    Your form will not let me submit this information :
    —–
    There is a problem with your support request.

    As noted above, you need to work through the FAQs and Troubleshooting Guide before submitting a Support Request. You checked the box saying you have worked through these, but you haven’t even visited these pages yet. Please go back and work through these completely before submitting a support request.
    —–

    Forgive me, but given that I’m simply trying to help you diagnose a problem you have inadvertently introduced, this seems a little onerous! I am more than happy to send you the relevant information by email if you could suggest a suitable email address.

    Plugin Contributor Red Sand Media Group

    (@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

    I just want to note that this is the exact same error message I got and was complaining about in my thread at https://wordpress.org/support/topic/turn-off-auto-updates/#post-8669061

    Not only was it cumbersome and insulting — it was also false, since I not only had read the troubleshooting guide, but I also was referring to it and quoting it in my comments on that thread.

    I don’t know if your form works by checking for a cookie or what… but it definitely doesn’t make it easy for anyone to submit info on your support site.

    We simply ask users to work through the troubleshooting guide, the FAQs, and the Known Conflicts page.

    As noted above, the problem is that the form throws up that error message even for users who HAVE checked the troubleshooting guide already. So in my eyes it is just a bit of poorly coded javascript intended to discourage people from submitting support requests.

    Plugin Contributor Red Sand Media Group

    (@redsand)

    @abigailm,

    I personally review our site’s logs. That is patently false. It’s an easy process to follow. You seem to be more intent on complaining than solving problems. If you want our help, then follow the support process. It’s pretty simply. Other users have no issues submitting support requests. You spend more time complaining than anything else.

    – Scott

    Why did I get that error message then?

    Plugin Contributor Red Sand Media Group

    (@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

    Thread Starter Salvatore

    (@darkwolf)

    Today, again, same error in log.
    I fix, and u put auto update (without any permission) and break again.
    Is really time to uninstall.

    This is not a good way to work.

    Really bad experience for me.

    Plugin Contributor Red Sand Media Group

    (@redsand)

    Hi @darkwolf,

    If you’re having an issue after the 1.9.9.8.5 release we ask that you submit a support request at the WP-SpamShield Support Page. It’s really not fair for you to say this if you had not submitted a support request at the plugin’s main support venue. Most users are having no issues with the latest release.

    – Scott

    Thread Starter Salvatore

    (@darkwolf)

    I don’t have update. U have update yourself without my permission.
    Also, I report here issue persist.
    Other user report issue still persist.

    Isn’t useful to report in other place.

    I repeat: Installed, bugged, fixed, u have update my release without ask to me If can update, bugged again.

    I’m an user, installed this plugin just yesterday, this is the bad experience has possible with a plugin.

    Regards, and good work with your plugin.

    I go to search alternative.

Viewing 15 replies - 1 through 15 (of 38 total)
  • The topic ‘Too many warning in error log!’ is closed to new replies.