X-theme version 6.4.6 - I am just editing a page however when the page loads, the content is not the same as that on the frontend. It is old content.
I am with SiteGround and have purged the cache - purged browser cache - used different browser, reset Permalinks several times. No error message - just loads old content.
Post I’m trying to edit: https://www.eatwelltas.org.au/whats-season-february/
Below are login details:
Hi Louise,
Thanks for reaching out.
It should be okay now, it’s due to transients (internal cache). I installed transient cleaner plugin and cleaned it. But Wordpress says
It could be true but SG Caching maybe isn’t fully syncing with the cleaning of transients, that’s why a plugin is still needed.
Please make sure to change the login credentials as well, you have provided it on public.
Thanks!
Well thank you but at first glance no deal - Still seeing old content. I removed all transients and cleaned SG Cache.
I had installed WP Optimizer to clean the transients as well - would that not be sufficient?
I provided the login details in a “secure note”? How come that is not secure??
So, what do I do now? Still can’t edit the page. All my Posts are doing it by the way. Somehow the February post saved itself (even when I opted to NOT save the page) and now the old content shows on the frontend again. This is getting a little very cumbersome. I’m afraid to edit ANY page now in case the new content is overwritten by the old content when I save a page or even exit without saving.
Hi Louise,
Please clear and deactivate the SG Cache for a while and provide us login credentials again so we can take another look, the credentials you provided above does not work anymore.
Thanks,
OK - I have disabled the Static, Dynamic Caches as well as Memcached on the SG server.
Would appreciate it if you could have another look.
I have given you another login:
Thank you.
Hello Louise,
I have logged in and checked the page.
This is what I am seeing.
Could you please clarify or send us a screenshot of the old version of the page that you are seeing?
You may also need to clear your browser cache or use a private browsing mode and test the page again.
Please let us know how it goes.
What you were seeing is the old version. I’ve emptied browser cache and tried Incognito mode - no success there either.
Every single post entitled “What’s in Season in [month]” displays the incorrect info when opened in Cornerstone. You can test this yourself by selecting “View” before you edit the page. View displays the CORRECT page. When then hitting Edit With Cornerstone, and you get the WRONG/OLD page content.
Please try that and you’ll see. Thank you.
Hey Louise,
By old content do you mean blank page in Cornerstone?
It is because your posts has been edited outside of Cornerstone so the builder’s data has been erased. If you have not edited your posts outside of Cornerstone, it is possible that a third party plugin did it.
If you can remember your website activity before this issue happened, that might lead us to the exact cause.
Right now, if you have a working backup of your site, you can revert to it. If not, regretfully, you will need to rebuild your posts.
Thanks.
No - I do not see a blank page. I see the OLD content - see screenshot. Just do a View like I said and you will see that the frontend is totally different from the backend.
1st screenshot is from What’s in Season in February backend.
2nd screenshot is from What’s in Season in February frontend.
The second one is correct - you can replicate this by going to VIEW. Then go back and EDIT WITH CORNERSTONE.
But OK - I can see that January and February are now saying they have been edited OUTSIDE of Cornerstone but March has NOT. Please check out the one for March - it shows the incorrect content too.
I see that the March post is old in Cornerstone but in the live page. However, my advice would still be the same.
Cornerstone could not revert to old data on its own. There must have been a database activity by a server process, website user or a third party plugin.
Regretfully, there is no mechanism for Cornerstone to get the generated content. If the builder’s data has been reverted to a previous version, the solution would be to restore a database backup where everything is correct. Otherwise, rebuilding the page would be necessary.
Thanks.
Thank you Christian - I appreciate your response. I’m not sure if the development team are planning on changing this vulnerability of Cornerstone. Once edited outside of it, your page is basically stuffed. Editors like Visual Composer and Avada’s editor are interselectable. Also the fact that page/post revisions are not available is - in this case - a severe drawback. Even though I have told my clients they always need to Edit With Cornerstone, the reality is that down the pike within their companies, this info sometimes gets lost. It is a vulnerability that makes me pick Avada over X/Pro for my next project. 
I’m sorry to hear that. I have posted this in our issue tracker so our development team would be made aware of this case and they might take this into consideration when building new features.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.