Scripts/styles not loading on cloned WP Site when logged in
Scripts/styles not loading on cloned WP Site when logged in
Scripts/styles not loading on cloned WP Site when logged in
This is a common issue. Unfortunately, it is just one of many possible symptoms of incorrectly moving a WordPress site to a new url. The solution is to ensure that WordPress (core, plugins and theme) and your web server are all using the same URL. If you have an SSL cert for the staging site … Read more
WordPress Staging site is redirecting to live and lost the child theme
It can absolutely be done using WP-Cli. Do you have SSH access to the remote server/site? If so, I am happy to show you a process I’ve cooked up using rsync as well as just some standard SQL for the database. That’s my preferred way to do it at the moment.
I found there were two problems causing this: There is some kind of server caching I apparently don’t manage. I cleared that by adding a query to the URL (like staging.site.org/?a=b) and some things started being served, but many were still giving 404s. There was a rewrite rule in .htaccess designed to prevent hotlinking things … Read more
On the Live website, Go to WordPress Dashboard and select Tools / Export Check Posts, Pages and Media. WordPress will export an XML with the data. On the Production website, Go to WordPress Dashboard and select Tools / Import / WordPress. Run the installer and import XML data form Live website.
Update Pages ONLY from Stage to Live (not products)
Usually people don’t create a repo for their entire site. Instead, they typically will create a repo for each theme and plugin. So, you’ll have a staging site where you can edit your theme (or child theme) files and keep those all in a repo. Once everything looks good on staging, you can then push … Read more
SO FINALLY to my question: Is this indeed a brilliant solution, or is there a real possibility it will it cause me major problems like broken links and database corruption in the future? You will find that new content created refers to the new URL, even after you remove the config statements, and old content … Read more
It sounds like a caching issue as mobile is the same domain. Try a different browser or if you use Chrome. Open Inspection Tool > Network Tab > then check Disable Cache Then do a hard refresh. If you aren’t sure how. Click and hold on the refresh icon with the inspection tool open.