instead of downgrading, i would suggest you wait the next version of wordpress in 2 or 3 months, where both wpmu and wordpress are merged seamlessly… right now, you have no real possibility to make it go independant or you play with the database…
Anoying for you, but the backend is exactly the same, except the BP menu
nexia > Do you think the merge is that close? I really hope so. Have heard about the merge, but didn’t realise it would solve this for me in the process. Thanks for pointing it out;-)
Chouf1 > WordPress MU and WordPress differs quite a lot. The user management is different for one thing.
Hum, actually Chouf is close to the truth… with the latest 3.0_ bleeding trunks *(testing ground), the MU of wordpress is completely merged, but the officiel 2.9.1 is not yet…
the merge of both projects will be announced soon, but the date of early april would be correct based on the rumors…
The merge is done in trunk. Seriously, the work has been done already. People have announced this merge since last May-ish. We’re just about at feature freeze, so from here on out will be bug fixes only (plus some UI work on the MU menus).
While I think it;s quite possible to downgrade MU to single WP, the reverse isn’t true and it would be much better to wait until 3.0. You’ll upgrade as usual, and there will be instructions on how to turn off the network and go back to a single blog. (probably cuz I’ll write them… )
sorry to be a little out of topic, but if you speak about future, i would ask what about code optimization and php memory ?
When reading on the codex, nothing is said that WP need by default 32 mo php RAM.
And the wp-health plugin is still under alpha dev…
And sure there is a problem with php memory.
On most shared host, this php memory is set to 16 Mo max… and no way to give more (even throught htaccess, wp-settings, wp-config tricks..)
This mean that WP/Mu can’t work with more than 4 or 5 plugins in best case.
And since 2.8, the memory consumption is growing a lot.