Is the migration down to the fact you’re moving servers and/or domains? Or that your merging into another blog? If the former, you might be better off with a database dump (search and replace old domain with new one if that’s changing too), then import into the new database (along with copying over the filesystem). …
WPTeX allows you to convert your WordPress blog to a LaTeX document. If it does not already contain support for inline LaTeX, it should be really easy to add it.
Database synchronization between dev/staging and production How to: Easily Move a WordPress Install from Development to Production? Maintaining synced staging/production WP sites
WordPress is built to import and export content. As such, there is no built-in way to import or export settings. Some theme and plugin authors, however, have built tools into their systems that import/export XML files that their systems can use store options. A great example is WordPress SEO by Yoast. Not only can you …
The XML file you export will include references to the images, including a full URL. If the assets are actually available at that URL when you import the XML file, WordPress will automatically download them and add them to your new site’s media library. This gets tricky if the site you’re importing from isn’t publicly …
The only native import/export facility is the one under Tools in the admin. And even that needs an extension (plugin) for importing from different formats. It’s pretty straightforward to build one yourself. Something along the lines of: $options = get_my_options(); header( ‘Content-disposition: attachment; filename=my_export.txt’ ); header( ‘Content-Type: text/plain’ ); echo json_encode( $options ); exit; And …
Caveat This is extremely bad for SEO. Having duplicate content can ultimately cause your site(s) to be removed from search results. Solution This is actually pretty simple to have one database and disk content. Point both of the docroots to the same directory. Make sure each server name in your Apache config for each domain …
I normally use mysqldump and sed: on old server: mysqldump -u user -p OldWpdatabase > wpdb.sql sed -i ‘s/oldurl/newurl/g’ wpdb.sql on new server: mysql -u user -p NewWpdatabase < wpdb.sql sed is used to search and replace all the hard coded occurrences of the website if needed.
I’ve just had this or a very similar problem (I didn’t use the WP export tool, but instead did a manual migration from one environment to another). As far as I can tell, the problem occurs because of how WP stores the thumbnail data in the the wp_postmeta table (with the key ‘_wp_attachment_metadata’). This data …
After spending time debugging export.php, I found that we have to register post_format taxonomy for our custom post type. register_taxonomy( ‘post_format’, ‘portfolio’, array( ‘public’ => true, ‘hierarchical’ => false, ‘labels’ => array( ‘name’ => _x( ‘Format’, ‘post format’ ), ‘singular_name’ => _x( ‘Format’, ‘post format’ ), ), ‘query_var’ => true, ‘rewrite’ => $rewrite[‘post_format’], ‘show_ui’ => …
