![]() If there are no thumbnails then use the plug-in Tools -> “Force Regenerate Have a license key, and/or where the license key is difference on development than on production.Ĩb. Look at the list of plug-ins and re-activate plug-ins that need activation. Apply the uploaded export file to the production site when prompted to do so.Ĩa. Wait patiently while the file uploads.ħb. In the dialog box that opens just drag and drop your exported file from step 3d or navigate to the exported file location.ħa. On your production site perform an import using the "All-in-One Migration’ plug-in. Download the file that is created to your Desktop or Downloads folder. Export to “File”, which is free with the plug-in.Ħd. This is only needed if the two are different.Ħc. Add a rule to ‘Find’ your development site database prefix and ‘Replace’ with your production Add a rule to ‘Find’ your development site name (e.g. Install the plug-in “Force Generate Thumbnails” to your Local site.Ĭreate an export file using the “All-in-One Migration” plug-in.Ħa. Install the plug-in “All-in-One WP Migration” to your Local site and your production site. Take production site out of maintenance mode. Then add the following to the end of list ![]() Put production site into maintenance mode So I would add the following to the beginning of your list. Hopefully this is helpful to you and to any others using the excellent Local by Flywheel too. My site,, is a multilingual web site and only “All-in-One Migration” kept the translated pages intact and associated with the parent page. I experimented with other plug-ins and only had good results using the “All-in-One Migration” tool. I’ve performed this process up and down now several times to perfect it. It should all match up with development now. Check out your pages and/or posts and/or comments.If there are no thumbnails then use the plug-in Tools -> “Force Regenerate Thumbnails” to (duh) force the regeneration of thumbnails in the media library. Typically these are ones that have a license key, and/or where the license key is difference on development than on production.ĥb. Apply the uploaded export file to the production site when prompted to do so.ĥa. Wait patiently while the file uploads.Ĥb. In the dialog box that opens just drag and drop your exported file from step 3d or navigate to the exported file location.Ĥa. On your production site perform an import using the "All-in-One Migration’ plug-in. ![]() Export to “File”, which is free with the plug-in.ģd. This is only needed if the two are different.ģc. Add a rule to ‘Find’ your development site database prefix and ‘Replace’ with your production site database prefix. dev) and ‘Replace’ with your production site name (e.g.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |