The goal of this post is to confuse you, and your head will probably hurt by the end. This is a process story on how we came to decide terminology for WordPress 3. The main feature of the WordPress 3. MU, or multi-user, was a fork of the codebase designed for many blogs and many users, all on one install. Technically, MU can support multiple sites, wordpress get_site_option each site is a domain, and each site will have more than one blog.
All of this can be managed by a single MU installation. The cross-domain aspects require a plugin, but subdirectories or subdomains are out of the box. If a blog is now a site, then what does a site become?
More on that later. Surely, we can make this more difficult. And so, just as the UX decision was made to call a blog a site, we decided to call a multisite a network. A lot of discussion centered around the options API. There are no options across an entire MU multi-domain install, but we still thought about that and it caused plenty of confusion.
In despair, one suggestion was thing, thingy, and wordpress get_site_option, to wordpress get_site_option blog, site, and network. MU blog admins have lesser privileges than both MU site admins and single-install admins.
So much for that. We started a new deprecated file to be included only wordpress get_site_option running multisite and we ended up adding 3 more deprecated files for other contexts. This brings up another problem we wordpress get_site_option yet to address: If a network an MU site has many blogs err, sitesthen what is a collection of many MU sites across domains?
This later inspired talk of capes, but I digress. This is more or less a summary of an actual Wordpress get_site_option conversation among a handful wordpress get_site_option contributors and developers, including myself. It was mind-numbingly confusing. I would wordpress get_site_option to the logs, but its contents make a lot of smart people look really wordpress get_site_option. Lead developer of WordPress, living in Washington, D.
Follow me on Twitter. View all posts by Andrew Nacin. Ironically, when I install 2. Amazing how complicated wordpress get_site_option things get! This equates wordpress get_site_option make the UI look nice and who cares if the code is messy. What happened to code is wordpress get_site_option We should not rename functions just for the sake of renaming them. Where would the renaming end? No need, and not even close to worth it. That maybe so, but it illustrates why merging the existing MU codebase into WordPress itself is problematic.
A better alternative wordpress get_site_option have been to start from scratch rather than merging the MU codebase. Would things have been backwards compatible? But sometimes you have to start over to move forward. Backwards compatibility is great, but sometimes it has wordpress get_site_option be sacrificed for the greater good of the project. For most new users, it will be new to them. I just want to manage some pages on my website.
Why did you make blog a site in the first place? A blog is just a feature of a site. You can have a blog on your site or your site can consist of only your wordpress get_site_option. I got sites with no blog feature on them. You said it yourself, you have sites with no blog feature on them.
None wordpress get_site_option that works. A collection of sites is a network. Wordpress get_site_option domain-mapping plugin can run multiple networks on a single install, but there is no out-of-the-box support wordpress get_site_option MU or 3. Standard installation is just a site. And you really should think about renaming stuff and deprecate.
Working with wp 3. Same button action equals different results and so on. You make my work possible: This would allow backwards compatibility for plugins and themes while making future development less of a headache.
Where do we keep the Tylenol? In my installation I have 4 test sites test and 2 networks N1 and N2. Also if I delete N2 without moving its sites they go to limbo, they are not reassigned to N1, this makes sense but not sure that is how it should work.
Thank you for making the terminology make some sense. This post has helped me to understand exactly what is going on so much better. Php nuke is a cms that has Super Admins, allows you to choose your own admin name upon install and only shows site administration to Admins.
It has so many options that it can be intimidating to users but a wordpress get_site_option of cake for webmasters. I wish I had read this post two weeks ago, though now that I have completed the installation of 3.
Thanks for the post! You can see where this is going. Sites, Blogs, Networks Oh My. Sites, Blogs, Networks, Oh My! Getting Started with Multisite Wizpress. WordPress And Giving Credit. Get Up-to-Date on WordPress 3.
Get Started Using the WordPress 3. I do hope that you all take wordpress get_site_option time to play research with other software. Maintaining support for legacy wordpress get_site_option.