Viewing 14 replies - 1 through 14 (of 14 total)
  • I installed stop spammers. It is working well, except, somewhere in all those settings I checked a block that said if I checked this added protection ect but could slow down my site. My loads everything at a crawl now and I cant find that option to uncheck it, does anyone know where it was located;

    also should the option for “allow blocked users to see allow form be checked or unchecked Its confused me.
    I am not techie savvy. Can someone help me.

    xoogu,

    I have added this to the version you can download at blogseye.com or you can use the update add-on to automate the process.

    I am curious as to why I don’t get the error and other users aren’t complaining. I checked the code and it executes just fine and does not throw errors. It is obviously a cut and paste error and I fixed it, but I don’t show the same error.

    It may be a PHP version thing.

    Keith

    Thread Starter xoogu

    (@xoogu)

    It very likely is a PHP version thing – I’m on PHP7 (with E_ALL error reporting), which tends to be a bit stricter than earlier versions.

    Good,

    That means you are my main beta tester. You should see strange errors long before anyone else.

    I have E_ALL set on WAMP machine at home, but I usually sneak my tests in here at work by publishing to a test subdomain on my Web Host.

    Keith

    I also have this error since I moved to PHP 7.

    I am going to upgrade to PHP7 on my test machine.

    In the mean time I am uploading a fix to BlogsEye.com

    Keith

    Same error since updating to PHp7 yesterday. Is there no fix for this yet?

    I tried downloading the beta version using the plugin @ https://www.blogseye.com/beta-test-plugins/ and that also did not work.

    Error:

    downloading_package
    Forbidden

    Please try downloading again from blogseye beta test. I did not have the latest version there.

    I have to go through the whole plugin in PHP7 and the new WordPress, and when I do I’ll officially release this. For now I will update the old version on WP with this fix.

    Keith

    Now I have:

    [10-Apr-2016 16:21:18 UTC] WordPress database error Incorrect parameter count in the call to native function 'LCASE' for query select ID,post_author,post_title,post_name,guid,post_content,post_mime_type
    from wp_posts where
    INSTR(LCASE(post_author), '<script') +
    INSTR(LCASE(post_title), '<script') +
    INSTR(LCASE(post_name), '<script') +
    INSTR(LCASE(guid), '<script') +
    
    INSTR(LCASE(post_author), 'eval(') +
    INSTR(LCASE(post_title), 'eval(') +
    INSTR(LCASE(post_name), 'eval(') +
    INSTR(LCASE(guid), 'eval(') +
    INSTR(LCASE(post_content), 'eval(') +
    
    INSTR(LCASE(post_author), 'eval (') +
    INSTR(LCASE(post_title), 'eval (') +
    INSTR(LCASE(post_name), 'eval (') +
    INSTR(LCASE(guid), 'eval (') +
    IINSTR(LCASE(post_content), 'eval (') +
    
    INSTR(LCASE(post_content), 'document.write(unescape(') +
    INSTR(LCASE(post_content), 'try{window.onload') +
    INSTR(LCASE(post_content), 'setAttribute(\'src\'') +
    INSTR(LCASE(post_mime_type), 'script') +
    INSTR(LCASE(document.write(string.fromcharcode), 'script') >0
    
     made by do_action('stop-spammers_page_ss_threat_scan'), kpg_ss_threat_scan, include_setting, require_once('/plugins/stop-spammer-registrations-plugin/settings/kpg_ss_threat_scan.php')
    [10-Apr-2016 16:21:32 UTC] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '')' at line 3 for query select option_id,option_value,option_name
    from wp_options where
    INSTR(LCASE(option_value), 'eval(') +INSTR(LCASE(option_value), 'eval (') +INSTR(LCASE(option_value), 'networkads') +INSTR(LCASE(option_value), 'document.write(unescape(') +INSTR(LCASE(option_value), 'try{window.onload') +INSTR(LCASE(option_value), 'escape(document[') +INSTR(LCASE(option_value), 'escape(navigator[') +INSTR(LCASE(option_value), 'document.write(string.fromcharcode') +INSTR(LCASE(option_value), '(base64_decode') +INSTR(LCASE(option_value), '(gzinflate') +INSTR(LCASE(option_value), 'UA-27917097-1') +INSTR(LCASE(option_value), 'w.wpquery.o') +INSTR(LCASE(option_value), '<scr'+')  made by do_action('stop-spammers_page_ss_threat_scan'), kpg_ss_threat_scan, include_setting, require_once('/plugins/stop-spammer-registrations-plugin/settings/kpg_ss_threat_scan.php')

    Fixed.

    Interesting thing about this is that it goes back over a year and always worked somehow.

    You can download latest at Blogseye.com on the beta page.

    thanks,

    Keith

    Hi Keith,

    That seems to have done the trick, many thanks for the fix – and for the great plugin.

    Thanks,
    Frank

    I confirm this error.
    I am running ubuntu 16, php 7 (fpm) w/ nginx.

    P.S. this stopped several of my clients from ordering.
    Why would you have 2 parameters named the same way ?

    public function kpg_ss_add_allow($ip,$options=array(),$stats=array(),$post=array(),$post=array()) {
    “plugins/stop-spammer-registrations-plugin/classes/kpg_ss_challenge.php”

    It is fixed in the version on my website BlogsEye.com. I also committed to the www.remarpro.com version, but did not update the version number because it was a simple bug fix.

    Keith

    I am having this issue too. Latest version (6.15) installed.

    2016/10/04 23:39:09 [error] 10310#10310: *843 FastCGI sent in stderr: "PHP message: PHP Fatal error: Redefinition of parameter $post in /srv/http/blog/public/assets/plugins/stop-spammer-registrations-plugin/classes/kpg_ss_challenge.php on line 383" while reading response header from upstream, client: [redacted], server: [redacted], request: "POST /wp-login.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php7.0-fpm.sock:", host: "[redacted]", referrer: "https://[redacted]/wp-login.php?redirect_to=https%3A%2F%[redacted]%2Fwp-admin%2F&reauth=1"

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Mistake in kpg_ss_add_allow’ is closed to new replies.