Legacy Documentation

Installation Instructions:

  1. Setup your first site according to WP standard instructions.
  2. Install and activate the WP Hive plugin through the Plugins menu in WordPress
  3. To add a new site, go to WP Admin > WP Hive > Add new and add any site you want.
  4. Run the WP Install for the new site by clicking “Install Site”.

If you are adding a new domain or subdomain, you must also point it (using DNS and webserver) to the directory that contains index.php. Subdirectory sites can be added at will,  without making changes to the webserver.

.htaccess

WP Hive must write some content to the .htaccess file in order to support subdirectory sites. It is important that after installing WordPress and WP Hive in the root domain that you setup pretty permalinks from the root site (http://domain.com). After the saving the permalink structure, you must make .htaccess read-only.  If you do not, then you will run into problems when you try to change the permalink structure for a subdirectory site.  This can potentially be fixed in a future version, but depends on a small change to WordPress Core (Trac Ticket # 14549).

Existing Subdirectory Installations

If you have set up a subdirectory installation using WP Hive V 0.5.x, you will need to check the following settings (in order):

1. For each subdirectory site, ensure the WordPress Address and Site Address options are set to the same value. For example: http://domain.com/subdirectory. This can be accessed via WP-Admin > Settings > General. This may appear to break your sites, but the next step will fix them.

2. Regenerate your .htaccess file by saving your permalinks from the root site (http://domain.com). This can be accessed via WP-Admin > Settings > Permalinks.

If you regenerate your .htaccess too early, the wp-admin on subdirectory sites could become unreachable. In this case, you may need to update options manually in the database.  See this post for details.

Write Permissions

The /wp-content/ directory must be writable during the installation process.
.htaccess should be writable when you first save the permalinks, and then should be made read-only.

WordPress Multisite

WP Hive and WordPress Multisite are not compatible.  It is not advised to attempt to set up a Multisite installation on any sites running on WP Hive, and vice-versa.

WordPress in its own directory

WP Hive does not support hosting WordPress as a separate directory. You must install WordPress in the root of the domain. For Example: http://domain.com/ is OK but http://domain.com/wp/ is not OK.  After you set up WP Hive on your root directory, you may add subdirectory sites at will.

Special Files

The files sitemap.xml, sitemap.xml.gz, robots.txt, and favicon.ico are treated specially. They are normally stored in the root directory, but since each blog shares the same root directory, they must be moved and properly handled.

  1. Ensure these files DO NOT exist in the root directory.
  2. For each domain that uses one or more of these files, save them in the directory: /wp-content/wp-hive/domainname.com/ (eg: /wp-content/wp-hive/domainname.com/robots.txt).
  3. The plugin ensures any external entity will access these file using the normal method (eg: http://www.yourdomain.com/robots.txt).

Note: If you use the ‘Google XML Sitemaps’ plugin, you can manually set the location of the sitemap file in the plugin configuration.

Deactivation

Deactivate the WP Hive plugin through the Plugins menu in WordPress.

Removal

To completely remove the plugin, deactivate as above, then manually remove the wphive-config and wphive-hosts tables from the database.