Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restoring a backup loses the stylesheet (all styling) #278

Closed
nicolepaschen opened this issue Aug 11, 2020 · 3 comments · Fixed by #274
Closed

Restoring a backup loses the stylesheet (all styling) #278

nicolepaschen opened this issue Aug 11, 2020 · 3 comments · Fixed by #274

Comments

@nicolepaschen
Copy link
Member

WP 5.4 + Backup 1.14.2 + Crio 2.3.1

Took a backup on my live site and transferred to CWP. All my CSS is gone.

image

@nicolepaschen
Copy link
Member Author

nicolepaschen commented Aug 11, 2020

The above issue was due to using minify with W3. Disabling minify fixed that issue.

@nicolepaschen
Copy link
Member Author

nicolepaschen commented Aug 11, 2020

I have an existing site using Crio + Backup + W3. Minify isn't enabled. I took a backup on the live site and transferred to CWP. I did the updates in CWP and my site looked fine.

I brought that backup to my live site and restored. The fonts on the front end are not the Customizer selections. When the Customizer is open I see my correct fonts but when I close the Customizer the fonts revert back to incorrect ones.

Something gets lost when it transfers. The live site had the last version of Crio, then I updated it in CWP so when it went back live it was the new version. I think it's related to that ?

@nicolepaschen
Copy link
Member Author

This time I had a completely up to date site and moved to a CWP. The fonts are broken. It happens only with Crio so not sure where the bug actually lives.

@jamesros161 jamesros161 transferred this issue from BoldGrid/boldgrid-backup Aug 18, 2020
@jamesros161 jamesros161 linked a pull request Aug 18, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants