WordPress MU Domain Mapping CN

WordPress MU Domain Mapping Simplified Chinese Language. Translate from Plugin WordPress MU Domain Mapping. URL:http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/ This plugin allows users of a WordPress MU site to map their blog to another domain. Site administrators must configure the plugin in Site 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. 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 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 original blog's domain for login to ensure the user is logged in on the original site as well as the domain mapped one. Site 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) There is a lot of debate on the handling of DNS using CNAME and ANAME so both methods are available depending on your preference and setup. Things to remember:

• CNAME records that point to other CNAME records should be avoided (RFC 1034 section 5.2.2) so only tell your end users to use your chosen domain name as their CNAME DNS entry if your domain name is an ANAME to an IP address (or addresses)
• Only use the CNAME method if your main domain is an ANAME of an IP address. This is very important. How do you know? Check your dns or ask your hosting company.
• Giving your user the option to just use your chosen domain name and not an IP (or list of IP's) to set as their CNAME will make administration of your WordPressMU blog platform easier, an example of this would be purchacing/deploying a new server or indeed adding more servers to use in a round robin scenario. Your end users have no need to worry about IP address changes.
• Finally, telling your end users to use an ANAME IP or CNAME domain name is up to you and how your systems are deployed.
• Further Reading: http://www.faqs.org/rfcs/rfc2219.html

1. Copy sunrise.php into wp-content/. If there is a sunrise.php there already, you'll just have to merge them as best you can.
2. Copy domain_mapping.php into wp-content/mu-plugins/.
3. Edit wp-config.php and uncomment the SUNRISE definition line: define( 'SUNRISE', 'on' );
4. As a "site admin", visit Site Admin->Domain Mapping to create the domain mapping database table and set the server IP address or a domain to point CNAME records at.
5. Make sure the default Apache virtual host points at your WordPress MU site so it will handle unknown domains correctly. (Need info on cpanel, etc. How do you get them to respond to any domain?)
6. Do not define COOKIE_DOMAIN in your wp-config.php as it conflicts with logins on your mapped domains.

For Cpanel users If your domain uses the nameservers on your hosting account you should follow these instructions. If the nameservers are elsewhere change the A record or CNAME as documented above. Add a wildcard subdomain/virtual host record to your site's DNS record in Web Host Manager (WHM). If you do not have access to WHM, you must email your web host and ask them to make this one change for you. Should be no problem:

• Go to "Edit DNS Zone" and select the domain of your WPMU installation and click "Edit".
• Below "Add New Entries Below This Line", enter in the first box (Domain) an asterisk: "*".
• The second box, TTL, should be "14400".
• The third box should be "IN".
• Select A Record Type from the drop down "A".
• And in the last box, paste in the IP address of your website.

From Cpanel, click on the "Parked Domains" under the "Domains" section:

• Under "Create a New Parked Domain" enter the domain name you want to add to your site.
• Click the "Add Domain" button.
• It should add the domain to the list of parked domains and under "Redirect to" it will say "not redirected". That is OKAY.

Now you're ready to do your domain mapping.

0.5.1

• Added Cpanel instructions, props Marty Martin (http://mearis.com)
• Filter more urls, props Ryan Waggoner (http://ryanwaggoner.com)
• Added CNAME support, props Martin Guppy
• Added check for COOKIE_DOMAIN, props Scott, http://ocaoimh.ie/wordpress-mu-domain-mapping-05/comment-page-1/#comment-671821

0.5

• Works in VHOST or folder based installs now.
• Remote login added.
• Admin backend redirects to mapped domain by default but can redirect to original blog url.
• Domain redirect can be 301 or 302.
• List multiple mapped domains on site admin blogs page if mapped
• Bug fixes: set blog_id of the current site's main blog in $current_site
• Bug fixes: cache domain maps correctly, blogid, not blog_id in $wpdb.

0.4.3

• Fixed bug in content filtering, VHOST check done in admin page, not sunrise.php now.

0.4.2

• Some actions are actually filters
• Change blog url in posts to mapped domain
• Don't redirect the dashboard to the domain mapped url
• Handle multiple domain mappings correctly.
• Don't let someone map an existing blog
• Only redirect the siteurl and home options if DOMAIN MAPPING set
• Delete domain mapping record if blog deleted
• Show mapping on blog's admin page.

0.4.1

• The admin pagesnon domain mapped blogs were redirected to an invalid url

0.4

• Redirect admin pages to the domain mapped url. Avoids problems with writing posts and image urls showing at the wrong url. Updated documentation on IP addresses for site admins.