[resolved] Giving WordPress multisite its own directory (10 posts)

  1. shennyg
    Posted 4 years ago #

    I am trying to figure out what the following means:

    Giving WordPress its own directory will not work in WordPress 3.0 with multisite enabled. It interferes with the member blog lookup.

    - http://codex.wordpress.org/Create_A_Network#WordPress_Settings_Requirements

    My guesses at the explanation of above:
    1. You can do it but it leads to errors in the future when you try to use the "member blog lookup."
    2. It will not work even if you try, wordpress knows you will be getting yourself into trouble and stops you.

    I think I ruled out number 2. I have the following setup in a test environment:

    dev.tld/mu/ - WordPress multisite enabled install
    dev.tld/mu/foo - mulitsite child site
    dev.tld/mu/bar - another mulitsite child site
    dev.tld/mu/biz - a new install of WordPress mulitsite

    So it does work, I want to figure out the problems I may run into.

    First problem I found is creating a child site from here: dev.tld/mu/biz/wp-admin/ms-sites.php
    I am trying to create the following sites:

    I get these errors: http://wordpress.pastebin.com/LKeknw4t
    Here is my configuration settings: http://wordpress.pastebin.com/Hz6Gq1vU

    Is this the "member blog lookup" interference that is being talked about?

    Could someone show me an example or explain what "member blog lookup" is?

    I want to make a recommendation to SysOps at my company on the proper way to architect what we need using WordPress.
    I am looking at having a blog at a subdirectory /mu/ while having a blog with the multisite capabilities bellow it at /mu/biz/

    I read that you cannot even put a multisite install in a subdirectory: http://wordpress.org/support/topic/multisite-sub-directory-setup
    But I did it at /mu/ and even went one further and installed another multisite beneath it at /mu/biz/

    According to my tests:
    1. One can setup a multisite installation in a subdirectory
    2. Nesting one multisite in another multisite starts throwing some errors.

    Can anyone provide me some insight?

    Thanks for reading!

  2. That warning refers to people who want to install the program in a directory (like /wordpress/) then run it out of the root so their domain is whateverdomain.com and the blogs are off that domina. THAT is what won;t work.

    If you want dev.tld/mu/ with dev.tld/mu/foo, you're fine.

    Nesting another multisite install in there is a different issue. not sure why you're attempting it?

  3. shennyg
    Posted 4 years ago #

    I want a blog at dev.tld/mu/ then I want a directory of city blogs (it will just be a page that links to each sub site) here dev.tld/mu/biz/ so I can do the following: dev.tld/mu/biz/city1 dev.tld/mu/biz/city2

    And when I try to create dev.tld/mu/biz/city1 from this page dev.tld/mu/wp-admin/ms-sites.php by inputing this: biz/city1 under "Add Site > Site Address: /mu/" I get the following error:

    Missing or invalid site address.

    Thanks for explaining my first problem!

  4. Yeah, you can't create nested sites from the backend. :)

    this might help tho, with grouping:

    not so much with the url structure.

  5. shennyg
    Posted 4 years ago #

    Interesting, thanks for your input Andrea!

    Is there another way to do it? not "from the backend"

  6. SFO
    Posted 4 years ago #

    Hi there,

    I was wondering if you might be able to help. I'm trying to set up a network using WordPress within a subdomain. I want to set it up so it works like this:

    domain.tld/blogs/ - multisite install
    domain.tld/blogs/foo - blog site
    domain.tld/blogs/bar - blog site

    I noted that you said you'd got WordPress to work this way, despite it saying on the create a network page that this wasn't possible.

    I have tried enabling the Multisite on a WordPress 3.1 installation and I have the Super Admin panel active and can create new sites. However, the themes are not carrying through and you can't access the backends for the blog sites, i.e. going to domain.tld/blogs/foo/wp-admin returns the 404 page.

    My settings appear to be the same as @shennyg but I might just need to do something quite simple to fix it.

    Any help given would be much appreciated!

    My settings are as follows:

    wp-config.php :

    define('WP_ALLOW_MULTISITE', true);
    define( 'MULTISITE', true );
    define( 'SUBDOMAIN_INSTALL', false );
    $base = '/blogs/';
    define( 'DOMAIN_CURRENT_SITE', 'domain.tld' );
    define( 'PATH_CURRENT_SITE', '/blogs/' );
    define( 'SITE_ID_CURRENT_SITE', 1 );
    define( 'BLOG_ID_CURRENT_SITE', 1 );

    .htaccess :

    RewriteEngine On
    RewriteBase /blogs/
    RewriteRule ^index\.php$ - [L]
    # uploaded files
    RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
    # add a trailing slash to /wp-admin
    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ - [L]
    RewriteRule  ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
    RewriteRule  ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    RewriteRule . index.php [L]



  7. No, that will work. :)

    What WON'T is installing WP in the blogs folder but wanting the URL to be domain.tld

    You have the right .htaccess, so in your case, it's that your .htaccess file is not being read properly. Tell your web host that's busted, and you need them to add allow overrides in their vhosts file to fix it.

  8. Ovidiu
    Posted 4 years ago #


    got a similar question:

    have a look at the wp-config.php settings above, it says:

    define( 'DOMAIN_CURRENT_SITE', 'domain.tld' );
    define( 'PATH_CURRENT_SITE', '/blogs/' );

    why would it say current site: domain.tld if I want my main site to be available at domain.tld/blogs/ ?

    my issue is that I want to install wp with multisite inside domain.tld/somefolder/ and want it available there, not on the main domain... would that work with above settings?


    Mine is this:

    define( 'DOMAIN_CURRENT_SITE', 'domain.tld' );
    define( 'PATH_CURRENT_SITE', '/' );

    You have to tell WordPress where it is, basically. Don't worry about the domain in your case, just the path :)

    Make sense?

  10. Ovidiu
    Posted 4 years ago #

    ok, thx.

Topic Closed

This topic has been closed to new replies.

About this Topic