Changes between Version 1 and Version 2 of how-to/wordpress/network


Ignore:
Timestamp:
Aug 19, 2013, 6:49:55 AM (6 years ago)
Author:
Jesus Franco
Comment:

Draft completed with instructions to set multi domains network.

Legend:

Unmodified
Added
Removed
Modified
  • how-to/wordpress/network

    v1 v2  
    6363''While you shouldn't to install a new WordPress application for every new domain, you should make sure you are adding the domains according to the prerequisites listed before, mapping your domain first to MF/PL nameservers, then adding the domain and its wildcard subdomain to the ServerAlias of the same Web Configuration your current WP Network.''
    6464
    65 There are two plugins available for this ...
     65There are two plugins available for this, the original one available in WP.org, [http://wordpress.org/plugins/wordpress-mu-domain-mapping/ WordPress MU Domain Mapping], helps you make every subdomain, a different domain, then you can have example2.com, example3.com and so on without maintaining a whole different WP install.
     66
     67Another one, based on the first, is developed to let you handle several domains and their respective subdomains through the same network. For a real example, we run several blogs like resonancia.saltoscuanticos.org, rac.saltoscuanticos.org, tomalapalabra.radiozapote.org, subalterno.radiozapote.org, and of course www.saltoscuanticos.org and www.radiozapote.org, all handled by the same network and being easier to maintain and upgrade, supporting several projects more easily and enforcing security and performance rules when needed, not being able to blogs admins to disable the SuperAdmin installed tweaks.
     68
     69While a bit different, the process to install these plugins it's not the typical one through search/upload, activate and go. We are going to detail the enabling of the second plugin, GPL'ed but upgradable only through a paid subscription to WPMUDEV:
     70
     711. Download the plugin (attached) and uncompress it ''on your own workstation'' (not the webserver).
     72
     732. Connect via SFTP to your account, and upload the different pieces of the plugin to the next wp-content locations:[[BR]][[BR]]
     74  * sunrise.php -> wp-content/
     75  * dm_sunrise.php -> wp-content/plugins/
     76  * /mu-plugins/ -> wp-content/plugins/
     77
     783. Edit again your wp-config.php and add the next definition:[[BR]]
     79  `define('SUNRISE', on);`
     80
     814. Login to your Network admin area and "Network activate" the "Multi-Domains for Multisite" plugin.[[BR]]
     82  `http://example.com/wp-admin/network/plugins.php`
     83
     845. Now you have the Multi-Domains item inside the Tools Menu in the Network Admin area. There you can add new domains to your network. You can enable a domain to be "private" (only other SuperAdmins can create new blogs for that domain, and assign new admin users to publish in them), or "public" (if you let existing/new users register by themselves new blogs, they will be able to choose that domain among all others domains marked as "public").
    6685
    6786== Beyond first Network ==
    6887
    6988It's possible running several networks over the same codebase (WP core, themes, plugins), without the ''sunrise'' domain mapping plugins, but it involves a bit of work right into the wp_site and wp_sitemeta tables, as it's described here: http://webmasterformat.com/blog/multiple-wp-site-management While a bit more involved, the advantage is being able to define different sets of super-admins, themes and plugins enabled, for different networks/sites/domains. With the ''sunrise'' domain mapping plugins, all the blogs run on the same network which is easier to handle.
     89
     90So, just for clarify, every site listed in wp_site table is a network and with the domain mapping plugins, can support several domains/subdomains (listed each one in wp_blogs table). Without any of these plugins, you can anyway support several domains/subdomains, but they will be handled logically like different networks. This can be very useful according to more complex userbases and projects.
     91
     92= A note about security =
     93
     94Be cautious on letting every single visitor to register a new account and creating new blogs, on the recents attack waves from botnets to WP sites across the world, we resisted because we didn't let anyone to register a new site, and we were hitted a lot! in the pages known to be entry point to spammers. Also, remember you are not letting every blog admin to install new plugins or new themes, not upgrading, nor editing them, their permissions are roughly similar (a bit more relaxed, actually), to the admins of wordpress.com or network23.org blogs.
     95
     96Anyway, if you keep the upgrades of the sites running smoothly and pay attention to help provided by tools like Better WP Security, W3TotalCache and several others (this is a whole area to be expanded in other how-to's), you are going to have happier users, and be a happier admin too without the nightmare of upgrade every single site, but all your network at once. Even if you are the only SuperAdmin/Admin/Editor of your sites (or have a very small team), the time spent on setting up your network is not a loss but a win in sleep hours into the future.
     97
     98Make Happy Networks! \o/