1. http://mu.wordpress.org/
2. I don’t get it. You want the blog files in one directory and the posts in another? Well, the posts is stored in mysql database, not as files in a directory.
Do you mean you want to post to a category defined by another of your multiple blogs?
I imagine that he means he would like to install WordPress in http://www.example.com/wordpress and then call the posts up from the main root index http://www.example.com/index.php. Which is obviously do-able. Furthermore, there are cases in which it would be handy. If, for example, you wanted a lot more static pages and content on your site that the new v1.5 PostPages features allows, you may want a WordPress blog to be a part of your site, rather than taking it over. However, you may want the latest post (or two) to come up on your site’s main (root index) page. Something like this, in other words. In fact, I am currently toying with this idea.
The problem is, it isn’t something that can come as an out-of-the-box solution in blogging software. After all, the only reason you would use it is to give you more site layout flexibility than WordPress (or any other) publishing tool allows. So building it into WP would somewhat defeat the point. The bottom line, andrewsprout, is that you can call posts (or any WP data) from any (PHP) page on your site, in any directory. You just need to write the database retreive functions into that page’s PHP code.
Thanks, rparker! That’s exactly what I was referring to, and I will try to use this advice. But then you see there is the whole PostPages and templates thing I’d have to know enough about php to do, but I don’t.
Maybe somebody could make a plug-in.
And as far as multiple blogs, I mean that instead of having a category for each, it would be more like… (do I have to say it?!) MoveableType in the sense that you can have different users under different blogs. For example, if I wanted an editorial part of my site, people could post there, and the other blog would be a news/updates blog with a different team of web editors.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Y’know, I’m getting a bit tired of the “I don’t understand reply …” which was the response last year when I said multiple blogs was the one thing keeping me from making the move.
Consider the work of a charity, a school, a church … subdomains for groups within the organization. So you get a main blog, then each group has its own blog – but all from the same blogging software.
On the front end, users might see:
http://www.mychurch.org – for general use
youth.mychurch.org – branded away from old fogies (e.g. different look, feel and content)
advent.mychurch.org – specializes in Christmas devotions
Each is branded differently, each has entirely different content, each supported by the same group of people – which is kinda hard to do w/categories – especially when categories become your points of menu navigation for each of the above.
On the back-end, one application/interface to rule them all.
That’s why.
I think we understand the benefit of having multiple blog support in WordPress. It’s just that A. it’s not in WordPress yet, and B. WordPress supporters are going to do their best to suggest what options are available. Often someone looking for multiple blog support finds a workable (if still a workaround) solution is out there.
Problem with findng a “workable/workaround” is when you use a blog as a form of content managlement for a charity, school or whatever.
You hack it all up for the institution, move on and they’re stuck wondering why they can’t upgrade the software.
Well as I said, we understand the benefit of multiple blog support.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
