After Cornerstone Update error - row: This element could not render because its definition is missing

I just updated Cornerstone from version 6.1.4 to 7.0.2 and am now getting an error for every element. Mostly I see the error for a row, because nothing within a row will render, but I also have a rev slider element with the same error. An example is:

row: This element could not render because its definition is missing. You may need to activate a plugin.

This error is seen in the Cornerstone editor. On the front-end, nothing displays at all where there should be content.

I have tested with a default theme and all other plugins disabled, and the problem is exactly the same. This is with the newest version of WordPress.

PHP is 7.4.

I downgraded to Cornerstone Plugin 6.1.4 and it started working again.

Is there something wrong with the new version?

Hey Brian,

Thanks for writing in!

We highly recommend that you clone your current site to a staging area. You can update Cornerstone plugin in the staging area. You may need to check out this article to know more about how you can create a staging site:

Meanwhile, the issue you may be experienced is that the Classic elements are turn OFF. You may need to go to Cornerstone > Settings > Permissions > Administrator > Elements.

Best Regards.

I went to where you said, and clicked on “Configure” next to elements, and checked “All Classic Elements” which was unchecked. It did not solve the issue or make any changes.

I don’t think “Row” is a classic element, nor is Revolution Slider. NO elements appear to work whatsoever.

But, for the record, “Row” IS checked.

I have once again reverted to the old version in the meantime. Since we use caching, I can mess with this without affecting logged-out users. I’m not too worried about a staging site.

Just to double check you clicked the “Update” button in the top right corner after checking that classic element button?

In a secure note giving us access to the site can help us diagnosis.
Turning on WP_DEBUG and checking the browser dev console under “Network” will give you the error I’m looking for where late-data is. That error you are experiencing usually happens when this request fails usually from a plugin conflict. Thanks let us know if you have any questions.

image

Hi Charlie,

Thank you for your continued help.

Yes, I clicked update after checking that button. And when I returned again, it was already checked.

I tried enabling wp_debug and then checking dev console and I couldn’t find anything like the error you’re showing there.

I’m confident it’s not a plugin conflict since, as mentioned, the problem is the same with all other plugins disabled and a default theme.

I will include credentials in a private note if you’d like to take a look.

1 Like

Hey @brianjohnsondesign,

I have logged in and checked your site. I have imported your homepage and load it up in my local testing server. I can replicate the issue seeing the "The definition for this element could not be located. You may need to activate a plugin. The type declared for this element is: " message.

So, I went back to your WP installation to figure what changed or difference with my install. I was guessing that maybe you have a custom PHP function. And then I noticed that you are actually using a 3rd party or custom made element named as “Classic: Image Hover Effects”

Regretfully this element is not in anyway associated with Themeco. I found out later that this element is part of the 3rd party Custom Cornerstone Elements plugin. It is best that you contact the creators of the plugin. They maybe have an update with a much newer version of the plugin that supports Cornerstone 7.0.

Best Regards.

Hi there,

Yes, the “Custom Cornerstone Elements” are a separate plugin, and I’m not worried about those. It is one we built.

Related to that: can you link me to the documentation for adding custom elements for cornerstone 7.0+? I can’t seem to find anything when searching.

What I’m not sure about is why the “row” element doesn’t appear to work. That’s my main problem. Even base elements are not working when I update.

To be abundantly clear, you said:

I can replicate the issue seeing the "The definition for this element could not be located.

The error you are referencing pertains to the classic:image-hover-effects element, and that is not my issue. The error message I get is:

“row: This element could not render because its definition is missing. You may need to activate a plugin.”

The rows themselves don’t even display. Row is not a custom element. I can’t get anything at all to display because all elements are contained within rows, and for some reason, Cornerstone thinks that the row element does not exist.

How can I solve this problem?

Once again, it happens even with all other plugins disabled and a default theme.

That’s the docs on the element API. This isn’t just for the “row” right it’s all of them? I’ll test your site as well this week in my local. If I can’t recreate I’ll probably ask you make a staging so we can tinker a little more safely. Apologies for the issues, we’ll get it handled though.

Okay great, thank you. That’s exactly the document I was hoping for.

And yes, it’s for all of the elements, in addition to row. However, since most elements are contained within a row, I don’t see errors for most of the rest since it fails before it gets to them.

One thing I have NOT yet tried is exporting the home page and simply re-importing that file. It’s possible that could work. Just thought of it now, since the last guy said he exported and imported locally and it worked.

1 Like

Hi @brianjohnsondesign,

Yes, you can export and import the Page you want, but you need to save it as Template and then you can download it as a .tco file. You can import in the same way wherever you want. I would suggest you follow the below steps.

  1. Save the Page as a Template.

image - 2023-01-10T160934.071

  1. Download the Saved Template

You can import the file, by clicking on the Import option in the above screen.

Hope it helps.
Thanks

I tried all of that and it also did not work. Exact problem as before.

I even tried importing the template into a brand new page, and the errors were identical.

Hi @brianjohnsondesign,

If I am not wrong here, the import was successful but the problem with the element definition still exists. If that is the case, it is due to the plugin used to create that specific element. I would suggest you install the same Custom Cornerstone Elements plugin where you are importing the template. If that is not the problem you trying to point out, please provide any screenshot marked with the issue or any video that helps us to recognize the problem.

Thanks

Hi,

No, that is not the problem. Please ignore the custom elements completely. Yes, that’s from a separate plugin, but that’s not my problem.

See screenshot.

NO elements are working when I update to the new version. This includes when I export the page content and import it in a new page. It also includes when I have all other plugins disabled and am using a default theme.

The main element that you can see isn’t working is a Row. Obviously “row” is not a custom element, and it should be working. This is not a case of custom elements or classic elements or anything like that.

You have access to the site if you want to test. See my note from earlier about it, and be prepared to upload the older version of Cornerstone when you’re done.

Hi @brianjohnsondesign,

I have investigated the issue further and I believe that this is a bug in the latest release of the theme. Most of the classic elements does not display when using standalone Cornerstone plugin. I have already reported this to our developers and they are made aware of the issue.

Please bear with us.

Okay, thank you for this response. I’m happy to hear you have identified this as an issue and are working to fix it.

I am curious though: “row” is not a classic element, correct? Because that’s the main element that seems to be broken in my case.

Hey @brianjohnsondesign,

The row is where to classic element is added. I’ve checked the issue report and our developer is now checking on it.

Please stay tuned and thank you for understanding.

Just a little more info. I am having this issue as well, on a brand new install of Pro 6.0.5 with no plugins except Under Construction and WP forms.

This is on a test install where I’m experimenting with the new version. The first thing I did was instal the “Starter Site” and everything works normally on that page. Then I tried installing one of the other demo sites and now any page I create has this issue. On a new blank page with no container, header or footer, when I create the first section. This happens.

It seems something about adding elements built on previous versions introduces this issue. This is something new because it never happened when I was testing during the beta.

Hello @Sheri17,

Can you please send us a video screencast so that we will have an idea of what is going on or at least a few steps on how we can replicate the issue on our end?

Thank you in advance.

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