Posted 5 months ago #
Am I understanding the readme correctly in that the plugin currently does not work in network mode if I am using sub-domains without a core hack?
Also, does the plugin work if I switch over to a sub-directory network install?
*I'm kinda wishing I had used a sub-directory install anyhow, as I didn't realize that you can now domain-map sub-directories, which prior was not possible.
Posted 1 month ago #
This is correct, and unfortunately neither are compatible without a core hack. The root of the problem is due to the pervasive use of absolute urls in wordpress. So at the moment only path-based installations are compatible and only if the core patch is applied (and I haven't updated the patch to work for 3.3 so you'd have to investigate the new version on your own.) And honestly after working with the MU system for wordpress for the past year I don't recommend it at all from a usability or architecture perspective. It's just a giant hack on top of the wordpress base install.
Posted 1 month ago #
By any chance were you able to come up with the mu 'hack'?
Because I don't have a better solution than to use mu, I'm kinda stuck having to use it.
I just read through the trac ticket and you make such a perfect argument that I am shocked that it is not being seriously considered. Here's to hoping that maybe in a near distant future the core team will give it more consideration as the benefits are huge.
Posted 1 month ago #
Unfortunately I don't have a one size fits all solution. It really depends on the number of users and whether each user needs access to mutltiple sites. Given the existing pain in managing users under the current MU install I'd wager it would be easier to just create separate installations of a single install and try to automate the upgrade process across each installation. Granted this means N databases, N apache configs, N admin accounts etc but if you can knock out a few shell scripts and your users don't need cross-site access then you'd be better off in my opinion. Unfortunately the wordpress core team is committed to keeping this application an install in one place and manage in one place only package so I doubt they'll be open to retrofitting the mu architecture in any significant way.
And the root problem of absolute urls will prevent any sane architecture and the core team has officially rejected such a design. It's sad to say but this is one of those cases where investing heavily into an application framework like codeigniter or joomla will yield better results (at a higher price of course.)
Posted 1 month ago #
I'm sad to hear that it's been officially rejected. Appreciate the heads up and information. Supppose I will keep muddling along.
You must log in to post.
