WordPress.org

Ready to get started?Download WordPress

Forums

Installing Multisite on Media Temple DV Server (not resolving) (3 posts)

  1. efschilling
    Member
    Posted 3 years ago #

    I've installed wordpress multi-site at uptownboston.mobi. The Network Admin interface seems to be correctly installed. I'm able to go into WordPress multisite and create a subdomain. I've created 2 subdomains: tailgate.uptownboston.mobi & baronassociate.uptown.mobi.

    The problem I'm having is the pages aren't resolving correctly. I get an Apache error page when I try to load the subdomains.

    There are two codex at WordPress I referenced to install multisite. They were 1) http://codex.wordpress.org/Create_A_Network
    &
    2) http://codex.wordpress.org/Configuring_Wildcard_Subdomains_for_multi_site_under_Plesk_Control_Panel

    There are apparently issues with installing multisite under Plesk and so the 2nd codex above addresses that topic.

    I did Steps 1 & 2 on Codex #1 above and then went to Codex #2 above to do the "Plesk workaround".

    I then went back to Codex #1 above and finished steps 3, 4, 5, 6.

    There are two areas I had trouble with. First is the verbiage that came before step1. And the verbiage that came after step 6.

    Here's the initial verbiage: (and I just don't know if the DV server is set up for wordpress multisite.)

    Admin Requirements

    If you want to run a network of blogs you should at least have a basic understanding of UNIX/Linux administration. A basic knowledge of WordPress development, PHP, HTML and CSS is recommended as well.

    Setting up and running a multi-site installation is more complex than a single-site install. Reading this page should help you to decide if you really need a multi-site install, and what might be involved with creating one. If the instructions on this page make no sense to you, be sure to test things on a development site first, rather than your live site.
    Server Requirements

    Since this feature requires extra server setup and more technical ability, please check with your webhost and ask if they support the use of this feature. It is not recommended to try this on shared hosting.

    You are given the choice between sub-domains or sub-directories in Step 4: Installing a Network. This means each additional site in your network will be created as a new virtual subdomain or subdirectory.

    * Sub-domains -- like site1.example.com and site2.example.com
    * Sub-directories -- like example.com/site1 and example.com/site2

    It is also possible later, through use of a plugin such as WordPress MU Domain Mapping, to map individual sites to independent domain names.

    Here is the verbiage after Step 6: (There is some talk about an Apache Virtual Server and I think that's what the DV is, but I don't know how to apply or if I should apply this info to my server.

    Things You Need To Know

    Here are some additional things you might need to know about advanced administration of the blog network.
    User Access

    By design, all users who are added to your network will have subscriber access to all sites on your network.

    Also, site admins cannot install new themes or plugins. Only the Network Admin (aka Super Admin) has that ability.
    Permalinks

    While permalinks will continue to work, the main blog (i.e. the first one created) will have an extra entry of blog, making your URLs appear like domain.com/blog/YYYY/MM/POSTNAME.

    This is by design, in order to prevent collisions with SubFolder installs. Currently there is no easy way to change it, as doing so prevents WordPress from auto-detecting collisions between your main site and any subsites. This will be addressed, and customizable, in a future version of WordPress.

    Also note that the blog prefix is not used for static pages which will be accessible directly under the base address, e.g. domain.com/PAGENAME. If you try to create a static page in the first blog with the name of another existing blog, the page's permalink will get a suffix (e.g. domain.com/PAGENAME-2). If you create a new blog with the slug of an existing static page, the static page will not be reachable anymore. To prevent this, you can add the names of your static pages to the blacklist so that no blog with this name can be created.
    WordPress Plugins

    WordPress Plugins now have additional flexibility, depending upon their implementation across the network.

    * Site Specific Plugins: WordPress Plugins to be activated or deactivated by an individual blog owner are stored in the plugins directory. You need to enable the Plugins page for individual site administrators from Network > Options.
    * Network Plugins: WordPress Plugins stored in the plugins directory can be activated across the network by the super admin.
    * Must-Use Plugins: Plugins to be used by all sites on the entire network may also be installed in the mu-plugins directory as single files, or a file to include a subfolder. Any files within a folder will not be read. These files are not activated or deactivated; if they exist, they are used.

    Categories and Tags

    Global terms are disabled in WordPress 3.0 by default. You can use the Sitewide Tags WordPress Plugin or other similar Plugins to incorporate global tags on the portal/front page of the site or on specific pages or blogs within the network to increase navigation based upon micro-categorized content.

    Switching between subdomains and subfolders

    If you have had WordPress installed for longer than a month and are attempting to activate the network, you will be told to use Sub-domain sites. This is in order to ensure you don't have conflicts between pages (i.e. example.com/pagename ) and sites (i.e. example.com/sitename ). If you are confident you will not have this issue, then you can change this after you finish the initial setup.

    In your wp-config.php file, you'll want to change the define call for SUBDOMAIN_INSTALL:

    Use SubDomains

    define( 'SUBDOMAIN_INSTALL', true );

    Use SubFolders

    define( 'SUBDOMAIN_INSTALL', false );

    You'll also have to change your .htaccess to the new setup. Be aware, you may have issues if you attempt this after being on one setup or the other for any length of time, so proceed with caution.

    Note that per the Settings Requirements you cannot switch from Sub-folder to Sub-domain when running on 127.0.0.1 or localhost. This can potentially cause an endless loop of reauth=1 on your root site due to cookie handling.
    Apache Virtual Hosts and Mod Rewrite

    To enable mod_rewrite to work within an Apache Virtual host you may need to set some options on the DocumentRoot.

    <VirtualHost *:80>
    DocumentRoot /var/www/vhosts/wordpress
    <Directory /var/www/vhosts/wordpress>
    AllowOverride Fileinfo Options
    </Directory>

    .htaccess and Mod Rewrite

    Unlike Single Site WordPress, which can work with "ugly" Permalinks and thus does not need Mod Rewrite, MultiSite requires its use to format URLs for your subsites. This necessitates the use of an .htaccess file, the format of which will be slightly different if you're using SubFolders or SubDomains. The examples below are the standard .htaccess entries for WordPress SubFolders and SubDomains, when WordPress is installed in the root folder of your website. If you have WordPress in it's own folder, you will need to change the value for RewriteBase appropriately.

    As a reminder, these are EXAMPLES and work in most, but not all, installs.

    SubFolder Example

    # BEGIN WordPress
    RewriteEngine On
    RewriteBase /
    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]
    # END WordPress

    SubDomain Example

    # BEGIN WordPress
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]

    # uploaded files
    RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ - [L]
    RewriteRule . index.php [L]
    # END WordPress

    Issues with old WPMU installs

    If you installed WordPress MU in subfolder/subdirectory (not in root folder on your server via ftp) and you have problem with image library, where thumbnails and images do not show, you may need to manually add in rewrite rules for your blogs file directories as follows:

    RewriteRule ^([_0-9a-zA-Z-]+/)?blogN/files/(.+) wp-content/blogs.dir/N/files/$2 [L]

    Put those below the normal call for uploaded files.
    Importing into WordPress Network

    When you've created your WordPress Network to import other blogs into, you need to look at the Migrating Multiple Blogs into WordPress Multisite article.

    CONCLUSION:

    I know this is "outside the scope" of what you do, however, I think the WordPress Multisite has a lot of growth potential and the will be many more people like me trying to build wordpress multisites at MT so I think as a cost benefit analysis you'd probably make your time back!!

    Thanks,

    David

  2. Please don't post the contents of a page we can go read ourselves.

    Ask MT support about setting up wildcard subdomains on their servers.

    All of us here - including mods - are volunteers. So not sure what you mean about the cost/benefit analysis. The only thing I get back is karma.

  3. Christopher Spires
    Member
    Posted 3 years ago #

    MT support will probably just direct you to this community article, which might prove helpful: http://wiki.mediatemple.net/w/(dv):Configure_a_wildcard_subdomain

Topic Closed

This topic has been closed to new replies.

About this Topic