Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter eosterman

    (@eosterman)

    Additionally, I just noticed that despite only activating the plugin on one site, I’m getting redirects to /custom-login on all other sites.

    -Erik

    Plugin Author Greg Winiarski

    (@gwin)

    Couple of questions to help debugging:
    1. what settings (redirects) do you have entered in CLU?
    2. does the same problem occurs on single site installation (ie. non-WPMU)?

    Thread Starter eosterman

    (@eosterman)

    Greg,

    Unfortunately, I don’t have any single site installations to test on. I started from the get go on WPMU from the get-go.

    Here are my CLU settings:

    https://www.dropbox.com/s/o1k8y8y4qh9miwd/Screenshot%202014-04-04%2010.00.12.png

    -Erik

    Plugin Author Greg Winiarski

    (@gwin)

    Hmm, config seems ok, the plugin will create an additional entries in your .htaccess file you can check if some other plugin or theme is not adding entries there earlier with flag [L], if yes then CLU redirects will not be executed.

    Thread Starter eosterman

    (@eosterman)

    Ah, perhaps therein lies the rub. I use NGINX, not Apache. The “.htaccess” stuff is an Apache construct.

    You you provide a sample .htaccess file for me so I can adapt those for Nginx?

    My .htaccess file in the document root is empty despite the permissions being 0644 and owned by the webserver process.

    -Erik

    Plugin Author Greg Winiarski

    (@gwin)

    The plugin adds lines similar to this in .htaccess

    RewriteRule ^panel/login/ /wp-login.php [QSA,L]
    RewriteRule ^panel/remind/ /wp-login.php?action=lostpassword [QSA,L]
    RewriteRule ^panel/register/ /wp-login.php?action=register [QSA,L]
    RewriteRule ^panel/logout/ /wp-login.php?action=logout [QSA,L]
    Thread Starter eosterman

    (@eosterman)

    Aha, this makes a big difference. I will implement a work around. I suggest that the plugin check to see if it is running under an Apache context and provide a warning, if not.

    -Erik

    After changing the permalinks I am now getting – ERROR 500 – INTERNAL SERVER ERROR – had to remove the rewrite rules for all the changed permalinks in .htaccess. Not sure why, maybe has something to do with all in one wp security plugin im running…just fyi.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘"Error 404 – page not found" After Install’ is closed to new replies.