Thank you for waiting. With @charlie’s help, we were able to manually removed the elements without the _type parameter in the Dev Toolkit > Tools > Documents Elements State field, allowing the page to save or update. This is a very intensive process, especially for large pages. Shown in the screenshot below is an example of an entry without the _type parameter that needs to be removed.
Please check the copy of the home page in the secure note.
The reference or ID of the entries without the _type parameter should also be removed from elements that contain them. In the example above, cs390 is used in the element cs387, so the reference to cs390 has to be removed there. Please check the screenshot below:
And one more thing, to make it easier to search for entries without the _type parameter, try using this tool: https://regex101.com/. In the regular expression field, add this "(?!(?:_m|_bp_data3_4))(\w+)": \{(?![^{}]*"_type")[^}]*\} then paste the element state in the test string field. You should see the entries highlighted like this:
Let us know if you need more info.
Hi @Ismael, thank you for diving into this and finding a solution. Just a few questions:
Is there a reason these sections/elements broke in the first place? If we are using elements from the Cornerstone builder, why would some of them be missing the _type parameter?
Also, if we continue building new pages within Cornerstone, how do we know this won’t just happen again with some of the same elements it is happening with now?
I looked at the copy of the homepage you sent in the secure not and I do not see the icon with the drill to open up the Dev Toolkit window, how can I access this?
Thank you.
Thank you for the update.
1-2.) According to @charlie, these elements were likely added from a very old version of the builder, possibly classic elements that are no longer supported or have been deprecated. They use the old builder interface, which, for some reason, didn’t get ported to the new version. Rest assured that from the current version onward, all elements will be readable and complete after every update.
3.) Please open the Preferences dialog, then enable the Dev Toolkit option as shown in the screenshot below. This has been enabled in the staging site. You should be able to access the Dev Toolkit > Tools > Documents Elements State afterward.
Let us know if you need more info.
In 6.6.3 we made an update so that you can still save and edit your page when it’s in this state. Let us know if that helps.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
