Cornerstone Styling Correct in Editor but Missing/Broken on Live Frontend

Support
#1

Hi,

I’m experiencing an issue where my website looks completely correct inside the Cornerstone editor, but the styling/layout is not displaying correctly on the live frontend.

Website: talloaksconstruction.ca

The site was built entirely using Pro/Cornerstone. The pages and design still appear correctly inside the Cornerstone editor, so the content itself does not appear to be lost or corrupted. However, when viewing the live website, much of the Cornerstone-generated styling/layout is missing or displaying incorrectly.

This issue appeared suddenly. The website had previously been displaying correctly on the frontend.

I contacted my hosting provider, HostPapa, and they investigated the server. They initially found mixed-content warnings and forced HTTP requests to HTTPS through .htaccess , but this did not resolve the frontend styling problem.

HostPapa then escalated the issue and checked the website/server more thoroughly. They reported that:

  • they could not find anything blocking the website’s CSS files;
  • they did not find server or WordPress error-log errors;
  • they cleared the Cornerstone plugin cache;
  • the problem still persisted;
  • they recommended contacting Themeco because they believe the issue is related to how Cornerstone is displaying/delivering the frontend layout.

One thing I noticed in Chrome DevTools that may be relevant: the live site was requesting some assets from a third-party domain/location rather than talloaksconstruction.ca. The console also showed mixed-content warnings for those assets.

This is particularly strange because this was a brand-new WordPress installation for talloaksconstruction.ca , originally installed by HostPapa on July 7. It was not migrated from another website. Since installation, I have built the website through the Pro/Cornerstone visual builder and have not manually edited the site code or migrated the WordPress installation from another domain.

The images currently uploaded to the WordPress Media Library also appear to have the correct talloaksconstruction.ca/wp-content/uploads/... URLs.

So currently:

Cornerstone editor: styling/layout displays correctly
Live frontend: styling/layout is broken or missing
WordPress Media Library: current images point to the correct domain
Hosting/server: HostPapa reports no CSS blocking or server errors

Could you please help me determine why the Cornerstone styling is rendering correctly in the editor but not being delivered correctly on the frontend, and whether the third-party asset references could be related?

I can provide screenshots of the Cornerstone editor, live frontend, Chrome console errors, and any additional diagnostic information you need.

Thank you!

#2

UPDATE / Possible clue: I believe I may have identified where at least some of the third-party asset references are coming from. One of the URLs shown in the Chrome console contains /interior-delight... . I used the Gridorama: Interior Delight pre-made template from Cornerstone on this website, and Cornerstone still shows that template in my Elements/Templates panel.

This makes me wonder whether the imported Gridorama template retained references to externally hosted demo assets on team.secdns.co instead of converting/copying all of those assets to the local WordPress Media Library.

Could those external Gridorama asset references — particularly if they are being requested over HTTP on an HTTPS site — be interfering with frontend rendering or Cornerstone’s generated assets? And if so, is there a recommended way to replace/purge those original template asset references without rebuilding the pages?

2026-08-13_09-35
2026-08-13_09-352000×1041 547 KB

#3

Hello Casandra,

Thank you for the additional detail and for narrowing this down yourself. I have reviewed your page source and can confirm the cause. This is not a caching, migration, or hosting fault — there is a syntax error in custom CSS applied to a footer element, and it is preventing the entire content stylesheet from being parsed.

To get this resolved, edit your custom footer. Find the Social Icon buttons and correct the background hover color that you have inserted incorrectly.

background-image:linear-gradient(to top right,#2b6940,#2b6940,#2b6940,#2b6940

Understand why this breaks the whole page – when a browser encounters an unclosed bracket, it does not stop at the end of that rule. It continues consuming the stylesheet looking for the missing bracket, discarding everything it absorbs. Your footer CSS is output before your page content CSS, so every content style after that point is thrown away. This is also why the builder looks correct: the editor renders element styles individually rather than as one combined stylesheet, so the error never cascades there.

Resolve two secondary issues once styling returns – first, one image still points to http://team.secdns.co/... (a leftover demo asset from the Gridorama template), which browsers block as mixed content on an HTTPS page; please upload that graphic to your Media Library and re-select it. Second, one cell has an unresolved background image showing as url(237:full) instead of a real file path; please re-select that image on the element. Neither of these caused the layout failure, but both should be corrected.

Kindly let us know how it goes.