BitNami WordPress Multisite

     

    IMPORTANT: WordPress Multisite requires you  to use different domains for each site. If you are trying to log into the WordPress application using an IP address, you may have problems with Google Chrome or Safari browsers. You can try using Firefox or Internet Explorer, but it is highly advisable that you use domains instead of using IP addresses. You can learn how to configure domains on your own machine for testing in the "How to configure the domain for WordPress Multisite" section.

    BitNami WordPress Multisite Stack simplifies the installation of WordPress Multisite Network and its required dependencies. A Multisite Network is similar to your regular WordPress blog but it lets you create more blogs on demand. A multisite network is a collection of sites that all share the same WordPress installation. They can also share plugins and themes. It is indicated for organizations, communities or user groups. 

    How to install WordPress Multisite?

    It can be deployed using a native installer, as a virtual machine or as an AMI to the Amazon cloud. The following instructions apply if you are downloadig the installer, if you are using the virtual machine or the AMI you can skip this section.

    Once you have downloaded the installer (the filename will be similar to bitnami-wordpress-VERSION-multisite-installer), double click on the icon to launch the installer. Note: If you are using Linux you will have to give executable permissions to the file first, using this command:

    chmod +x /path/to/bitnami-wordpress-VERSION-multisite-linux-installer.bin
    

    WordPress multisite requires to be installed in the default port: 80. For this reason it is necessary on Linux systems to run the installer as root user in Linux machines.

    If you see the following error message:

    "Unable to bind to the 80 port number. WordPress Multisite only supports this port for the Apache server."
    

    It is possible that you are not running the installer as root user or is there any other application using this port (for example Skype or a web server). To run the installer as the root user on Linux,  you will need to execute it using sudo (for example if you are running Ubuntu) :

    sudo /path/to/bitnami-wordpress-VERSION-multisite-linux-installer.run
    

    or become root first with the following command, and then execute the installer:

    su -l 
    

    If you are using OS X, the installer will ask you for the Administrator password automatically. You can also run the Stack as root user from a Terminal:

    $ sudo /path/to/bitnami-wordpress-VERSION-multisite-linux-installer.app/Contents/MacOS/installbuilder.sh

    Once the installation process starts, it will look like the following:

    In the Component Selection page you can enable or disable phpMyAdmin application installation. This application is a tool written in PHP intended to handle the administration of MySQL over the Web.

    In the following page you can configure the Admin user credentials for the WordPress Multisite application. You can configure the "login" and "password" for the Administrator. You can also specify your name and your email address.

     

    In the next screen, you can configure the Blog name and the domain. If you are installing the Stack in a machine with an already domain configured, you only have to specify it. If you are installing it in a local network for testing, you can add a new domain in the "hosts" file in your machine. For example, you can add the following line in the "/etc/hosts" file.

    127.0.0.1    mydomain.com
    

    On Windows you can add the same line in the "C:\windows\system32\drivers\etc\hosts" file.

    On OS X you can edit the "hosts" file with the following command in a Terminal:

    $ sudo nano /etc/hosts
    

    Do not forget to remove this entry if you are using a know domain name and uninstall BitNami WordPress Multisite.

    You can also configure the email settings for the application. This is required so your application be able to send emails. If you use a GMail account, you only have to specify your user and password. If not, you should have to specify the SMTP settings of your email provider.

    These following options only changes the file permissions in the WordPress installation. If you are going to deploy the BitNami WordPress Multisite in a public server, it is advisable to select this option.

    The Stack is copying the files and configuring WordPress Multisite.

     

    So easy right? That's all!

    How to configure the domain for the WordPress Multisite main blog?

    This approach is based on the Bitnami Configuration Tool (bnconfig).

    Bitnami Cloud Hosting

    The best way to change your URL in BCH is to go to your application tab and modify it there. In the Bitnami Cloud Hosting console, select Servers, choose your server, Manage and go to the Applications tab. Press there the pencil next to the application which URL you want to modify and choose .

    Cloud Images and Virtual Machines

    Moving the application to /

     If your application is running in "/wordpress" you can remove the prefix from the URL executing the following command:

    $ sudo /opt/bitnami/apps/wordpress/bnconfig --appurl /
    

    (use --help to check if that option is available for your application)

    Now you will be able to access to the application at http://YOUR_DOMAIN instead of http://YOUR_DOMAIN/wordpress.

    Updating the IP or hostname

    Some applications require to update the IP/domain if the machine IP/domain changes. The bnconfig tool also has an option which updates the IP automatically during boot, called machine_hostname (use --help to check if that option is available for your application). Note that this tool changes the URL to http://NEW_DOMAIN/wordpress

    sudo /opt/bitnami/apps/wordpress/bnconfig --machine_hostname NEW_DOMAIN
    

    If you already moved your application to the root URL you should include both options at the same time.

    sudo /opt/bitnami/apps/wordpress/bnconfig --appurl / --machine_hostname NEW_DOMAIN

     

    If you have configured your machine to use an static domain name or IP, you should rename or remove the "/opt/bitnami/apps/wordpress/bnconfig" file.

    sudo mv /opt/bitnami/apps/wordpress/bnconfig /opt/bitnami/apps/wordpress/bnconfig.disabled

     

    Native Installer

    Remember to use your actual installation directory instead of installdir.

    Moving the application to /

    If your application is running in "/wordpress" you can remove the prefix from the URL executing the following command:

    On Linux,

    installdir/apps/wordpress/bnconfig --appurl /
    

    On Mac OS X, 

    installdir/apps/wordpress/bnconfig.app/Contents/MacOS/installbuilder.sh --appurl /
    

    On Windows,

    installdir/apps/wordpress/bnconfig.exe --appurl /
    

    (use --help to check if that option is available for your application)

    Now you will be able to access to the application at http://YOUR_DOMAIN instead of http://YOUR_DOMAIN/wordpress.

    Updating the IP or hostname

    Some applications require to update the IP/domain if the machine IP/domain changes. The bnconfig tool also has an option which updates the IP automatically during boot, called machine_hostname (use --help to check if that option is available for your application). Note that this tool changes the URL to http://NEW_DOMAIN/wordpress.

    installdir/apps/wordpress/bnconfig --machine_hostname NEW_DOMAIN
    

    If you already moved your application to the root URL you should include both options at the same time.

    installdir/apps/wordpress/bnconfig --appurl / --machine_hostname NEW_DOMAIN
    

     

    If you have configured your machine to use an static domain name or IP, you should rename or remove the "/opt/bitnami/apps/wordpress/bnconfig" file.

    mv installdir/apps/wordpress/bnconfig installdir/apps/wordpress/bnconfig.disabled
    

    Tabs end

    If you have problems with redirection when you try to log in the WordPress admin panel, check that the domain was successfully updated in the database:

    - "wp_options" table: siteurl and home options
    - "wp_blogs" table: domain option
    

    Then clear your browser cache and try to log in again to the application. If you are using an IP address instead of a domain name, you can find problems with some browsers. It is advisable to use a domain name for WordPress Multisite.

     

    If you are installing it in your local machine for testing, you can add a new domain in the "hosts" file in your machine. For example, on Linux or OS X you can add the following line in the "/etc/hosts" file:

    127.0.0.1    mydomain.com
    

    On Windows you can add the same line in the "C:\system32\drivers\etc\hosts" file.

    On OS X you can edit the "hosts" file with the following command in a Terminal:

    $ sudo nano /etc/hosts
    

    How to add several WordPress Multisite blogs with subdomains?

    You can add a new Site from the Network Admin panel. In this case, the site address is automatically configured for creating a subdomain. This configuration works if you have previously configured your domain to accept wildcards (*.mydomain.com). For example: site1.mydomain.com, site2.mydomain.com, etc. You can see how to configure wildcards subdomains at http://codex.wordpress.org/Configuring_Wildcard_Subdomains.

    The steps if you want to configure it on Apache are:

    • In /opt/bitnami/apache2/conf/bitnami/bitnami-apps-vhosts.conf add the line

      Include "/opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf"
      
    • In /opt/bitnami/apache2/conf/bitnami/bitnami-apps-prefix.conf comment the line

      Include "/opt/bitnami/apps/wordpress/conf/httpd-prefix.conf"
      
    • In /opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf modify the ServerName and ServerAlias entries to look like this

      ServerName mydomain.com
      ServerAlias *.mydomain.com
      
    • Restart the Apache server

      sudo /opt/bitnami/ctlscript.sh restart apache
      

    If you are installing it in your local machine for testing, you can add a new domain in the "hosts" file in your machine. For example, on Linux or OS X you can add the following line in the "/etc/hosts" file:

    127.0.0.1    mydomain.com
    

    On Windows you can add the same line in the "C:\system32\drivers\etc\hosts" file.

     

     

    If you want to create a new site, WordPress Multisite automatically configures your new site in a subdomain. Important: please add an "Admin Email" for an already existing user in WordPress. You can use the same email that you use for the main site.

     

     

    Once you have created your new site in a subdomain, it is necessary that the new site address is resolved. In this case, if you have not configured the Wildcard subdomains, you can simply add it in the your "hosts" file for testing:

    127.0.0.1    newsite.mydomain.com
    

     

    That's all, you can access now at http://mydomain.com and http://newsite.mydomain.com blogs.

    How to add several WordPress Multisite blogs with different domains?

    The WordPress MU Domain Mapping plugin allows users of a WordPress Multisite network to map their blog/site to another domain. This plugins is already installed in your BitNami WordPress Multisite since 3.5.1-1 version (if you are using a previous version, you can install the plugin following the plugin installation guide).

    This section describes how to add different blogs in WordPress Multisite with different domains, for example: mydomain.com, newsite.com, otherdomain.com.

    In this case it is necessary that all these domains points to the same machine IP address where it is WordPress Multisite installed.

    Working on your local machine

    If you are testing locally you can use the hosts file to add them. 

    On Linux or OS X you can add the following line in the "/etc/hosts" file:

    127.0.0.1    mydomain.com
    127.0.0.1    newsite.com
    127.0.0.1    otherdomain.com
    

    On Windows you can add the same line in the "C:\system32\drivers\etc\hosts" file.

    On OS X you can edit the "hosts" file with the following command in a Terminal:

    $ sudo nano /etc/hosts
    
    Domain provider configuration

    If you already have different domains, you can configure them to point to the server IP address in your Domain Provider. You can find more info here

    Configuring apache to accept any domain

    IMPORTANT: WordPress Multisite is configured to use subdomains by default. If you are going to point any domain to your WordPress application, it is necessary to edit the "/opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf" file to accept any domain. Replace the following option in the file and restart the Apache server:

    ServerAlias *.yourdomain.com

    with

    ServerAlias *

    If you are running WordPress Multisite with other applications in Bitnami Cloud Hosting make sure that you check  this section.

    WordPress configuration

    Go to the WordPress admin panel and enable the "WordPress MU Domain Maping" in the "Plugins" section.

    multisite1.png

    Then configure the plugin in "Settings" -> "Domain Mapping". Note that this option is in the Network admin panel, check that you are in the main Network admin panel and not in a subsite administration panel.

    In this example, you can find an example using the BitNami Cloud Hosting service, but you can use a similar configuration for your installation. BitNami Cloud Hosting already uses a wildcard for the subdomain, so all the subdomains points to the same IP address. The main domain for this example is: wpms.bitnamiapp.com.

    test1.wpms.bitnamiapp.com, test2.wpms.bitnamiapp.com and all the subdomains will automatically points to the same IP address. In your installation, check that you are using wildcards for the domain or, if you are testing it, check that all the domains are present in your hosts file.

    It is important to enable the "Permanent redirect" option. This makes your subdomain or subdirectory sites redirect to their domains.

    multisite4.png

    Create a new site now. Do not worry about the subdomain name, it will be replaced to your new domain for the blog users.

    multisite2.png

    Go to "Settings" -> "Domains" and configure the domain for the new site. You should know the Site ID. In this example, the main blog have the Site ID 1 and the new site (test1.wpms.bitnamiapp.com) has the Site ID 2. That's all, you only have to associate your own domain to the Site ID. Note that "seconddomain.com" should be configured to use the server IP address in your domain provider administration panel.

    multisite5.png

    In the "Sites" section, you can check the current configuration for the different sites.

    multisite6.png

    If you also want to add more domains for the same site, you can also add them using this plugin. F.e. if you want to configure "bitnami-example.com" and "www.bitnami-example.com" to the same site, you can add both domains to the same site. Note this only works for subsites and it is not possible to add more than one domain for the main site.

    domain-mapping.png

    The result is the same site has different domains, one of them is the primary domain.

    domain-mapping-2.png

    WordPress Multisite with domain support configuration sharing server with other applications (Bitnami Cloud Hosting)

    In Bitnami Cloud hosting you can create a server with WordPress Multisite running together with other applications. If you configure your WordPress installation to support domains adding the ServerAlias * directive you may find that other applications are redirected to WordPress as well. In order to avoid this edit the /opt/bitnami/apache2/conf/bitnami/bitnami-apps-vhosts.conf and make sure that /opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf is the last file loaded.

    If you have applications running in /prefix (/redmine, /owncload, etc), these applications are running in the default VirtualHost defined in the /opt/bitnami/apache2/conf/bitnami/bitnami.conf file. You will also need to edit this file and specify the ServerName directive to avoid them to be redirected to your WordPress Multisite instance:

    <VirtualHost _default_:80>
        ServerName example.bitnamiapp.com
        ServerAlias localhost
        (...)
    
    <VirtualHost _default_:443>
        ServerName example.bitnamiapp.com
        ServerAlias localhost
        (...)
    

     

    Note that these changes are only necessary when configuring WordPress Multisite to support different domains. The default configuration in Bitnami supports subdomains and these additional changes are not necessary. If you are trying to access phpMyAdmin using the SSH tunnel, you should can connect to the web application at http://localhost:8888/phpmyadmin

    To learn more about name-based Virtual Host support in apache please check the official Apache documentation.

    How to add several WordPress Multisite blogs with different domains manually?

    This is a manual process to change the WordPress database to use different domains. We strongly suggest to use the plugin "WordPress MU Domain Mapping" in case you need to use different domains for the sites. You can find more info in the previous section.

    This section describes how to add different blogs in WordPress Multisite with different domains, for example: mydomain.com, newsite.com, otherdomain.com.

    In this case it is necessary that all these domains points to the same machine IP address where it is WordPress Multisite installed. If you are testing locally you can use the hosts file to add them.

    On Linux or OS X you can add the following line in the "/etc/hosts" file:

    127.0.0.1    mydomain.com
    127.0.0.1    newsite.com
    127.0.0.1    otherdomain.com
    

    On Windows you can add the same line in the "C:\system32\drivers\etc\hosts" file.

    On OS X you can edit the "hosts" file with the following command in a Terminal:

    $ sudo nano /etc/hosts
    

     

    Go to the Administration panel and create a new site. WordPress only lets you create a subdomain. Do not worry about that. Once you created it, you can edit the full domain name.

     

    wordpressms10.png

     

    Once you created the site it is necessary some changes in the database. You can modify the options using phpMyAdmin application.

    1. Open the bitnami_wordpress database and insert anew row in the wp_site table:
      Leave “id” empty (it is an autoincrement field), set “domain” to the domain name, and enter "/“ as path. Then, click the "Go" button.

      multisite-phpmyadmin.png

    1. Copy all the rows in wp_sitemeta replacing site_id to the new site id. You can do this running the following SQL query (replacing $SITEID with the id number that got created in the previous step):
    INSERT INTO wp_sitemeta (site_id, meta_key, meta_value) SELECT $SITEID, meta_key, meta_value FROM wp_sitemeta WHERE site_id = 1;
    
     
    1. Go to the wp_blogs table and edit the entry that have the domain of your new site. It is necessary to update the site_id to the id of the row created on step 1 in wp_sites table ( in this case it is "2")

      multisite-phpmyadmin2.png

    2. Open the "wp_[blog_id]_options" table (in this case is wp_2_options) and update the fileupload_url to match the new domain. You can open the "Search" tab and enter "fileupload_url" in the option_name. Then edit this option_value to match the new domain.​

    That's all, you have your new site in a new domain ready. Note that following these steps, the new site will dissapear from your Network Sites in the Network Administration panel. WordPress Multisite is configured to use subdomains by default.

    How to change my installation from subdomains to subdirectories configuration?

    Our default configuration for WordPress Multisite is using subdomains. If you want to use a subdirectories configuration instead, you can change our default configuration following the steps below. Please note that this should be done before creating new sites.

    Check your Network Setup in the Settings section of your WordPress Network Admin dashboard.

    Screenshot-1.png

    You will see that your wp-config.php is using "define('SUBDOMAIN_INSTALL', true);". Edit your wp-config.php file and change this value to false (create a copy of this file first in case you need to revert your change).  This file is located at your installation directory in apps/wordpress/htdocs/wp-config.php (on virtual machines and cloud images, the installation directory is /opt/bitnami).

    Your wp-config.php file should include now . Refresh your dashboard and check that this configuration setting have been updated.

    Now you will need to update the Rewrite configuration. WordPress instructions refer to the .htaccess file, however in Bitnami these settings are located in the WordPress httpd-app.conf file. For security Bitnami disables the .htaccess file. Edit the apps/wordpress/conf/http-app.conf file in your installation directory (create a copy of the file first) and update the Rewrite conditions to match with the options showed in the Network Setup panel.

    Once you have updated the configuration, restart the apache server.

    /opt/bitnami/ctlscript.sh restart apache
    

    How to manage roles and permissions for different blogs?

    By default, all users will have subscriber access to all sites on your network. You can add new users and also assign different roles for each site in the WordPress Multisite. If you use the Multisite User Management plugin, you can set the default role for each site and this plugin applies it.

    The administrator users cannot install new themes or plugins in their blogs assigned, only the Network Admin or "Super Admin" be able to install them and can be activated per-site or for the entire network.

    How to log in the admin panel for the different sites?

    If you are using different domains and different users in the same machine for testing, is it possible that you have login issues in the admin panels for the different sites. It is important that you clean you browser cache and cookies. You can find more info at http://codex.wordpress.org/Login_Trouble

     

    How to enable Multisite support manually

    The following guide describes how to convert an existing WordPress installation in a WordPress Multisite manually.

    How do I enable Multisite support?

    Assuming your server is already set up on port 80, follow the steps below to enable Multisite support:

    First of all, make a backup of the files involved in this process, just in case (htaccess.conf may not exist):

    cp  /installdir/apps/wordpress/htdocs/wp-config.php /installdir/apps/wordpress/htdocs/wp-config.php.backup
    cp  /installdir/apps/wordpress/conf/htaccess.conf /installdir/apps/wordpress/conf/htaccess.conf.backup
    

    Now, edit /installdir/apps/wordpress/htdocs/wp-config.php and add the following piece of code at the top of the file, just below the <?php header:

     
    /** This will enable Wordpress' multisite feature */
    define('WP_ALLOW_MULTISITE', true);
    

    The top of the file will then look something like this:

    <?php
    /** This will enable Wordpress' multisite feature */
    define('WP_ALLOW_MULTISITE', true);
    /**
     * The base configurations of the WordPress.
     *
    
     

    Again, make sure you leave the "<?php" at the top. Now go to the Wordpress Dashboard, which is located at http://your_server_address/wordpress/wp-admin. Inside the Tools menu there is a new option, "Network". Click it.

    step 04.png

    Now Wordpress will ask you about the details of your blog network. Fill in your information and click Install.

    step 05.png

     

    At this point, Wordpress will show you a screen with instructions. Notice the two big blocks of code:

    Screenshot-1.png

    We will need them in a minute.

    Make a directory called blogs.dir inside /installdir/apps/wordpress/htdocs/wp-content/

    mkdir /installdir/apps/wordpress/htdocs/wp-content/blogs.dir

    Next, edit /installdir/apps/wordpress/htdocs/wp-config.php, locate the line /* That’s all, stop editing! Happy blogging. */ and paste the first big block of code above it. The result should be similar to this, except for your server address which will likely be different:

    define( 'MULTISITE', true );
    define( 'SUBDOMAIN_INSTALL', false );
    $base = '/wordpress/';
    define( 'DOMAIN_CURRENT_SITE', '127.0.0.1' );
    define( 'PATH_CURRENT_SITE', '/wordpress/' );
    define( 'SITE_ID_CURRENT_SITE', 1 );
    define( 'BLOG_ID_CURRENT_SITE', 1 );
    /* That’s all, stop editing! Happy blogging. */

    Edit /installdir/apps/wordpress/conf/htaccess.conf (create it if it doesn't exist) and replace whatever is between #BEGIN Wordpress and #END WordPress with the second big block of code. Again, the result should be similar to this:

    # BEGIN WordPress
    <Directory installdir/apps/wordpress/htdocs>
    RewriteEngine On
    RewriteBase /wordpress/
    RewriteRule ^index\.php$ - [L]
    
    # uploaded files
    RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [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).*) $1 [L]
    RewriteRule  ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
    RewriteRule . index.php [L]
    </Directory> 
    
    # END WordPress
    
     
    Finally, edit /installdir/apps/wordpress/conf/httpd-app.conf. This file is the main application configuration file. Add here (if it wasn't) the htaccess.conf file, just writing the following line at the end of the file.
    Include "/installdir/apps/wordpress/conf/htaccess.conf"
    

    Now you just have to log in again to the WordPress Dashboard (http://your_server_address/wordpress/wp-admin) and you will see a new option called "Network Admin" in the upper right corner:

    step 7.png

    Inside you will be able to create new sites.

    result.png

    Help! I followed the instructions and now Wordpress does not work! How do I restore the backup files?

    Just copy the backup files over the modified ones.

    cp  /installdir/apps/wordpress/htdocs/wp-config.php.backup /installdir/apps/wordpress/htdocs/wp-config.php
    cp  /installdir/apps/wordpress/conf/htaccess.conf /installdir/apps/wordpress/conf/htaccess.conf
    

    This will disable all multisite-related functionality.

    Tag page (Edit tags)
    • No tags
    Pages that link here
    Page statistics
    196409 view(s), 86 edit(s) and 34494 character(s)

    Comments

    You must login to post a comment.

    Attach file

    Attachments

    FileSizeDateAttached by 
     domain-mapping-2.png
    Domain mapping www
    4.82 kB14:29, 28 Apr 2014AdminActions
     domain-mapping.png
    Domain mapping
    8.81 kB14:29, 28 Apr 2014AdminActions
     multisite-phpmyadmin.png
    Multisite database changes
    28.11 kB16:27, 8 Jan 2013AdminActions
     multisite-phpmyadmin2.png
    Multisite database changes
    30.24 kB16:28, 8 Jan 2013AdminActions
     multisite1.png
    multisite1
    88.9 kB11:48, 1 Feb 2013AdminActions
     multisite2.png
    multisite2
    64.54 kB12:02, 1 Feb 2013AdminActions
     multisite4.png
    multisite4
    79.52 kB12:01, 1 Feb 2013AdminActions
     multisite5.png
    multisite5
    58.98 kB12:24, 1 Feb 2013AdminActions
     multisite6.png
    multisite6
    81.41 kB12:25, 1 Feb 2013AdminActions
    newdomain.png
    wordpress multisite new domain
    26.7 kB11:05, 23 Mar 2012AdminActions
     newdomain1.png
    wordpress multisite new domain
    26.7 kB11:05, 23 Mar 2012AdminActions
     newdomain2.png
    wordpress multisite new domain
    29.42 kB11:01, 23 Mar 2012AdminActions
     wordpress-multisite-add.png
    WordPress Multisite Network add
    38.77 kB15:34, 10 Feb 2012AdminActions
     wordpress-multisite-edit.png
    WordPress Multisite Network edit
    38.53 kB15:34, 10 Feb 2012AdminActions
     wordpress-multisite.png
    WordPress Multisite Network
    37.03 kB15:17, 10 Feb 2012AdminActions
     wordpress-multisite2.png
    WordPress Multisite Network 2
    24.94 kB15:17, 10 Feb 2012AdminActions
     wordpress-multisite3.png
    WordPress Multisite Network domain
    22.94 kB15:17, 10 Feb 2012AdminActions
     wordpress-multisite4.png
    WordPress Multisite Network installation
    40.71 kB15:17, 10 Feb 2012AdminActions
     wordpressms1.png
    wordpressms1.png
    23.98 kB11:32, 13 Feb 2012AdminActions
     wordpressms10.png
    wordpressms10
    49.49 kB12:13, 13 Feb 2012AdminActions
     wordpressms4.png
    wordpressms4
    23.36 kB11:45, 13 Feb 2012AdminActions
     wordpressms5.png
    wordpressms5
    21.03 kB12:38, 13 Feb 2012AdminActions
     wordpressms6.png
    wordpressms6
    31.65 kB12:08, 13 Feb 2012AdminActions
     wordpressms8.png
    wordpressms8
    45.42 kB12:11, 13 Feb 2012AdminActions
     wordpressms9.png
    wordpressms9
    44.02 kB12:12, 13 Feb 2012AdminActions