[xorredParticipant]

I do not know how that happened, but my homepage is now not editable in cornerstone as it said I edited it outside of it. But even if I edited it in text mode or visual, which I did not – but even if I did, or a plugin did or whatever – why do we have to completely rebuild our pages in cornerstone if any change happens to the page?

Can you offer some backup solution? Or a solution in geneeral?

[JackKeymaster]

Hi there @xorred,

Hope you’re well today! 🙂

We currently have a active feature requests for implementing a restore/undo/redo functionality into Cornerstone, which hopefully something similar will come to Cornerstone in the near future.

At the moment, the closest would be the templates option of Cornerstone, so you could create a template from a Cornerstone page and then if the above happens, you can enter that page again in Cornerstone and upload your template so it can then once again be edited in Cornerstone.

You can read more about page templates here https://community.theme.co/kb/cornerstone-interface-layout/ 🙂

Thank you!

[xorredParticipant]

At this point I am more worried about having to rebuild the whole homepage from scratch. Where is the field that triggers 0 or 1 on modified or not, in the db?

[JackKeymaster]

Hi there @xorred,

I’ve been speaking with the developer of Cornerstone and technically if you switch back to the cornerstone editor after saving a page outside of Cornerstone, it should still remember the last point and use that data.

There have been known instances of ACF (Advance Custom Fields), conflciting and deleting Cornerstone data, you’ll find the Cornerstone data in your database with the meta key _cornerstone_data

Hope this helps.

Thanks!

[xorredParticipant]

I was asking which field in the db for that page to change from “edited outside of cornerstone” to “not edited outside of cornerstone”

[xorredParticipant]

maybe it’s a good idea to add a checkbox to a page ‘set as not edited outside of cornerstone’? To me it seems pretty basic to preserve the shortcodes and keep cornerstone working – for advanced users…

[Nabeel AModerator]

Hi again,

Best way to remedy this is to go back on the previous revision or 2,3 revisions back where everything was working fine with CS. That should get things right and then you can start editing your content again without rebuilding it.

Let us know how this goes!

[xorredParticipant]

Revisions is not the best way in my case…. I am asking where and what can I change in the DB in order to mark this page as not edited outside of cornerstone….

[xorredParticipant]

no matter what revision I choose it says modified outside cornerstone. It’s a fault of a system, not my fault. I am asking how to fix it.

[xorredParticipant]

switching to cornerstone starts from scratch…. this is really weird. And I don’t want to start from scratch…

[AlexanderKeymaster]

Hey there,

This is Alex, lead developer on Cornerstone. I wanted to chime in here with some more technical info. When you hit “save” in Cornerstone it does a few things:

1. Updates post meta _cornerstone_data with all the page data and _cornerstone_settings with things like Custom CSS and responsive text.
2. Updates any modified WordPress fields like the title or page template.
3. Uses the page data in _cornerstone_data to render an arrangement of shortcodes.
4. Removes the _cornerstone_override post meta should it exist.

The _cornerstone_override is the flag you’re looking for above. When it’s present, we’re indicating that you’ve made modifications to the_content via means outside of Cornerstone itself. It’s what helps us manage the state of things when you edit a post in the dashboard

The shortcode generated for the_content are as simple as possible, and do not represent the full amount of data stored for each page. This helps with performance, but is part of why you can’t go backwards. The shortcodes themselves don’t carry enough information to reconstruct the Cornerstone page builder data, and control values. For example, some controls end up simply appending CSS classes to elements. This layer allows us to streamline the shortcode markup while providing more options in Cornerstone, instead of bloating out shortcodes. It also helps speed up how Cornerstone loads and processes information.

---

Now… getting to the problem at hand. I’m not sure what exactly is causing the problem, but I’ve seen a case like this recently.

Have you done any of the following on this site shortly before this started happening?

– Moved to a new URL
– Used the ACF plugin
– Run any kind of manual database operation

In a recent case, there was a problem were a migration script swapped out the URLs from one domain to the next, but miscounted the number of characters somehow, which corrupted the Cornerstone data. This made it impossible to import any of the revisions which were previously working fine.

[xorredParticipant]

Hi Alex, thanks for jumping in!
I installed a db plugin which searches and replaces all strings in the db with anew one. I replaced http to https… then the page said ‘modified outside of cornerstone’ and since then I can’t go back. Thinking more about it I decided it would be viable to just rebuild, instead of going to the db and running a risk of breaking something bigger.

[Nabeel AModerator]

Sounds good.

Do let us know if need any assistance in this regard.

Cheers!

[Author]

Posts