Tagged: wpmu Toggle Comment Threads | Keyboard Shortcuts

  • Jay Versluis 6:40 pm on January 20, 2014 Permalink | Reply
    Tags: , , wpmu   

    Categories: WordPress ( 135 )

    WordPress Multisite: a Brief Guided Tour 

    101012-pink-black-cherry-blossom-festival-icon-social-media-logos-wordpress-logo-squareInstalling WordPress Multisite isn’t the hard part – it’s getting your head around how to use it, especially if you’ve mostly been using single installs. In this quick tour I want to give you some pointers on how to use your new installation, and how it differs from single WordPress installations.

    New Role: The Super Admin

    On a single installation, the Administrator was the “master of your domain”. In a Multisite installation however he no longer has the powers that he once had. Instead, the Super Admin is now in charge of many of the more intricate options.

    Super Admins can create new sites, delete sites, install themes and plugins, assign upload space and upgrade WordPress along with themes and plugins from a central location. Administrators can no longer do such things.

    As a (once single site) Administrator having converted your site into a Multisite environment your user automatically becomes a Super Admin upon conversion. Hence you have two different dashboards to go to: a Network Dashboard, and a Site Dashboard. That can be very confusing when you’e first confronted with the concept.

    What once was the Main Site

    After the upgrade to Multisite your previous site is now part of the network, by default appended with “sites”. So if your single site was called “Demonstration”, then WordPress will now call it “Demonstration Sites”. You can simply rename it if it’s not to your taste.

    Screen Shot 2014-01-20 at 17.49.59

    New Menu Option: My Sites

    At the top of the admin bar you’ll see two options: “My Sites” and “Your Site Title”, both of which have the usual drop down menus upon hovering. The latter option is the current site you’re administering and works much like what you’re used to from single site installs.

    My Sites is different, and perhaps better known to WordPress.com users who have more than one blog. My Sites will show you each of the sites you’re a member of, and provide handy links to each site’s Dashboard and options. Right now you may only have one site, so this menu will make much more sense when you start creating your second and third site in a moment.

    Themes and Plugins

    In Multisite, only the Super Admin can install the above, and decide which are “Network Enabled”. This means that once installed, a theme or plugin can be made “available” to site users, who in turn can configure or activate the enabled items.

    When themes are network enabled, site users can choose which one to activate. Network enabled plugins on the other hand are active immediately on each site, but not necessarily configured (Akistmet for example requires an API key for each network site).

    Creating New Sites

    Navigate to My Sites – Network Admin – Sites to see a list of current sites in your network. From here, use the Add Site button to create a new site. Give it a name, permalink and email address for the administrator (use your own if you’d like to be one yourself).

    Screen Shot 2014-01-20 at 18.06.22

    This will create a new set of tables in the database, but use the same WordPress files on disk to serve each website. Single installs have 11 magic tables, Multisite has 17, and will add another 9 for each additional site in the network – with a different prefix for each site.

    Uploaded files are still stored on disk under wp-content/uploads, but now each site has a subdirectory which coincides with the Site ID in the network, followed by year/month folders. For example, a new file for your first site may be stored as wp-content/uploads/2/2014/01/yourfile.png. Note that those directories are only created when you’re uploading a file.

    Deleting, Archiving and Deactivating Sites

    WordPress is nice and cleans up after itself: deleting a site will remove all those additional database tables associated with a site, as well as remove all files from the server that were uploaded by said site.

    When a site is archived, it becomes read-only, juts for browsing, but it will remain public.

    Deactivating takes it offline so it’s no longer accessible on the network. Only Super Admins will see it and can being it back if necessary. This is useful if you want to curb your network, and alternative to deleting sites completely.

    Neither option compresses or removes files from the server, nor is this meant to be a “backup option”, as the term archiving may imply.

    Multisite Upgrades

    Under Network Admin – Updates you can download upgrades for themes, plugins and WordPress core. Once done you will be prompted to “update your network” which will go through each site and apply the necessary database tweaks associated with an update. Depending on the amount of sites in your network this can take some time.

    Note that site users no longer need to perform any update operations and are not notified of new theme/plugin versions. It’s now up to the Super Admin to take care of such tasks.

    Multisite Settings

    Most aspects of your network can be tweaked, from the welcome email text to free public registration, to the amount of upload space each site user is allowed. Explore Network Admin – Settings – Network Settings for a long list of such options.

    While you’re here, note the Network Setup section. These familiar code boxes contain your configuration for both wp-config.php and .htaccess files – in case you misplaced those settings.

    Creating additional Super Admins

    Super Admins can create “users” under Network Admin – Users. By default these are Administrators which can be added to sites in the network. Editing an Administrator allows the Super Admin to tick a box called “Grant this user Super Admin privileges”.

    The End

    And that concludes the quick guided tour! Let me know if anything is unclear or if you’re still stumped as to how to make Multisite work for you.





     
  • Jay Versluis 5:31 pm on January 20, 2014 Permalink | Reply
    Tags: , wpmu   

    Categories: WordPress ( 135 )

    How to setup WordPress as a Multisite Network (formerly known as WPMU) 

    wordpress-iconInstalling WordPress Multisite can give your site the benefit of being part of a network. I use this feature to spawn multiple installations that live on the same domain. It makes my life so much easier to update several WordPress instances at once. It’s also a great way of being logged into several individual sites at the same time.

    WordPress Multisite isn’t for everybody, and not every hosting company will allow you to install or use it. It will however work with most hosting packages that support a standard WordPress installation.

    Let me talk you through the installation process and the caveats you may encounter. The current installer that comes with WordPress 3.8 is excellent at giving you guidance on what to do. Note that you cannot install Multisite on localhost installations (MAMP, Wamp Server, etc).

    Starting from scratch

    We’ll start with a standard single WordPress installation, created by a one-click installer from Plesk 11.5. Multisite can be installed in two ways and it’s a good idea to think about how you’d like your sites to appear:

    It is the latter way of installing Multisite that usually causes trouble because it requires domain wildcards to be setup correctly. To avoid this problem we’re going to use the first option and go with subfolders. At this point I assume your single instance is working correctly.

    Permalinks

    Multisite only works if any form of Permalinks are activated. The default is set to the very first option in the list (?p=123) and we can’t have that. Choose any of the options, I’m going with the option called Post Name:

    Screen Shot 2014-01-20 at 16.55.02

    Hit save and you should be greeted by the message “Permalink Structure saved”. This will save Apache ModRewrite rule changes to your .htaccess file and tells the web server how to re-write URLs in the browser that’s visiting us. Sometimes this file is not writable, in which case WordPress will instead display what you need to manually add to this file as a block of code.

    Tweak wp-config.php

    Now it’s time to add a line to your configuration file. This will tell WordPress that you’d like to install the Multisite environment. Add the following to your wp-config.php file, just above the Authentication Keys will work fine (roughly in line 35/36):

    /** Multisite Setup **/
    define('WP_ALLOW_MULTISITE', true );
    

    Save the changes, then upload the file back to your server and refresh the Admin Interface. At first glance, nothing appears to have changed (which is a good sign).

    Activating and Installing “The Network”

    Navigate to Tools – Network Setup, which is a new option that’s become active since we’ve fiddled with that configuration file. Choose how you’d like to install the network (subdomains or subfolders, as explained above), give your new network a catchy name and verify your email address.

    Choose option 2 (subfolders) to avoid complications, then hit Install:

    Screen Shot 2014-01-20 at 17.03.34

    WordPress will get back to you with two blocks of code, specific to your installation. Please copy and paste from what WordPress will give you, this is for illustration purposes only

    The first block needs to go into your wp-config.php file which we’ve patched earlier. Directly underneath the line that specified “allow multisite” (roughly line 37/38).

    The final result should look like this:

    /** Multisite Setup **/
    define('WP_ALLOW_MULTISITE', true );
    define('MULTISITE', true);
    define('SUBDOMAIN_INSTALL', false);
    define('DOMAIN_CURRENT_SITE', 'example.com');
    define('PATH_CURRENT_SITE', '/');
    define('SITE_ID_CURRENT_SITE', 1);
    define('BLOG_ID_CURRENT_SITE', 1);
    

    The second block is something for your .htaccess file and will replace the current Permalink structure we’ve setup earlier. WordPress Permalink Tweaks usually start with #BEGIN WordPress and #END WordPress. Anything in between those lines needs to be updated with the code WordPress will give you.

    Your .htaccess file should look something like this when you’re finished:

    # BEGIN WordPress
    
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    
    # add a trailing slash to /wp-admin
    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
    
    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ - [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    RewriteRule . index.php [L]
    
    # END WordPress
    

    Save both files and upload them back to your server. Once done you can follow the handy Log In link at the bottom of that page or just click on the Dashboard option. You will be prompted to login again.

    Welcome to your new Multisite Network

    Nicely done! You’re back in your main site’s Dashboard and all looks well (I hope). You will notice a couple of extra options at the top to administer the sites in your network.

    The Multisite philosophy is very different from single site installs. For example, themes and plugins can no longer be installed via their respective menu options, they can only be activated or deactivated. These powers no longer belong to the Administrator role, they have been given to the Super Admin instead.

    We’ll get into how to use WordPress Multisite in another article though.





     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel