This Element Could Not Render Due to Invalid Markup Error

@USAT009 - Is your site hosted by WPEngine? If so, let’s both contact them to see if they know what is going on. Please update me here. I will also update if I get anywhere with them.

Speaking with WPENGINE… We downgraded to an older version of Wordpress and Woocommerce. Same issues. They’ve checked all error logs, and are sure that it is a Themeco issue with something about how it handles woocommerce or something… Too technical for me to understand.

We do know it INVOLVES woocommerce, because we can simply deactivate woocommerce, and everything works fine. But WPEngine believes it is actually Themeco’s issue with a change you’ve made, not Woocommerce.

They have confirmed that they have not made any back-end changes to their servers in the last 2 weeks.

Came here to say I’m having the same issue too. I’ve checked all plugins, and it’s a Woocommerce conflict - as others have also found out. It’s only when I go to make a change in Cornerstone, that markup issue shows up in the editor window.

Thanks :slight_smile:

1 Like

@pdxcomps Can you send FTP credentials to this site? I’m going to put a dev build there and see if that gets us further.

I added a secure note with the dev site info. It’s ready for you to do whatever you want.

@TIrvine Are you with WPEngine for your hosting?

Sorry I need FTP access since I need to upload Cornerstone files. See secure note as well.

Charlie - Please see this secure note here.

Well I’ve narrowed it down to Jetpack. disabling the plugin fixed the issue. Then on your dev site reactivating Jetpack again seemed to fix the issue. Which might work on other sites as well. Although I took this site into Jetpack Safe Mode which might have also fixed it. Something with Woo + Jetpack changing React to use a CDN causes the issue.

We’ll try to have a fix written this week. At worst you might need to deactive Jetpack for the time being or find a setting to turn off the CDN for Jetpack.

The problem being that their CDN overwrites the default React url during the initial load, but not during REST requests like changing content in Cornerstone. Thus causing react to load in twice and then crashing Cornerstone. I think we can write a workaround for this, or just disable the Jetpack CDN when the app is running.

Thanks for your patience

Well well! How cool is this! I will try to find a way to disable the CDN for jetpack - If I am succesful, then I will update with a “how to” for others to find here.

Would you like me to keep my DEV site up for you to test on? I am not doing anything with it, and have no problems helping out with that.

Thanks!

UPDATE!

As promised, I would update this to relay the info. You CAN disable Jetpack’s CDN. In your Wordpress back-end dashboard, look for “Jetpack” in the menu on the right. Then click on the “settings” option. On the page that loads, you will see some options at the top of the page. One of them is “Performance” - click that. The 2nd option down, you will see “Performance & Speed”, disable the “Enable Site Accelerator” - Which should also disable the 2 settings right below it “Speed up image load times” and “Speed up static file load times”.

You will get a quick message that says it has been disabled. After doing this, I enabled Woocommerce again, and it works perfectly. I do not see any performance degrade, and everything seems to be working perfect again. I hope Themeco will update this thread once the fix is released, so I can re-enable the option.

Thanks again for the great customer service!

2 Likes

Hi Ryan,

Thanks for confirming it. As my colleague says we are working on it, and the fix will be released soon.

1 Like

@pdxcomps
I’m not, sorry. I host my own sites.

Thank you @pdxcomps and Themeco staff for working on this. So much appreciated :pray:t3:

1 Like

Happy to help! That is what these forums are for. I hate it when someone finds a solution to a problem, but never takes the time to help others. Best of luck!

1 Like

Hi @pdxcomps,

Your help is always appreciated.

Fix is out now in the update today. Let us know if you still encounter issues. Have a great day.

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