Info: July 30, 2008 Posted by: admin 4 comments

WPMU Installation Problems

The full text post for WPMU Installation Problems is located here

In the installation process this week for a client…encountered some little tips that might help the installation process go a little bit easier for you.

No WPMU Website Defined on This Host

Firstly, a very common error message is No WPMU Website Defined on this Host.  Unfortunately, the codex is not completely clear on the fact that the MU autoinstaller has a function built into that created a wp-config file.  Even though the distribution package comes with a wp-config-sample.php as regular Wordpress does, it is not the same installation process to change the parameters in this file and rename it.  The same thing goes for the .htaccess file.  There is a .htaccess.dist that comes with the package.  Although both of these files are in the zip or tar.gz package, neither is actually utilized.  That’s right…you should have neither file, wp-config.php or an .htaccess file, these will be autocreated by the install.  You will be guided through entering your SQL details, logins, user, database, etc.

WPMU - Wordpress MU, Wordpress Multi-User

Installing WPMU in Root Directory

You might find that there are some issues with your host and the autoinstaller when attempting installing WPMU in the Root Directory.  The codex and searches don’t provide a ton of information on this.  Since the write properties of the directory that contain the WPMU files must be writeable, there are some issues with write permissions being blocked out and prohibited from change to allow for the write access.  This is the only way for the WPMU auto-install to work.  The easiest solution, obviously, if you encounter this, which you likely will, is to install MU in a directory, which can easily be changed in most cases for permissions via FTP.  Still looking for a good solution for installing WPMU in the root directory.  This had been done on a project, but it has been several years, so the notes seemed to have vanished.  It did work fine when installed in a directory however, which worked fine for the clients application due to the need for ability to enhance the main design of the site quite a bit which might be more limited with Multi-User.

WordPress MU Forums Tag: installation

Wildcard DNS, Subdirectory, WPMU Hosting

You will need to decide whether you want to utilize the subdirectory method or the folder option.  The difference is how the new blog sites created by users are accessed once a user is done creating a blog with WPMU.  Your host will have to activate Wildcard DNS should you wish the following type of address for a blog (if you have your own server, this article explains how to setup Wildcard DNS on Apache, otherwise, your host would do it):

musubdomain.domain.com

With a folder access installed in a separate directory, you would get something like this, which does not require the DNS Wildcard.  Some hosts may not support this.  The host, asmallorange.com which is listed on our Wordpress Hosting Page does.

sitedomain/directory/mu-user

WordPress MU Forums Tag: DNS Wildcard
  • Forget about wildchar dns.
    This is a simple trick to configure this.

    Create a subdomain
    *.yourdomainname and point it to the folder which the yourdomainname points to.

    Issue is solved.
    for eg : If yourdomainname.com points to folder
    public_html then create subdomain *.yourdomainname and point it to public_html

    this trick works with shared web hosting. I just now configured it in computerkid.info


    2009 02 09
  • The DNS wild card is needed when you are running in sub-domain mode.

    Without it blog.my.domain , blog2.my.domain, blog3.my.domain won't work as the names will not resolve. By default most DNS records are set up to handle my.domain and http://www.my.domain


    2007 10 26

WordPress MU Forums Tag: subdirectory

Professional WPMU Installation, Hosting, MU Developer Install

As always, we are happy to direct you where to go for WPMU hosting or for a Professional WPMU Install.