Problem activating on wordpress site in subdirectory

  • Resolved Fadookie

    (@fadookie)


    11 years, 3 months ago

    My wordpress installation lives in a subdirectory (‘I’ll call it subdir’) as described here:
    http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory

    The main site content gets served from the site root using a rewrite rule in .htaccess:

    <IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

    This used to work for normal site content (i.e. myblog.com/somepage), but I’d access my admin by giving the URL to the actual subdirectory. So that would be myblog.com/subdir/wp-login.php.

    I’ve followed your instructions adding the hook in functions.php (let’s say I renamed my login page to ‘skeeball’ for sake of example) and the additional rewrite rules in .htaccess. My wp-login.php is successfully blocked, but I get a 404 regardless of whether I hit myblog.com/skeeball or myblog.com/subdir/skeeball. I’ve been dicking with the rewrite rules for a while trying to get it to work and I’ve given up.

    https://wordpress.org/plugins/sf-move-login/

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author Grégory Viguier

    (@greglone)

    11 years, 3 months ago

    Hi Fadookie.

    I definitely haven’t try this kind of edgy configuration.
    Are the rewrite rules from the plugin printed BEFORE those from WordPress in the .htaccess file?

    Plugin Author Grégory Viguier

    (@greglone)

    11 years, 2 months ago

    Hello.
    Still not working?
    I remember a bug in WordPress that could cause this kind of problem: if your WP is not up to date and use https for login/administration (but not on the site itself), it might be it.

    rob1n

    (@rob1n)

    11 years, 2 months ago

    I had the same issues with this plugin, and I ended up having to deactivate it. My setup is similar to the first post, with my site served at http://domain.com/ but my WordPress files (wp-includes/, wp-admin/, wp-blog-header.php, etc.) are in http://domain.com/wp/.

    This means my login page is at http://domain.com/wp/wp-login.php.

    However, the rewrite rules kept trying to rewrite my custom slug to http://domain.com/wp-login.php, which of course doesn’t exist so it displays my 404 page.

    I poked around in the code, and it looks like there’s nothing in place to take care of this kind of setup (which isn’t an uncommon layout at all).

    RewriteBase is based on the home URL, which for me would be http://domain.com/, so it’s RewriteBase /. However, none of the individual rules add the WPURL part (wp/) so it ends up not working.

    A possible solution could be to get the value of parse_url( site_url(), PHP_URL_PATH ) which should be something like “/wp” in my case, then adding this on before every RewriteRule. I wouldn’t change RewriteBase as that could have unintended effects on other rules in the htaccess.

    Plugin Author Grégory Viguier

    (@greglone)

    11 years, 2 months ago

    Hi there.

    @rob1n, I’ll give it a try this week-end.

    rob1n

    (@rob1n)

    11 years, 2 months ago

    You’ll figure this out when you work on how to do this, but it just occurred to me that after getting the “/wp” part, you should strip the first slash and add a trailing slash to make it work with the rewrite rules.

    Thanks for looking into this!

    Plugin Author Grégory Viguier

    (@greglone)

    11 years, 2 months ago

    OK, want to try the beta out and give me a feedback?
    Tested on both monosite and multisite in directory: the plugin seems to work fine for both now.

    rob1n

    (@rob1n)

    11 years, 2 months ago

    Just installed it and tried it out; seems to work fine so far. I’ll let you know if I have any problems, but so far so good.

    Thanks for taking the time to fix this.

    Plugin Author Grégory Viguier

    (@greglone)

    11 years, 2 months ago

    OK, version 2.1 is unleashed.
    I tag this topic as resolved.

    Randy Hicks

    (@vc27)

    10 years, 7 months ago

    Any possibility this could need to be re-opened? I am having this same issue. Everything seems to be correct. The .htaccess seems good -> gist example

    I’m running a clean install with no other plugins running and using the 2015 theme. Just doing some testing of a few mashups.

    Any ideas I should look into?

    Plugin Author Grégory Viguier

    (@greglone)

    10 years, 7 months ago

    Hi.

    Indeed, this bug seemed to be resolved and I don’t see any problem in the rewrite rules.
    Is your wp-login.php file really located at example.com/admin/wp-login.php?
    Maybe the fact that the folder is named “admin” is the problem, but it would be surprising.

    Greg

    Randy Hicks

    (@vc27)

    10 years, 7 months ago

    Yeah the wp-login.php is located at example.com/admin/wp-login.php.

    I’ll do some more research on my own setup. Considering no one else has posted any issues in 6mo I’m pretty sure it’s my setup. I’ll post back when I figure it out. It’s probably something supper simple I over looked 🙂

    creationdepot

    (@creationdepot)

    10 years, 4 months ago

    Hey all!

    So I’m having the same issue with wordpress having moved into its own directory, and the login is pointing me to 404 pages. I’ve got version 2.2.2 installed.

    Sure I’m just missing something obvious but I’ve tried domain.com/wp/login and domain.com/login and still no luck.

    Appreciate any feedback!

    Thanks!

    Wendy

    Plugin Author Grégory Viguier

    (@greglone)

    10 years, 4 months ago

    Hello Wendy.

    I keep testing but I don’t trigger any bug 🙁
    I confirm the login page should be available at domain.com/wp/login (only).
    The only bug I know in the plugin right now occurs if you’re not using the port 80 on your server (like localhost:8080 for example).

    Greg

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

The topic ‘Problem activating on wordpress site in subdirectory’ is closed to new replies.