[ZeshanMember]

Hi there,

Thanks for writing in!

Have you created that post in Cornerstone? Upon checking, I am not able to see any Cornerstone tab in the post edit page (see: http://prntscr.com/97hzn7). If you have created it directly from the WordPress standard editor, you can simply remove the headlines from the text.

Thank you!

[DesignbytrickParticipant]

This reply has been marked as private.

[DesignbytrickParticipant]

The post was made using only Cornerstone and the tab is there. Please see screenshot attached.

I am comfortable removing the headlines from the text in the WordPress standard editor, but I was under the impression that it is better to stick with Cornerstone once I have started building with it, and not to switch between the two? It gives me a warning when I try to switch…and I really don’t want to lose everything!

[ChristopherModerator]

Hi there,

Switching between editors breaks CS layout.
You can restore revisions to fix this issue.

Hope it helps.

[DesignbytrickParticipant]

Okay, just to clarify, here is what has happened so far:

1. I built a post in Cornerstone.

2. Then I contacted support asking for help removing headings from Cornerstone.

3. Now the post is suddenly in WordPress text editor and no longer in Cornerstone.

4. I have tried restoring several revisions in order to get the version back that was originally built in Cornertsone. Nothing has worked. The default remains text editor no matter how far back I restore the revision.

5. The original problem of the headings that can’t be deleted is still a problem.

6. I now appear to have no choice but to rebuild the entire post.

Is there any other way to fix this?

[Paul RModerator]

Hi,

Upon checking, I can’t see the cornerstone tab on the backend.

http://screencast.com/t/0HvcjnU34

It seems the user provided above don’t have admin access.

Posts and pages defaults to the editor it was last saved. If you have saved your posts or pages in cornerstone then open them again afterwards to edit, it should default to cornerstone.

I also can’t seem to find the post you are referring to. Can you provide us the url of the post where we could see the issue.

Thanks

[DesignbytrickParticipant]

This reply has been marked as private.

[ChristianModerator]

I see. What you placed in the Raw Content element are Cornerstone shortcodes that are available in the elements list therefore Cornerstone treats them as editable elements but the content is incorrect. That setup is not recommended since you can add the element directly from the elements list and you don’t need to use Raw Content. Raw Content is only for raw HTML and other third party scripts or shortcodes. The only solution for that currently is to use developer tools of a browser and remove the class of the element which you’ve added in Raw Content. Please see attachment.

Hope that helps.

[DesignbytrickParticipant]

Thanks for clarifying! I managed to delete the raw content elements.

I suppose there was some confusion because earlier on in this thread we experienced the same thing with shortcodes in text elements, and were then told to use raw elements instead.

So I have to wonder, if shortcodes can’t/shouldn’t be used in text elements, why is there that option?

[ChristianModerator]

The shortcode generator was supposed to be used in the Classic Editor. Since the Text element uses the classic editor though, the generator is there. I’ll take note of this and we’ll see if it can be removed in the future.

Thanks.

[ChristianModerator]

Sorry for the confusion. I just tested using the shortcode generator in Text element in my test setup and it works fine. I could select the text element without conflicts. This is brings me to conclude that this might be something unique to your setup. Can you duplicate your page and in your copy, remove elements one by one until you find the conflicting element. Let us know how it goes.

Thanks.

[Author]

Posts