Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • @quecksilver I blocked two strings in our htaccess
    These ended the junk in our search tracking

    <IfModule mod_rewrite.c>
    RewriteEngine On
    # next lines stop search spam added 2/7/2017
    RewriteCond %{REQUEST_URI} "82019309" [OR,NC]
    RewriteCond %{REQUEST_URI} "yl18" [OR,NC]
    RewriteCond %{QUERY_STRING} "82019309" [OR,NC]
    RewriteCond %{QUERY_STRING} "yl18" [NC]
    RewriteRule .* - [F,L]
    </IfModule>

    We also ran into this annoyance from a search spamming bot. The .htaccess blocking method seemed to work most effectively.

    At the root of our WP site, we edited the .htaccess file and included a new block

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteCond %{REQUEST_URI} “blockword1” [OR,NC]
    RewriteCond %{REQUEST_URI} “blockword2” [OR,NC]
    RewriteCond %{QUERY_STRING} “blockword1” [OR,NC]
    RewriteCond %{QUERY_STRING} “blockword2” [NC]
    RewriteRule .* – [F,L]
    </IfModule>

    Any request that has blockword1 or blockword2 in the URI or query string will get redirected to a 403 Forbidden page.

    Note, make sure it is outside of the WordPress block of settings, surrounded by
    # BEGIN WordPress
    # END WordPress

    Credit to a number of other authors for the advice, we settled on this after a few minutes of googling.

    We just went through a fresh install on 4.7, and SSO is working mostly. We have a problem related to assigned user permissions, but that existed on WP 4.5 too.

Viewing 3 replies - 1 through 3 (of 3 total)