Loss of styles in a migrated site
I built a WP site on my hosting account. I used the Global Style Ashen. I modified its colors, font selection, paragraph text size, and added a style for URLs.
I migrated the site to a localhost account, essentially for backup. The site looked fine. However, when I opened a page to make a correction in Brizy, the colors and appearance changed in Brizy. I found I was now in the Overpass Global Style. I went back to the Ashen Global Style. The Global Colors and fonts reverted to the usual Ashen values and the individual styles were the standard Ashen settings. The URL style was missing.
I used WPVivid plugin to clone and migrate the site. I am using Laragon on a Win 10 Pro PC.
What other gotchas are hiding in there?
I exited to Dashboard - and did NOT get a warning about losing changes, despite having changed the Global Style. When I reloaded, in a separate tab, the page I had planned to edit, it now showed the standard Ashen fonts and colors.
This is not good!
-
Hi Jack,
Usually, for site migration, we recommend using the All in One Migration plugin. It copies all the files and users don't find some problems or inconveniences. Could you try using this plugin and let us know if all is working correctly?
Thanks!
Best regards,
Sandra0 -
Hi Sandra,
I used All-in-One WP Migration, as requested. Had the usual issues of the file size being too big (835MB vs an initial allowance of 8MB). Edited the .htaccess file on localhost.
The site came in as it should. Global Styles were as configured in the live (source) site, including colors, fonts, and an extra style for URLs.
I will contact the WPVivid team, since it seems to be their issue.
Thanks!
Jack
0 -
Hi Jack,
Thank you for informing us! If we could help you with something else, please feel free to ask us and we will be happy to help you!
Best regards,
Sandra
0 -
Hi Sandra,
FYI
I contacted the WPVivid team. Per discussion with them, I created an online test site. Cloned the source site with their plugin. It came in correctly with all my changes to the Global Style and the additional style I created intact. The correct Global Style was selected.
I think this is a good thing, although non-reproducible errors are always a concern.
Best,
Jack
0 -
Thank you, Jack, for the update. It is important news. Each migration tool has its own structure and behaviour and sometimes it can not copy some folder and files and for this reason, happens such types of inconveniences! I'm happy to hear that now all is fine!
Have a great day, Jack!
Best regards,
Sandra
0 -
Sandra,
I went back to the localhost site that had the original problem with changes to Brizy. I deleted the uploaded backup.
I uploaded the backup again and did a restore, all with WPVivid. The site came in properly.
Must have had a few drunken electrons the first time.
Thanks for your help.
Jack0 -
Hi Jack,
Was very funny to read "few drunken electrons" :)! You are amusing!
Yeah, maybe something goes wrong at the first time! If you will encounter some other inconveniences with Brizy, please let us know and we will be happy to help you!
Best regards,
Sandra
0 -
Bringing this thread back to life from the dead as I just had this same issue come up. I used Jetbackup for the migration.
I don't have access to WPVivid, and All-in-One exceeds my hosting storage space.
The issue with the migration is huge. I'm now having to go back into the live site and manually update all the styles, PLUS, go into each and every page to reassign the styles to every body of text, as they've now been labeled as "Custom."
@Brizy: Limiting the migration to one specific tool does not seem to be good support advice. There should be an option in the Style builder to save a style file (such as in the drop down, adding an option: "Save as a custom style" which can then be uploaded to a migrated site.
0 -
Hi Kris,
Have you tried using the free version of WP Vivid? If not, kindly remigrate your website using WPVivid free and check if styles migrate well. Kindly try the process outlined at How To Migrate Your Site To A New Host | wpvivid demo You could also attempt the following 2 steps process
- Take a backup of the source site using WPVivid and download the backup file to your computer
- Upload the backup to WPVivid in the destination site and restore the website from the uploaded backup
You could temporarily deactivate and delete the JetBackup plugin to free up hosting space if storage space is a constraint. Please also consider removing any unused themes from your WordPress Dashboard to create additional space.
0
Please sign in to leave a comment.
Comments
9 comments