Adds a Networks panel for network admins to create and manage multiple Networks from one WordPress installation.
|Author:||David Dean (profile at wordpress.org)|
|WordPress version required:||3.0|
|WordPress version tested:||3.7.1|
|Added to WordPress repository:||21-01-2011|
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|Total downloads:||25 629|
Click to start download
Adds a Networks panel allowing network admins to create and manage multiple Networks from one WordPress installation. Each Network can exist on its own domain, and have its own set of blogs / Sites.
Each Network can have its own set of plugins, themes, administrators, permissions, and policies, but all will share a database of user accounts.
Sites can be moved freely among Networks.
Each Network will require changes to your web server and DNS.
See Frequently Asked Questions for detailed instructions.
- Slovak translation generously provided by Branco, (WebHostingGeeks.com)
How do I set up new domains as networks with a single WordPress install?
Your webserver must direct requests for each domain you want to use to your WordPress install’s filesystem location.
Here’s a quick overview:
- DNS should resolve each desired domain to your web server.
- Configure your web server to direct requests for each desired domain to the same site (e.g. via
Tip: You can use the New Network Preview feature to verify DNS and server configuration BEFORE creating your networks.
What’s with `networks-mufunctions.php`?
This file has fixes for unusual network topologies, like networks without a root site or those more than one subdirectory deep.
The fix for networks with deep paths was graciously contributed by Spencer Bryant.
For a long time I avoided bundling fixes like these, since I was committed to having this plugin run only when needed by the dashboard.
This file does not rely on the rest of Networks for WordPress to function, so you are free to copy it to your mu-plugins folder and use it on its own.
This seemed like a good compromise. If you have thoughts, let me know in the comments!
If you are on WP 3.5 – 3.6.1 and want to use native file uploads, you must either:
- Activate the Networks plugin on all of your networks, OR
If you do not do this, your uploaded files will end up in unexpected places.
This is not needed for WP 3.7+.
- Changed: Native upload handling on WP 3.7 without this plugin active
- Changed: Made text labels more consistent with WP terminology
- Changed: Made siteurl replacement trailing slash-insensitive when changing network path – fix contributed by mgburns!
- Fixed: changing network domain or path could reset site paths – fix contributed by mgburns!
- Fixed: PHP warning when viewing the Networks admin screen – thanks, zawszaws
- Added: ability to set upload handling per network
- Added: switch blog_id when switching sites / networks
- Fixed: primary sites on all networks used the same upload path (WP 3.5+ only) – thanks, RavanH
- Added: Slovak translation provided by Branco, (WebHostingGeeks.com)
- Added: Delete rewrite rules when moving a site – thanks, mgburns
- Changed: New network’s root site inherits the search-engine visibility of the site used to create it – thanks, Christian Wach
- Fixed: Squashed PHP warnings when
WP_DEBUGis true – contributed by Christian Wach
- Fixed: Bug fixes in restore_current_site – contributed by Christian Wach
networks-mufunctions.phpfile containing fixes for unusual Network topologies. See FAQ for details
- Changed: made visual changes to fit in with the WP dashboard
- Changed: assign sites select boxes are now bigger (varies by number of sites)
- Fixed: bug that prepended the domain name on to sites whose path matched the network’s when moving – thanks, sharonmiranda!
- Fixed: provide SSL network URLs when required – thanks, Spencer Bryant
- Added: Screen Options for selecting number of Networks per page
add_sitefunction now defaults to a path of ‘/’ if one is not supplied
- Fixed: searching and sorting by Network Name – thanks, skvwp
- Added: descriptions for MANY more sitemeta keys, using WP native strings where possible
- Added: placeholders for most text fields
is_super_admin_for()function for checking permissions on other networks
- Changed: reorganized the “Create a Network” panel to be more intuitive
- Changed: (for developers)
$options_to_copynow carries the sitemeta keys to be cloned as values instead of keys
- Changed: switched to
- Changed: split code up into different files for easier maintenance
- Fixed: hardcoded URL that may have prevented some from deleting networks in bulk
- Added: New Network Preview will try to check mapped domains for possible collisions
upload_filetypesis now cloned by default, so you don’t have to save settings before uploading files on new networks
- Added: enhanced help menu for WP 3.3
- Added: ability to restrict Networks Menu to a certain Network with the
- Added: WP 3.3 help pointer
- Changed: removed ability to delete the primary network
- Fixed: enhanced compatibility with WP < 3.1 – thanks, suresh.sambandam
- Added: support for the
- Changed: Updated Help screen to display in WP 3.3
- Fixed: Adding a network now displays the correct update message
- Added: Network diagnostic screen
- Changed: allow Site assignment page to continue even if a blogname key is missing
- Added: hooks with new wpms prefixes
- Fixed: enabled checkbox to avoid creating a root blog. This is for advanced users only.
- Added: better documentation in the Help tab
- Added: basic automated validation of new Network settings
- Removed: documentation on domain names that no longer applies
- Changed: show each network only once in Move Site field, regardless of metadata issues
- Fixed: a bug affecting network installs with old table name scheme (created before WP 3.0)
- Fixed: admin display bug affecting WP 3.2 installs
- Changed: processing to ensure that new Network paths are always valid
- Changed: documentation on new Networks
- Fixed: short_open_tag off compatibility
- Fixed: a bug that showed the Networks panel in the Site Admin backend on 3.1
- Fixed: a typo that left network-dependent blog options behind when moving blogs – thanks, edmeister
- Fixed an issue with the link to Network backends for versions before 3.1 – thanks, RavanH
- Initial release