Davidherron's List: Wordpress

• Note: For this tutorial, I will be using the WordPress MU Domain Mapping plugin. However, I am using the trunk version of the plugin. It has fixes in it that you will need for proper 3.0 support. Don’t try it with the regular version. (Note: The regular version works fine. This was originally written before the latest version, or 3.0, was released.)

   
• Now you have to configure the domain mapping plugin so that it knows what it’s doing properly. This is easy to do, really. Go to your main domain’s admin page and log in as a super admin. Then go to the new Super Admin->Domain Mapping menu.

• WordPress MU Domain Mapping

   

  Map any blog/site on a WordPressMU or WordPress 3.0 network to an external domain.
• This plugin allows users of a WordPress MU site or WordPress 3.0 network to map their blog/site to another domain.

• It requires manual installation as one file must be copied to wp-content/. When upgrading the plugin, remember to update domain_mapping.php and sunrise.php. Full instructions are on the Installation page and are quite easy to follow. You should also read this page too.

    

  Super administrators must configure the plugin in Super Admin->Domain Mapping. You must enter the IP or IP addresses (comma deliminated) of your server on this page. The addresses are purely for documentation purposes so the user knows what they are (so users can set up their DNS correctly). They do nothing special in the plugin, they're only printed for the user to see.

• You may also define a CNAME on this page. It will most likely be the domain name of your network. See below for some restrictions and warnings.

    

  Your users should go to Tools->Domain Mapping where they can add or delete domains. One domain must be set as the primary domain for the blog. When mapping a domain, (like 'example.com') your users must create an A record in their DNS pointing at that IP address. They should use multiple A records if your server uses more than one IP address. If your user is mapping a hostname of a domain (sometimes called a "subdomain") like http://www.example.com or blog.example.com it's sufficient to create a CNAME record pointing at their blog url (NOT IP address).

• The login page will almost always redirect back to the blog's original domain for login to ensure the user is logged in on the original network as well as the domain mapped one. For security reasons remote login is disabled if you allow users to use their Dashboard on the mapped domain.

    

  Super admins can now choose to either allow users to setup DNS ANAME records by supplying an IP (or list of IP addresses) or set a CNAME but not both (entering a CNAME for the end user voids the use of IP's)

3 more annotations...

• Since Version 3.0, WordPress includes new multisite features, meaning that it can run many blogs, even with their own separate domains, on one WordPress installation. This tutorial explains how to migrate multiple WordPress installations into one new WordPress multisite. You can migrate sites that are using their own domain, as well as sites using a subdomain on your main domain.

• As of WordPress 3.0, you have the ability to create a network of sites (Multisite). This article is instructions for creating a network. It is very similar to creating your own personal version of wordpress.com.

• Requires at least: WordPress 2.9
   Tested up to: WordPress 3.0-beta
    Current latest version: v2.21
   Download: Latest version from official WordPress plugin site

• Post Control gives you complete control over your write options for every user level/role in WordPress. It not only allows you to hides unwanted items like custom fields, trackbacks, revisions etc. but also gives you a whole lot more control over how WordPress deals with creating content.

   

  Simplify the and customise the write post and page areas of WordPress and just show the controls you need. Great for de-cluttering – do you really need those pingback and trackback options… now you can decide what users can see and use!

   

  You can also disable autosaves, revisions and disable the Flash uploader.

   

  New to version 2 is the ability to hide different items for each user role – administrator, editor, author and even contributor.

• You can control the display of the following post options for each role level:

   
   
  • Post Tags
   
  • Post Categories
   
  • Post Excerpt
   
  • Post Trackbacks
   
  • Post Custom Fields
   
  • Post Discussion
   
  • Post Comment & Ping Options
   
  • Post Author

• You can control the display of the following page options:

   
   
  • Page Custom Fields
   
  • Page Discussion
   
  • Page Comment & Ping Options
   
  • Page Attributes

2 more annotations...