WordPress MultiSite lacks the ability of SingleSite to ‘act as if it’s in root when it’s not.’ In short, You’ll need to move your WordPress install out of the wordpress folder and just into plain webroot.
Alas, this is NOT as easy as it is with Single Site.
Probably the best way is to move the files up one folder and then search/replace your SQL database for site.com/wordpress
There are a LOT of places.
Agh, that’s frustrating, WP isn’t running my entire site, just want it for a couple of blogging platforms on the same site.
It’d be stupid to have to install 2 separate WP installs to run under different directories.
It doesn’t have to run your whole site, you know.
I have WordPress running the main page, but I have a separate gallery and wiki, and even some static .html pages out there. You just have to pay attention to your setup and you can use it.
I’d use WordPress for my default index page and any static pages, virtual subfolders for the blogs per normal and then REAL subfolders for whatever else I need. Slap a static front page up and Bob’s your uncle.
Hmmm, yeh, that is one way, but I’m a neat freak and WP is NOT the main thing for my site, it’s secondary so I’d like my folder structure to match that theology.
I’m sure I’ll figure out a way, I just have to get in there and figure out how it’s referencing files and urls.
Doesn’t work.
It just doesn’t. Many MANY many very smart people have tried and they have failed.
You just CANNOT run WP MultiSite like that. It does not do ‘giving wordpress it’s own directory’ like singlesite. Sucks, but there you are.
I know how you feel. I want wordpress in a folder too, but I’m resigned to this for better URLs.
