Issues on http://staging4.storeitcold.com/wp-admin

[Web_Services]

Hi,

So we were able to create a staging 4 site for our website (storeitcold.com). On that domain’s wordpress, we were able to install X-theme and a child’s theme for it.

However, when we actually try editing any of the created pages in X, we get this message:

“The preview could not load due to misconfigured URLs. This could happen if you are using multiple environments and the site URL was not updated after migrating.
Origin URL: https://www.staging4.storeitcold.com
Preview URL: https://www.storeitcold.com”

Could you please fix this.

[jade]

Hi @Web_Services,

Is you site hosting in SiteGround? If so, please check this link for a workaround:

@ThemecoKB

Seeing the error in a SiteGround staging environment?

There’s a known issue with SiteGround staging environments where the builder tries to preview on the production URL. It happens because to make DB updates go smoother, SiteGround doesn’t update the site URL inside WordPress, instead they rewrite it as the site is rendered. This has a side effect of any plugin/theme that uses the site URL directly from the database could end up using the production version instead. SiteGround is aware of this, and they’ve informed us they’re working on improvements to their staging system to account for the additional cases.

To workaround the issue for now, they are recommending that you change the URLs before and after deploying. Here’s a guide for that process:

1. After creating your staging environment, go to Settings > General in your dashboard. Update the WordPress and site URLs to match the staging URL. For example staging-1-2-3.yourdomain.com
2. Work on your site as usual.
3. Before redeploying to production, go back and return the URLs to the production URL. If you fail to set the URL back before deploying, it will break the URLs on the production site.

If you are hosted elsewhere and the live and staging site do not share the same database, Please install the Better Search Replace plugin then do the following:

    search for http://www.storeitcold.com and replace it with https://www.staging4.storeitcold.com and
    search for http:\/\/www.storeitcold.com and replace it with https:\/\/www.staging4.storeitcold.com

Replace example.com with the domain name of your site.

Please make sure to keep a backup of your database before making any changes.

Hope this helps.

[Web_Services]

Hi,

So I made the changes you noted and that allowed me to initially edit the site on X. The issue I ran into after that was that I get this page when I try and open it on a browser:

I contacted siteground to get support on this and they told me that I would have to contact X to fix this. Can you please resolve this?

[lely]

Hi @Web_Services,

Please check this detailed guide. It is not a theme issue but rather incorrect configuration. The article will provide detailed information on how to fixed it. Hope this helps.

[Web_Services]

Hi Lely,

I tried everything that this guide discusses but was not able to fix this error. Can you please look into it and try to resolve it. I can give you any login credentials that you need.

[Web_Services]

I was able to get rid of the “too many redirects” issue by changing general settings under wp-admin. However, now we are back to the same issue where I get the image below for each page that I try to edit in Cornerstone.

How can we fix this issue without ending up with the “too many redirects” issue? Please get back to me at your earliest convenience. This is quite urgent.

P.S. Here is a transcript of my previous communication with siteground (our hosting provider) on the matter:

[ruenel]

Hello @Web_Services,

To resolve this issue, please login to your FTP of the staging site and then browse to the root folder. Find your wp-config.php file of the staging url and then add the following lines:

Please see the secure note

You will need this lines so that Cornerstone or Pro editor will be force to use the same staging url of the dashboard and not the define urls in Settings > General.

Kindly let us know how it goes.

[Web_Services]

So I asked siteground to make the changes and this is what they responded with. Should I still ask them to go ahead and make the changes?

[Prasant]

Hello @Web_Services,

Thanks for updating the thread.

@Web_Services

Should I still ask them to go ahead and make the changes?

Yes, you can let Siteground support know to proceed with the changes. As Siteground support team mentioned that Apache module replaces is on-fly in that regards It’s the only way to fix URLs.

Thanks.