content migration from local dev to staging

This topic is: not resolved
Viewing 2 posts - 1 through 2 (of 2 total)
Author Posts
February 13, 2014 at 4:04 am #3418
webmaster@gravitant.com
Post count: 1

I am developing locally, then pushing changes to a staging server for client review. In the process I add content to custom post types locally, then make a copy of the database and import the database to the staging server. The one thing I am running into is that images uploaded through custom fields are not being recognized, even when the image files themselves are migrated to the staging server.

Any advice on how to do successful content migrations?

February 13, 2014 at 12:31 pm #3419
traversal
Post count: 207

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

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

Latest From the Blog

Ability to deactivate licence domains within MasterPress account management

25th October 2024

We have just rolled out an account management feature which allows licence holders to have better control over the domains that use their licence key. From the MasterPress Account Management page, the list of Active Sites that use your licence now includes a function that allows you to remove a domain from your licence. Simply… 

Plugin Requirements

MasterPress requires a minimum of WordPress version 4.9, MySQL 5.6, and PHP version 5.6.20.

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.

Three AM