[Summary view] [Print] [Text view]

   1  WordPress Multi User
   2  --------------------
   3  
   4  WordPress MU is a multi user version of WordPress.
   5  
   6  If you're not comfortable editing PHP code, taking care of a complex
   7  webserver and database system and being pro-active about following
   8  developments of this project then run, don't walk, to 
   9  http://wordpress.com/ and sign yourself and your friends up to free blogs.
  10  It's easier in the long run and you'll save yourself a lot of pain
  11  and angst.
  12  
  13  Apache
  14  ======
  15  Apache must be configured so that mod_rewrite works. Here are 
  16  instructions for Apache 2. Apache 1.3 is very similar.
  17  
  18  1. Make sure a line like the following appears in your httpd.conf
  19  LoadModule rewrite_module /usr/lib/apache2/modules/mod_rewrite.so
  20  
  21  2. In the <Directory> directive of your virtual host, look for this
  22  line
  23  "AllowOverride None"
  24  and change it to
  25  "AllowOverride FileInfo Options"
  26  
  27  3. In the <VirtualHost> section of the config file for your host there
  28  will be a line defining the hostname. You need to add the following 
  29  if you want virtual hosts to work properly:
  30  "ServerAlias *.domain.tld"
  31  Replace domain.tld with whatever your one is, and remove the quotes.
  32  
  33  
  34  DNS
  35  ===
  36  If you want to host blogs of the form http://blog.domain.tld/ where 
  37  domain.tld is the domain name of your machine then you must add a 
  38  wildcard record to your DNS records.
  39  This usually means adding a "*" hostname record pointing at your 
  40  webserver in your DNS configuration tool.
  41  Matt has a more detailed explanation:
  42  http://ma.tt/2003/10/10/wildcard-dns-and-sub-domains/
  43  
  44  
  45  PHP
  46  ===
  47  1. Don't display error messages to the browser. This is almost always
  48  turned off but sometimes when you're testing you turn this on and forget
  49  to reset it.
  50  
  51  2. If your PHP is compiled with memory limit checks, the default is 8MB
  52  which is much too small. You should increase this to at least 32MB or 64MB
  53  to avoid PHP out of memory errors. Look for "memory_limit" in your php.ini
  54  file.
  55  
  56  3. GLOBAL variables must be turned off. This is one of the first things
  57  any security aware admin will do. These days the default is for it to
  58  be off!
  59  
  60  The easiest way of configuring it is via the .htaccess file that is
  61  created during the install. If you haven't installed WPMU yet then edit
  62  the file htaccess.dist in this directory and add these two lines at the
  63  top:
  64  
  65  php_flag register_globals 0
  66  php_flag display_errors 0
  67  
  68  This is NOT included in that file by default because it doesn't work on
  69  all machines. If it doesn't work on your machine, you'll get a cryptic
  70  "500 internal error" after you install WPMU. To remove the offending lines
  71  just edit the file ".htaccess" in your install directory and you'll see
  72  them at the top. Delete and save the file again.
  73  Read here for how to enable this: http://ie.php.net/configuration.changes
  74  
  75  If you don't want to edit your .htaccess file then you need to change your
  76  php.ini. It's beyond the scope of this README to know exactly where it is
  77  on your machine, but if you're on a shared hosted server you probably
  78  don't have access to it as it requires root or administrator privileges
  79  to change.
  80  
  81  If you do have root access, try "locate php.ini" or check in:
  82  
  83  /etc/php4/apache2/php.ini
  84  /usr/local/lib/php.ini
  85  
  86  Once you have opened your php.ini, look for the sections related to 
  87  register_globals and display_errors. Make sure both are Off like so:
  88  
  89  display_errors = Off
  90  register_globals = Off
  91  
  92  You'll have to restart Apache after you modify your php.ini for the 
  93  settings to be updated.
  94  
  95  4. If you want to restrict blog signups, set the restrict domain email 
  96  setting in the admin.
  97  
  98  
  99  Install
 100  =======
 101  1. Download and unzip the WordPress MU package, if you haven't already.
 102     The unzipped files will be created in a directory named "wordpressmu"
 103     followed by a version number.
 104  2. Create a database for WordPress MU on your web server, as well as a 
 105     MySQL user who has all privileges for accessing and modifying it.
 106  3. Place the WordPress MU files in the desired location on your web server:
 107     * If you want to integrate WordPress MU into the root of your 
 108       domain (e.g. http://example.com/), move or upload all the files and
 109       directories of the unzipped WordPress MU directory into the root 
 110       directory of your web server.
 111     * If you want to have your WordPress MU installation in its own 
 112       subdirectory on your web site (e.g. http://example.com/blogs/), 
 113       rename the directory wordpressmu to the name you'd like the 
 114       subdirectory to have and move or upload it to your web server. 
 115       For example if you want the WordPress MU installation in a 
 116       subdirectory called "blog", you should rename the directory called 
 117       "wordpressmu" to "blogs" and upload it to the root directory of your 
 118       web server. 
 119  4. Make sure your install directory and the wp-contents directory are
 120     writeable by the webserver.
 121  5. Run the WordPress MU installation script by accessing index.php
 122     in your favorite web browser.
 123     * If you installed WordPress MU in the root directory, you should 
 124       visit: http://example.com/index.php
 125     * If you installed WordPress MU in its own subdirectory called 
 126       blogs, for example, you should visit: http://example.com/blogs/index.php 
 127  (Adapted from http://codex.wordpress.org/Installing_WordPress)
 128  
 129  If you're upgrading, skip to the end of this document.
 130  
 131  ERROR LOGGING
 132  =============
 133  If you are developing a site based on WPMU it is recommended that you
 134  turn on PHP error logging. Look in your php.ini for the section marked
 135  "Error handling and logging" where you can configure it.
 136  
 137  Mysql database errors are logged to the PHP error log if enabled or it
 138  can also send error reports to a file of your choice. After installing,
 139  edit wp-config.php and define a constant, "ERRORLOGFILE", pointing at
 140  your MySQL error log. This file must be writeable by your webserver.
 141  Please don't log to a file visible by your webserver or people may 
 142  figure out they can download it.
 143  Example definition:
 144  define( "ERRORLOGFILE", "/tmp/mysql.log" );
 145  
 146  
 147  UPGRADING
 148  =========
 149  Please see this page for instructions on upgrading your install:
 150  http://codex.wordpress.org/Upgrading_WPMU
 151  
 152  
 153  PERFORMANCE
 154  ===========
 155  WordPress MU has a caching framework which allows third party developers
 156  to create cache engines that improve performance. 
 157  There are two types of caching plugins available for WordPress. 
 158  
 159  1. Object Cache.
 160  These work by storing commonly accessed data in a rapid access storage
 161  container such as RAM or directly on the filesystem. 
 162  To install these plugins copy them into your wp-content folder.
 163  Memcached: http://dev.wp-plugins.org/browser/memcached/trunk/
 164  Filesystem: http://neosmart.net/dl.php?id=14
 165  Xcache: http://neosmart.net/dl.php?id=12
 166  eAccelerator: http://neosmart.net/dl.php?id=13
 167  
 168  2. Full page cache. 
 169  These work by storing complete web pages and are generally faster than 
 170  object cache plugins at the expense of less flexibility. On a busy
 171  WordPress MU site these may in fact slow down your server due to 
 172  limitations in how the cached files are stored. Clearing out the cached
 173  files on a regular basis will alleviate this problem. YMMV.
 174  WP Super Cache: http://ocaoimh.ie/wp-super-cache/
 175  
 176  
 177  Support Forum and Bug Reports
 178  =============================
 179  Please read http://codex.wordpress.org/Debugging_WPMU before
 180  asking any questions. Without all the information required there
 181  we'll just ask for it anyway or worse, your request will be ignored.
 182  
 183  http://mu.wordpress.org/forums/
 184  
 185  Trac is our bug tracking system. Again, please read the above link
 186  before submitting a bug report.
 187  http://trac.mu.wordpress.org/report/1
 188  
 189  You can login to both sites using your wordpress.org username and
 190  password.
 191  
 192  http://mu.wordpress.org/