ok, I’m about to add details to secure note
Hello @dcheese,
I have investigated the issue and I found out that there is an error 500 going on in your website’s server. Please check out thos article for the troubleshooting instead:
You may also contact your hosting provider for further assistance.
Thank you.
I did all of the things mentioned in that page, without success.
I’m trying to know if my hosting provider can help me.
Hi @dcheese,
Whenever trying to access the staging admin URL through the previous URL it shows the following error. Please check once and let us know once it is accessible.
Thanks
Hello @tristup, staging is not active anymore, so you can use the first link I gave you in the secure note to enter the backend of the website. Thank you
Hello @dcheese,
I have investigated the issue further and I can replicate the issue. I cannot select any of the elements on the builder.
- Please see my video screencast in the secure note below.
I would recommend that you reactivate your staging site and we will continue troubleshooting in your staging site since your site is live. The issue could be one of your plugins or that one of the theme files were corrupted. We highly recommend that we continue the troubleshooting in staging so that we can deactivate most of the plugins and switch to the parent theme as well.
Best Regards.
Hi @dcheese,
Unfortunately, the staging URL is still not accessible. I have tried logging into your live server, but it still shows the 404.
Thanks
Hey @dcheese,
Your staging setup won’t work for Cornerstone as Cornerstone loads the preview is URL based. Your staging site should not be showing the live domain like https://example.com. It should be https://staging.example.com or https://example.com/staging
The builder is behaving like when you’re in Theme Options. That means the builder is previewing a mirror of your site that’s why you see that “Edit Page” when you hover over the content.
Would you mind providing details when this issue happened? What did you do to your site before this happened?
Also, please don’t use the staging method that you’re currently using as it still uses or displays the live domain. Disable it on your site. Again, your staging should either be a subdomain like https://staging.example.com or a subfolder like https://example.com/staging.
Thanks.
Hello @christian, the error for why I ask your help is not related to the live staging. It is the same on production website.
I’m going to deactivate the live staging right now. I want to try to update to PRO to see if the issue is still there.
Hey @dcheese,
Thanks for confirming that the issue happens on the live site without the staging setup as well.
My comments remain the same, whether in production or staging. I just made sure that your staging setup is not in the way.
The cause right now is a mystery to us that is why I asked the following questions.
Upgrading to Pro might not be the solution. Reinstalling WordPress and/or changing your web host might help.
In a Secure Note, also post your wp-config.php setup. Or, give us FTP access (you can get this info from your web host).
Thanks.
Hi Christian, sorry for the total confusion. Unfortunately the “live staging” offered by my provider creates a problem at the production site, where the images are missing. They haven’t found a solution to this problem yet, so the only way to work in “live staging” without the production site goes affected is to put it under maintenance.
Anyway… to try to fix it in another way, I created a copy of the website on another domain, by using an old backup. Everything works (seems) perfectly. Currently this new staging uses WordPress 5.2.4 with X 7.0.4. Meanwhile, I’d like to be able to update X, so I’m asking if the latest version is compatible with Wordpress 5.2.4.
SOLVED guys! I was able to update wordpress, X and all the plugins without having any problems. Seems that the problem occurred due to WPML. Thanks so much for your time! You are precious 
When I wrote my last post I was referring to the staging website, which works as it should. But when I moved it to the production website, the problem is still the same: the pages are not correctly editable. In the error log, when I open a page in cornerstone and try to edit it, appears the message in secure note. Any advice?
Hey @dcheese,
Please contact your web host or server administrator to enable gzdecode support. If your web host cannot support gzdecode, regretfully, you need to move to a different host. Our products work well on popular web hosts.
By the way, I previously asked about some history of your site to give us more context on the issue. Also, I asked for FTP credentials. It looks like that can’t be provided so the only option now is to move to a different host.
If you do decide to migrate or move, you can follow the instruction here: https://theme.co/docs/how-to-migrate-your-site
Thanks.
Hello @christian. All my webstites are on that hosting provider, and all of them use X or PRO.
The unique difference from other websites on the same hosting is the choosed plan: it has only 256MB of memory limit allowed. Hcrosal is an old website, made with X, and it’s migrated from another hosting to the actual this year. It never had any problems.
Tomorrow I’ll speak again with my hosting provider to better understand if gzdecode is disabled only on the basic plan. If yes, this could be the problem.
I’ll let you know. Thank you: pray:
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.