Bitnami WordPress Multisite

     

    IMPORTANT: WordPress Multisite requires that you 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 (known issue) 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.

    The 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.

    Is WordPress Multisite right for you?

    If you plan to have more than one WordPress-powered website or blog, there are different ways to accomplish this. One option is to install multiple independent WordPress instances on the same server. Another option is to install WordPress Multisite, which lets you create and manage multiple WordPress blogs/websites from a single WordPress instance.

    • WordPress Multisite might be a good option for you if you have multiple websites or blogs focused on the same industry or topic - for example, a network of food or travel blogs. In this scenario, WordPress Multisite lets you manage multiple websites from a common dashboard, and you have the added advantage of being able to share themes and plugins between your WordPress Multisite sites.
    • If, on the other hand, you have multiple websites or blogs, each with a different focus area, it would be better to use a separate WordPress instance for each website. This means, for example, that you would run one WordPress instance for your personal blog, another for your company website and a third for your family’s photoblog. This would maximize your flexibility and allow you to configure each WordPress website or blog differently, with independent themes, plugins and settings.

    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.

    How to configure WordPress Multisite?

    Common usage scenarios

    SCENARIO 1: You want multiple websites/blogs at subdomains of your primary domain eg. your primary domain is our-planets.com and you have separate websites/blogs at mercury.our-planets.com, mars.our-planets.com and earth.our-planets.com.

    SCENARIO 2: You want multiple websites/blogs at different domains eg. a website at our-planets.com and another at space-is-awesome.com.

    SCENARIO 3: You want a combination of the two previous scenarios eg. a primary domain at our-planets.com with separate blogs for Earth and Mars at earth.our-planets.com and mars.our-planets.com, another blog at space-is-awesome.com, and yet another blog at photos.space-is-awesome.com.

    The following sections will guide you through configuring WordPress Multisite to handle these different scenarios.

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

    This is a mandatory step regardless of how you plan to use WordPress Multisite.

    This section assumes that:

    • You have a working WordPress Multisite installation.
    • Your server has a static IP address.
    • You are able to log in to your server console using a tool like PuTTY (Windows) or SSH (Linux and Mac OS X).
    • You own at least one custom domain name for which you can configure DNS settings.

    The first step is to define the primary domain for your WordPress Multisite instance. To do this, choose your platform below and follow the instructions in the corresponding sub-section.

    Bitnami Hosting

    To define the primary domain, follow these steps:

    • Browse to the Bitnami Cloud Hosting dashboard and sign in if required using your Bitnami account.
    • Select the "Servers" menu item.
    • Select your server from the resulting list and click the "Manage" button.
    • Select the "Applications" tab.
    • Update the application domain by clicking the pencil icon and entering your custom domain name in the resulting input field. In this example, let's assume the primary domain is our-planets.com.

    • Click the "Update" button to save your changes.

    Google Cloud Platform / Microsoft Azure / AWS

    To define the primary domain, follow these steps:

    sudo./bnconfig --machine_hostname our-planets.com
    
    • The bnconfig tool runs automatically every time the server starts to reset the machine hostname to its IP address. Obviously this is undesirable when using a custom domain name, so you must also execute the following command to disable the bnconfig tool for subsequent restarts.
    sudo mv bnconfig bnconfig.disabled
    

    Native Installer

    To define the primary domain, follow these steps.

    On Linux:

    • Log in to your server console as root.
    • Change to the /opt/bitnami/apps/wordpress subdirectory (where /opt/bitnami is assumed to be the installation directory for your Bitnami WordPress Multisite stack). If you installed the stack to a different directory, modify the path accordingly.
    • Execute the following command to update the domain name.  In this example, let's assume the primary domain is our-planets.com.
    sudo ./bnconfig --machine_hostname our-planets.com
    

    On Windows:

    • Open a Windows Command Prompt with the “Run as administrator” option
    • Change to the apps/wordpress subdirectory of your WordPress Multisite installation directory.
    • Execute the following command to update the domain name.  In this example, let's assume the primary domain is our-planets.com.
    bnconfig.exe --machine_hostname our-planets.com
    

    Virtual Machine

    To define the primary domain, follow these steps:

    • Log in to your virtual machine console
    • Change to the /opt/bitnami/apps/wordpress directory.
    • Execute the following command to update the domain name.  In this example, let's assume the primary domain is our-planets.com.
    sudo./bnconfig --machine_hostname our-planets.com
    
    • The bnconfig tool runs automatically every time the server starts to reset the machine hostname to its IP address. Obviously this is undesirable when using a custom domain name, so you must also execute the following command to disable the bnconfig tool for subsequent restarts.
    sudo mv bnconfig bnconfig.disabled
    

    Tabs end

    At this point, you also need to update your domain's DNS settings, specifically adding an A record that points your domain to the static IP address of your cloud server. If you're in a hurry, or just testing things out, you can instead modify your local hosts file to map your domain to your server's IP address. For more information on both these options, refer to the section on testing your installation.

    Following these changes, entering your custom domain name into the browser address bar should take you to the WordPress Multisite default blog, as shown below:


    You should also be able to log in to the WordPress dashboard by visiting http://[your-domain-name]/wp-login.php. To obtain access credentials, select your platform and follow the steps listed:

    Bitnami Hosting

    • Browse to the Bitnami Cloud Hosting dashboard and sign in if required using your Bitnami account.
    • Select the "Servers" menu item.
    • Select your server from the resulting list and click the "Manage" button.
    • Select the "Properties" tab.
    • Select "Show" under "Application Credentials".

    Google Cloud Platform / Microsoft Azure

    If you’re using the Bitnami Launchpad for Google Cloud Platform:

    • Browse to the Bitnami Launchpad for Google Cloud Platform dashboard and sign in if required using your Bitnami account.
    • Select the "Virtual Machines" menu item.
    • Select your WordPress Multisite server from the resulting list.
    • Obtain credentials by selecting "Show" under "Credentials".

    If you’re using the Bitnami Launchpad for Microsoft Azure:

    • Browse to the Bitnami Launchpad for Microsoft Azure dashboard and sign in if required using your Bitnami account.
    • Select the "Virtual Machines" menu item.
    • Select your WordPress Multisite server from the resulting list.
    • Obtain credentials from the “Application Info" panel.

    Native Installer

    Use the access credentials you configured when installing the application.

    Virtual Machine

    Log in with the username “user” and password “bitnami”.

    Tabs end

    If you have problems with redirection when you log in to the WordPress dashboard, check that the domain was successfully updated in these database tables:

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

    An easy way to check these database tables is with phpMyAdmin (instructions).

    Then, clear your browser cache and try to log in again to the application. Remember that if you are using an IP address instead of a domain name, you will have problems with some browsers; it is advisable to use the custom domain name only.

    You can now choose from the following sections based on your requirements.

    How to add several WordPress Multisite blogs with subdomains?

    This section assumes that:

    • You have a working WordPress Multisite installation.
    • Your server has a static IP address.
    • You are able to log in to your server console using a tool like PuTTY (Windows) or SSH (Linux and Mac OS X).
    • You own at least one custom domain name for which you can configure DNS settings.
    • You have defined your primary domain and blog as described in the previous section and you are able to log in to the WordPress Multisite dashboard.

    WordPress Multisite is designed for subdomains, so it's easy to add a separate blog for each subdomain of your primary domain (Scenario 1). In this example, let's assume we're adding two blogs: earth.our-planet.com and mars.our-planet.com.

    Follow these steps to associate a new blog with a subdomain:

    • In the WordPress Multisite dashboard, select the "My Sites -> Network Admin -> Sites" option.

    • Select "Add New" to add a new blog.
    • Enter the subdomain name (the primary domain will already be filled in), together with a site title and administrator email address.

    • Click "Add Site" to create the new blog or website.

    Repeat the above steps for all the subdomains and blogs you wish to create. Once you're done, you can see a list by selecting the "My Sites -> Network Admin -> Sites" option.
     


    At this point, you also need to update your domain's DNS settings, specifically adding A records for your subdomains that point to the static IP address of your cloud server. If you're in a hurry, or just testing things out, you can instead modify your local hosts file to map each subdomains to your server's IP address. For more information on both these options, refer to the section on testing your installation.

    Following these changes, entering the subdomain name into the browser address bar should take you to the blog for that subdomain, as shown below:
     

    How to add several WordPress Multisite blogs with different domains?

    This section assumes that:

    • You have a working WordPress Multisite installation
    • Your server has a static IP address
    • You are able to log in to your server console using a tool like PuTTY (Windows) or SSH (Linux and Mac OS X)
    • You own at least one custom domain name for which you can configure DNS settings
    • You have defined your primary domain and blog as described in the previous section and you are able to log in to the WordPress Multisite dashboard.

    The WordPress MU Domain Mapping plugin allows users of a WordPress Multisite installation to map their blogs or websites to other domains or subdomains (Scenarios 2 and 3). This plugin is already installed in your Bitnami WordPress Multisite stack since v3.5.1-1. If you're using an older version, you must manually install the plugin using this plugin installation guide.

    First, you must activate and configure the WordPress MU Domain Mapping plugin as follows:

    • In the WordPress Multisite dashboard, select the "My Sites -> Network Admin -> Plugins" option.
    • Find the plugin named "WordPress MU Domain Mapping" and select "Network Activate" to activate it.

    • In the same dashboard, select the "Settings -> Domain Mapping" option.
    • Enable the "Permanent redirect" option. This makes your blogs redirect to their mapped domains.


    In this example, let's assume we're adding a blog for the domain space-is-awesome.com. Create and associate a new blog for the domain as follows:

    • In the WordPress Multisite dashboard, select the "My Sites -> Network Admin -> Sites" option.
    • Select "Add New" to add a new blog.
    • Enter the new domain name (ignore the primary domain which will appear as a suffix), together with a site title and administrator email address.

    • Click "Add Site" to create the new blog.
    • Select the "My Sites -> Network Admin -> Sites" option and you should see the new blog in the list.
    • Hover over the new blog's name in the list, you will see that the URL for the blog includes a numeric site ID. Make a note of the site ID, as you will need it in the next step.

    NOTE: You can also obtain the numeric site ID from the “wp_blogs” table in the database. An easy way to check this database table is with phpMyAdmin (instructions).

    • In the WordPress Multisite dashboard, select the "Settings -> Domains" option.
    • Associate the new blog with the domain by entering the new blog's site ID together with the domain name in the fields provided.

    • Save the association by clicking "Save".

    Repeat these steps for each domain or subdomain you wish to associate with a separate blog. Once you're done, select the "My Sites -> Network Admin -> Sites" option and verify the domain mapping for each blog.

    Depending on your platform, you might need to perform additional steps. Choose your platform below and proceed according to the instructions provided.

    Bitnami Hosting

    Configure your Apache server to handle the new domains, by creating a wildcard alias. To do this, log in to your server terminal and follow these steps:

    • Edit the /opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf file and modify the ServerName and ServerAlias entries to look like this, remembering to replace the example domain name with your custom domain name.
    ServerName our-planets.com
    ServerAlias *
    
    • Restart the Apache server.
    sudo /opt/bitnami/ctlscript.sh restart apache
    


    After you make the changes above, you might find that other applications on the same server redirect to your WordPress Multisite primary blog. To correct this, refer to the next section.

    Support Other Applications on the Same Server

    NOTE: This section is only applicable if you want to configure WordPress Multisite for multiple domain names on Bitnami Cloud Hosting and if you also have other applications running on the server.

    Bitnami Cloud Hosting lets you create a server with WordPress Multisite running together with other applications. These applications are usually running on the server under directory paths like http://[domain]/[app] - for example /redmine or /phpmyadmin. In this scenario, after you configure WordPress Multisite to use more than one domain, you might find that other applications on the server are also redirected to your primary domain blog.

    To correct this, log in to your server terminal and perform these additional steps:

    • Edit the /opt/bitnami/apache2/conf/bitnami/bitnami.conf file and and specify the ServerName directive to avoid other applications from being redirected to your WordPress Multisite instance. Remember to replace the example server name below with the actual DNS name of your server, which you can obtain from the Bitnami Cloud Hosting dashboard.
    <VirtualHost _default_:80>
        ServerName example-server-a1234.bitnamiapp.com
        ServerAlias localhost
        ...
    </VirtualHost>
    
    <VirtualHost _default_:443>
        ServerName example-server-a1234.bitnamiapp.com
        ServerAlias localhost
       ...
    </VirtualHost>
    
    • Restart the Apache server.
    sudo /opt/bitnami/ctlscript.sh restart apache
    

    Google Cloud Platform / Microsoft Azure

    There are no platform-specific steps.

    Native Installer

    There are no platform-specific steps.

    Virtual Machine

    There are no platform-specific steps.

    Tabs end

    At this point, you also need to update each domain or subdomain's DNS settings, specifically adding A records that point them to the static IP address of your cloud server. If you're in a hurry, or just testing things out, you can instead modify your local hosts file to map each domain or subdomain to your server's IP address. For more information on both these options, refer to the section on testing your installation.

    Following these changes, entering the domain name into the browser address bar should take you to the associated blog, as shown below:


    You might find that although you're now able to access the new blog using the domain or subdomain name, you're not able to access the blog's dashboard. Typically, this is because WordPress still considers the new site to be a subdomain of the primary domain and tries to access it using a invalid URL (following the above example, space-is-awesome.our-planets.com). To resolve this, you can either update the DNS records for your primary domain and add an A record for this subdomain, or you can edit the entry for the site in the "My Sites -> Network Admin -> Sites" list and modify the domain URL, as shown below:
     

    How to test WordPress Multisite?

    Testing with DNS

    As a general rule, every domain or subdomain that you use in WordPress Multisite should have a DNS entry pointing to your server. This requires a change to each domain's DNS settings, specifically the addition of an A record that points the domain to the static IP address of your server.

    This change can only be accomplished through your domain name provider; it cannot be made through Bitnami's hosting dashboard or through local commands on your server. You will therefore need to log in to your domain name provider's management console and make the necessary changes. Step-by-step instructions for some popular providers are listed below:

    Remember that once you make the necessary changes, it can take up to 48 hours for the change to propagate across other DNS servers. You can verify the new DNS record by using the Global DNS Propagation Checker and entering your domain name into the search field.

    Testing with the hosts File

    Given that DNS propagation takes some time, you can use a shortcut to test that your WordPress Multisite installation is working correctly. The shortcut involves manually adding entries for your domain(s) and subdomain(s) in your local system's hosts file, which is always checked before a query is sent to a DNS server.

    To do this, open the file C:\Windows\system32\drivers\etc\hosts (on Windows) or /etc/hosts (on Linux and Mac OS X) in a text editor and add a line like the one below to it.

    54.224.97.204       our-planets.com
    

    Remember to update the IP address on the left to reflect the IP address of your server, and the domain name on the right to reflect the domain or subdomain you wish to test. If you have multiple domains to test, add a separate line for each domain.

    Once done, save the file. This takes care of mapping the our-planets.com domain name to the IP address 54.224.97.204.

    If you now open your browser and type in the URL to your domain, such as http://our-planets.com, it should redirect to your server.

    NOTE: On some versions of Windows, you will not be able to edit the C:\Windows\system32\drivers\etc\hosts file without administrator privileges. You can edit the file by right-clicking the Notepad icon and selected the "Run as administrator" menu option, then entering administrator credentials (if required) and clicking "OK" or "Yes" to proceed.

    NOTE: On Mac OS X, you can edit the /etc/hosts file with the following command in a terminal:

    sudo nano /etc/hosts
    

    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.

     

    How to add more than one user to httpd authentication file?

    If you want to let more than one person in, you'll need to create a group file. This group file associates a group name with a list of persons in that group and has the following syntax:

    GroupName: bitnami user admin user2
    

    Now you should add the user to your password file

    $ htpasswd /path/to/your/password_file user2
    

    The last thing you should do is modify the apache configuration and then restart the server.

    AuthTypeBasic
    AuthName"By Invitation Only"
    # Optional line:
    AuthBasicProvider file
    AuthUserFile /path/to/your/password_file
    AuthGroupFile/path/to/your/groups_file
    Require group GroupName
    

    * Remember use the correct path to your password and group files.

    Tag page (Edit tags)
    • No tags
    Pages that link here
    Page statistics
    252964 view(s), 107 edit(s) and 51308 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
     image1.jpg
    No description
    37.69 kB14:55, 11 Dec 2014vikramActions
     image1.png
    No description
    14.08 kB12:59, 11 Dec 2014vikramActions
     image10.jpg
    No description
    51.6 kB14:59, 11 Dec 2014vikramActions
     image10.png
    No description
    18.74 kB13:39, 11 Dec 2014vikramActions
     image11.jpg
    No description
    37.27 kB14:59, 11 Dec 2014vikramActions
    image11.png
    No description
    13.99 kB13:43, 11 Dec 2014vikramActions
     image12.jpg
    No description
    55.43 kB15:00, 11 Dec 2014vikramActions
     image12.png
    No description
    17.98 kB13:41, 11 Dec 2014vikramActions
     image13.jpg
    No description
    47.91 kB15:01, 11 Dec 2014vikramActions
     image13.png
    No description
    20.09 kB13:43, 11 Dec 2014vikramActions
     image14.jpg
    No description
    50.58 kB15:01, 11 Dec 2014vikramActions
     image14.png
    No description
    25.12 kB13:44, 11 Dec 2014vikramActions
     image2.jpg
    No description
    73.65 kB14:55, 11 Dec 2014vikramActions
     image2.png
    No description
    28.66 kB13:00, 11 Dec 2014vikramActions
     image3.jpg
    No description
    42.3 kB14:55, 11 Dec 2014vikramActions
     image3.png
    No description
    13 kB13:29, 11 Dec 2014vikramActions
    image4.jpg
    No description
    48.58 kB14:57, 11 Dec 2014vikramActions
     image4.png
    No description
    18.94 kB13:30, 11 Dec 2014vikramActions
     image5.jpg
    No description
    35.67 kB14:56, 11 Dec 2014vikramActions
     image5.png
    No description
    14.69 kB13:30, 11 Dec 2014vikramActions
     image6.jpg
    No description
    60 kB14:58, 11 Dec 2014vikramActions
     image6.png
    No description
    117.25 kB13:31, 11 Dec 2014vikramActions
     image7.jpg
    No description
    106.47 kB14:58, 11 Dec 2014vikramActions
     image7.png
    No description
    24.17 kB13:37, 11 Dec 2014vikramActions
     image8.jpg
    No description
    72.5 kB14:58, 11 Dec 2014vikramActions
     image8.png
    No description
    18.97 kB13:37, 11 Dec 2014vikramActions
     image9.jpg
    No description
    47.39 kB14:59, 11 Dec 2014vikramActions
     image9.png
    No description
    15.37 kB13:38, 11 Dec 2014vikramActions
     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