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.
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:
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!
- The topic ‘Giving WordPress multisite its own directory’ is closed to new replies.