multisite wordpress files in a subfolder / index.php in root ... possible? (25 posts)

  1. cinematic
    Posted 6 years ago #

    I like it to install wordpress in a subfolder and place just the index.php to the root directory. I know that this was not possible with the 'old' wordpress multiuser. However, I tried it with wordpress 3.0 multiuser and it looks as if there are no problems at all.

    Are there known issues with multiuser if wordpress url and siteurl are different? I tried creating new blogs, uploading images and I didn't experience any problems so it *SEEMS* to work fine. However, I would rather prefer to be sure :-)
    Thanks for any infos on this.

  2. Samuel B

    Posted 6 years ago #

    works well for me

  3. cinematic
    Posted 6 years ago #

    thanks ... then I too will give it a try ...

  4. Really? It's not supposed to work...

    for both of you, what format are you using, subdomains or subfolders?

  5. Samuel B - Seriously? MultiSite's been known to blow ugly chunks when this is done. How did you do it?

  6. cinematic
    Posted 6 years ago #

    I am using subfolders and have not experienced any problems yet.

  7. can you login to the backend of the sub-blogs?

  8. cinematic
    Posted 6 years ago #

    Yes, I can go to the backend by clicking multisite network, choosing the site and click on adminstration. I can also log out and log in again via the backend of the sub blog.

  9. .. and I wanna know what kind of blog addresses y'all are getting for the sub sites.

  10. Did you enable the network and then move the index.php up to the root?

  11. cinematic
    Posted 6 years ago #

    The blogaddress is domain/blog/subsite

  12. cinematic
    Posted 6 years ago #

    I first moved the index.php and then enabled the network. Just noticed that the permalink is blog and the folder with the wordpress files is named blog too. Does this make a difference?

  13. Ah, okay.

    I thought you were somehow getting it to work so your blog was installed in domain/blog, but the URLs would be domain/subsite.

    I am officially less weirded :)

  14. Me too.

    edit: for people being told this is *not* possible, the different is the folder name is still intact. If you don't want the folder name to show up... sorry. no can do.

  15. I speak Andrea:

    You cannot install in domain.com/wordpress and have your links be domain.com/blog/permalink and domain.com/subblog/permalink

    Your links will be:

  16. :D

    and darn fluently too!

  17. tirussell
    Posted 6 years ago #

    I don't yet speak Andrea, and think my desired setup is similar.

    It's a .edu site, and I hope to have it work more as a CMS where

    domain.edu/ ...is the homepage (or immediately redirect to home.php or other), which will not be powered by WP3, at least for now.

    and then have

    domain.edu/office2/ ...as my sub-sites

    ...the way I have WP3 multi-site working is the pages of the main network site appear at


    is this going to lead to tragedy down the line, and how do you suggest I configure WP so I can have a completely standalone (non-WP) homepage?

    I see things about a mandatory /blog/ directory, but my staging site seems to be working without?

  18. When wp is installed in root, the mandatory blog folder is a virtual construct you can override. When it's a physical folder, not so much.

    That said, top level site pages are supposed to be sans the blog folder, so that's okay. The sanity checks for pages should cover any potential conflict with subsites.

  19. Samuel B

    Posted 6 years ago #

    sorry been away - see you all worked it out :>)

  20. tirussell
    Posted 6 years ago #

    Just sipping my first cup of coffee, so can you clarify a bit - do you mean I can just drop in my own index.php in the root to enable a standalone (non-wp) domain homepage and the rest of the top-level pages and subsites will still work? That seems like it would prevent the whole WP system from being invoked - or will the .htaccess settings make this a non-issue?

    Sorry if this is dumb - sleep still very much in my eyes, but hope to jump on this as soon as I get to my desk this morning.

  21. I can't speak for whatever it is that Samboll or cinematic did, actually. I would assume that their index.php is a copy of the one from their wordpress folder (assuming domain.edu/wordpress is where it's installed) and they changed




    Which ... might work, given that cinematic reports the URLs that come back DO include the wordpress foldername.

    What I do know is that if you install WordPress in root (so domain.edu) then you get the following URL structures

    Site #1 main interface -- domain.edu
    Site #1 blog posts -- domain.edu/blog/permalink
    Site #1 PAGES -- domain.edu/pagename

    Site #2 main interface -- domain.edu/site2
    Site #2 blog posts -- domain.edu/site2/permalink
    Site #2 PAGES -- domain.edu/site2/pagename

    etc etc.

  22. Samuel B

    Posted 6 years ago #

    that's it exactly - I have this working locally and in a test environment at ASO

  23. To the best of my knowledge, even with this kind of setup, if you use a subdirectory version of multisite with WordPress's files inside a physical subfolder off of the root, you won't be able to access domain.com/$blogname/wp-admin/, nor can you access domain.com/$blogname/wp/wp-admin/ or domain.com/wp/$blogname/wp-admin/

    The subsites will appear to function, their themes and permalinks will behave, but you'll have no access to WordPress files.

  24. that's exactly what I've been trying to explain all along.

  25. You might be able do some kind of .htaccess hack to balance that out, but I still don't think it would work reliably on a subdirectory install.

    Works fine when multisite is setup with subdomains though.

Topic Closed

This topic has been closed to new replies.

About this Topic


No tags yet.