Subject: Cornerstone homepage sections showing side by side instead of stacked

Subject: Cornerstone homepage sections rendering side by side instead of stacked

Hi,

My site (christianfamilylaw.com) uses the Pro/Cornerstone theme. My homepage is broken: two of my .x-section elements (the bio section and a call-to-action section) are no longer rendering inside my #x-site wrapper. Instead, they show up as direct siblings of #x-site under #x-root. Since #x-root uses display: flex with the default row direction, this makes all three top-level pieces display side by side instead of stacked, and the text overlaps.

I confirmed this by inspecting the live DOM directly: #x-root has 3 children (#x-site plus the two escaped .x-section elements), each taking about a third of the page width.

I also compared my page’s saved content (via the REST API) against what’s actually served to visitors. The saved content is properly nested. But the live HTML includes an extra, broken fragment (a stray

) right after my “Explore the path” tile links section, which isn’t present in the saved content. That fragment appears to be what breaks the nesting.

This looks like something is running WordPress’s automatic paragraph formatting (wpautop) or a similar content filter against my Cornerstone content, when Cornerstone content is normally supposed to be excluded from that. I’ve already ruled out WP Rocket and Jetpack Boost’s CSS/critical-CSS optimization features as the cause (tested with both turned off, cache cleared, no change).

Can you help me figure out why Cornerstone’s “don’t reformat this content” protection isn’t being applied on this page, and how to restore it? I don’t have a developer, so a step-by-step fix would help a lot. Thank you.

Hello @jmedajd,

Thanks for writing to us.

I checked your site on my end, and it is rendering fine. I tested it in Google Chrome browser version 150.0.7871.187. It might be a browser cache issue, so I would suggest clearing your browser cache and checking it again. If the issue still persists, please share a screenshot or screen recording so we can replicate the issue on our end.

Thanks