Cornerstone is having trouble when adding any element

Support
#1

Hi,

I am having big trouble with Cornerstone for the last month. I thought the issue is with the translation plugin I am using (WPML), but it turns out it is somewhere else. I have been talking with the WPML guys for a while. They ran some tests and concluded that there is no problem from them, but there is an issue with some AJAX requests.

The guy from WPML actually created a video testing the issue:

https://www.loom.com/share/e8be80af8cd34e4ca1a06355a4640b77

Basically if we try to add any new section or element or whatever the page breaks and is not displayed properly on the live website. We can view it perfectly in the Cornerstone editor, but when we save and go to the live website, things are not working well.

Hope you guys can help!

Kind regards

#2

https://www.loom.com/share/e8be80af8cd34e4ca1a06355a4640b77

#3

This is the loom video from the WPML guy

https:// www. loom. com/ share/e8be80af8cd34e4ca1a06355a4640b77

#4

Hi Julian,

Thank you for the video. Is this happening on specific page only? We got the same issue before and the root cause is incorrect html. Can you please double check your content and see if there’s any mismatch html tags? If you can’t find one, please let’s also try basic troubleshooting. You could try testing for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.

In case the reason is not any of your plugins, please share credentials inside a secure note so we can double check your setup. Thank you.

#5

Hi Lely,

We do still have a problem. I disabled everything apart from Cornerstone and WPML. Once I enable WPML all the changes that I do on the page are either not visible or break parts of the page.

Also since the recent update of X-Theme there is no way to edit text in a text block on a word-by-word basis. I mean now we do need to use HTML for each little thing we want to do and before it was possible to actually use the navigation provided by the Theme and Cornerstone. Why was this removed? It makes working on the website quite inconvenient.
My partner is responsible for the content and he is not a programmer and the whole idea of a page builder is to take away the overhead of development. Removing these functions from the page builder achieved exactly the opposite result.

Is there an easy way for my partner to change stuff as he did up until now or working with HTML directly is the only remaining option?

Kind regards,
Julian

#6

Hello Julian,

Can you please confirm that you have installed the latest version of the theme? We have X theme 7.1.2 and Cornerstone 4.1.2. To better assist you with your issue, kindly provide us access to your site so that we can check your settings. Please create a secure note with the following info:
– Link to your site
– WordPress Admin username / password

To know how to create a secure note, please check this out:

Thank you in advance.

#7

Hi RueNel,

A guy from WPML is running some tests at the moment. He should be done around Wednesday/Thursday. Then I will give you access to the website so that you don’t interfere with each other.

What about this part of my question?

At the moment all 3 elements:

Text
Classic Text
Content Area

do pretty much the same thing. Before there was a way, similar to word, to easily change the single words to bold or larger size with simple controls similar to Word. Now this seems to be removed from the “Text” element for some reason and this makes things quite difficult for my partner who has no HTML skills. Am I missing something? Are these options just moved?

Kind regards,
Julian

#8

Hi Julian,

There must be a conflict somewhere with WYSIWYG. It should be available like this: https://screencast-o-matic.com/watch/cqlb6pviSP

You might need to do a basic troubleshooting first. You could try testing for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.

Let us know how it goes!

#9

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.