Reply To: content migration from local dev to staging

Author Replies
traversal # Posted on February 13, 2014 at 12:31 pm

Hey there,

Yep, this is not unexpected, as the image field type needs to be able to reference a local file on the server but also stores the full URL to the image at the time it was created, which would likely be the URL of your local dev machine. If you’re able to do a MySQL replace of the local URL to the staging URL on the meta_value field in the postmeta table when you migrate the database, that would solve the problem. Let me know if you need more precise instructions on how to do that.

Without a fair amount of work, this is probably the only solution in the short term, but I would like to work out some way to make this process a little easier in the future, as it’s not an unusual scenario you’ve described.

Hope this helps

Travis

Latest From the Blog

MasterPress 1.1.4 now available

MasterPress 1.1.4 is now available. This release contains an important compatibility fix for WordPress 4.5 to allow correct detection of the taxonomy term editing screen. Without this fix, any custom fields you have attached to custom taxonomies will not be shown at all in the editing form. Note also that MasterPress will still detect the edit screen correctly in… 

Plugin Requirements

MasterPress requires a minimum of WordPress version 3.4, MySQL 5, and PHP version 5.2.4.

We also recommend that PHP is configured to use a memory limit of 64MB per request (128MB may be required for sites with higher complexity).

This plug-in is not compatible with the WordPress.com hosted service.

Traversal