WordPress MU Domain Mapping
Map any blog/site on a WordPressMU or WordPress 3.X network to an external domain.
- WordPress 3.1 compatibility.
- Localization fixes.
- IDN warnings about using punycode format.
- Fixed delete domain redirect.
- Better looking setup page.
- Better support for sites using SSL backends.
- Check input on admin page.
- Allow the primary domain to be ignored.
- Lots more bug fixes.
- Added www support
- Now supports WordPress 3.0
- Updated readme/instructions
- 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.
- Fixed bug in content filtering, VHOST check done in admin page, not sunrise.php now.
- 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.
- The admin pagesnon domain mapped blogs were redirected to an invalid url
- 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.
Requires: 3.1 or higher
Compatible up to: 3.9.1
Last Updated: 2014-4-17
4.5 out of 5 stars
17 of 71 support threads in the last two months have been resolved.
Got something to say? Need help?