Andrew Nacin who is one of the core developers of WordPress has published a post that should have come with a package of Tylenol. The post goes into the reasons behind why the terminology within WordPress MU was changed and why it’s created a soup of confusion. I’ve read the post three times in a row and it still hurts my head to try and make sense of it all.
When the merge began, the core developers began to use multisite internally to mean many blogs (well, sites), shortened to “ms” where possible, thus removing the “mu” and “wpmu” prefixes on files and functions.
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.
So if you’re wondering why things are named the way they are in the merged edition of WordPress MU, give his article a read. Bonus points if you can read it once and not get lost.
In this fun filled episode of WordPress Weekly, I was privileged to be joined by two awesome members of the WordPress community, Andrea and Ron Rennick also known as the WordPress MU Gurus. During the show, we talked about a number of different things related to WordPress MU including the impending code base merge with WordPress, plugin and theme compatibility, the differences between WordPress and WordPress MU, usability enhancements to the WordPress MY back-end interface, and much more. Near the end of the show, we talk about the trend of plugins switching to a paid model which I find to be a very interesting topic.