Hi!
I'm going to host some wordpress blogs (5..20) and I want every user to be able to install its own modules and themes.
I'm currently running multiple copies of wordpress. That works fine, but updating means updating each site individually.
WordPress MU on the other hand is great for thousands of blogs, but doesn't support module or theme installation by my users.
So I'm searching for something like drupal's multisite feature, where each hosted site lives inside the /sites/ folder with an individual config-file and its own modules/templates.
So who's responsible for updating a user-uploaded theme that breaks as a result of updating the core blog software?
I'm aware of many (even security related) issues that may arise from this kind of configuration.
the thing is, that my users are usually a bit lazy upgrading their wordpress installation (when they update at all) and I prefer a broken theme over a pwned website.
So I would like to update the codebase when it is necessary without doing it individually for each site, which is rather annoying after the nth installation.
I am also interested in such an installation scenario.
I will also try to experiment and report back any findings.
I have tried to set up a multisite wordpress installation (without using wordpress-mu). I can say that it is possible using a drupal-style technique, but there should be some flexibility regarding the absolute path to wp-content/, so that users can have their own plugins and themes. This is what has caused the most issues so far and has required to make modifications to the core WordPress files.
lipflip
gnot