Enables you to move your blog across locations, or even make it available through multiple urls at the same time.
|Author:||Onno Marsman (profile at wordpress.org)|
|WordPress version required:||2.9.0|
|WordPress version tested:||3.0.5|
|Added to WordPress repository:||14-02-2010|
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|Total downloads:||3 170|
Click to start download
Tutorial on how to use the ezMigrate plugin: Moving wordpress using the ezmigrate plugin
This plugin makes it easy to use and migrate your blog across different locations by detecting the current location and replacing all absolute paths on the fly. While there are ways to move your blog around by replacing the locations within the database manually or through scripts, they are very error prone and not very easy to do. Once enabled, this plugin doesn't require you to do anything other than move your code and database to a new location when you want to. You can even access your blog through multiple urls at the same time when you need to.
This plugin is useful when:
- You want to make your blog available through different urls
- You want to move your blog around
- You're staging the development of a blog with development, test and production environments which all have their own urls.
- You're using a Version Control System on a development server and developers have their own checkouts and urls to access a blog using a single database.
The ezMigrate plugin does the following things:
- It determines the root url of the blog.
- It replaces the options "siteurl", "home", "upload_path" and "fileupload_url" to the correct values, independent of their values stored inside the database.
- When not already set in wp-config.php it sets the constants WP_CONTENT_URL, COOKIEPATH and SITECOOKIEPATH to the correct values.
- When a post is saved into the database it replaces all root urls in href and src attributes with a placeholder. (This is also done for all posts when the plugin is activated).
- When a post is retrieved from the database it replaces all placeholders with the current calculated root url. (This is also done for all posts when the plugin is deactivated).
This way you don't need to do anything when you migrate your blog and you can even make your blog accessible through multiple urls. It made life for me and the other developers at triptic a lot easier when we need to develop blogs using wordpress.
What this plugin doesn't do (but might do in the future):
- Put a in the header of your template. You can easily do this yourself by placing <base href="<?php echo ezMigrate_getFullUrl();?>/" /> right after the <head> tag in the header.php file of your theme.
- Replace urls outside of the four mentioned options or outside of href and src attributes in posts.
- Make changes that might be necessary in the .htaccess file.
Known plugins that won't work on multiple locations without modification:
- cforms II, http://www.deliciousdays.com/cforms-plugin won't work because of absolute paths in abspath.php and js/cforms.js
- Prevented the ezmigrate tag from being prepended twice when the content_save_pre is called twice, which, apparently, can happen.
- Removed an incorrect reference which could cause problems in WordPress 3.1.3 and maybe other versions as well. (Fix provided by Patrick Fenner)
- fixed some errors when short_open_tag php.ini directive is set to off
- fixed a warning for php version 5.2.14
- fixed a bug where an extra character was stripped from the base url
- Fixed another bug where a symbolic link in the path to the wordpress installation wasn’t handled correctly
- Fixed a bug where a symbolic link in the path to the wordpress installation wasn’t handled correctly
- Fixed a bug where a symbolic link in the path to the wordpress installation gave an error (Thanks to input by Colin K. MacLeod)
- Fixed a bug where written html inside the text of a post was wrongfully converted upon plugin activation
- Fixed a bug where written html inside the text of a post was wrongfully converted upon post save
- Fixed a bug where plugin failed on the root of a webserver
- Removed duplicate code
- Initial version