CSS changes in Pro Cornerstone not reflected on front end

[cglobal]

This is extremely frustrating, and it is not the first time this has happened…

I’ve got a fresh and mostly empty / clean WordPress install that’s running Pro. I will work on building out a new page using the Cornerstone page builder that’s now built into Pro, utilizing some custom CSS on the page, and all of a sudden a change to the CSS will be reflected in the page editor but not on the front end! An example of this is would be removing all the custom CSS for the page, then saving the page, then viewing the page.

The theme is validated and everything is up to date. There are plugins in the install because they are in the plugins folder. Most of them have never been activated since resetting the install.

I have tried everything, including clearing the style cache in Pro’s settings as well as activating my hosts’s cache plugin to clear caches.

[Prasant]

Hello @cwsglobal,

Thanks for asking and I am sorry for the trouble you are facing. However, I am glad that you reached out for help.

I checked the page and as per your instructions I removed all the CSS and saved the page and checked the front page I could see the changes. I then rolled-back the CSS and then also I can see the changes getting reflected.

To test further in one of the element I made few changes and they are reflected on the front page. Have recorded a screencast. Please take a look. https://cloudup.com/ck2Q8-bFiKK

I am also quite curious as in why you are using custom CSS for things that can be easily changed using the Visual builder. Ofcourse CSS does gives you lot more flexibility but for things like changing font size, margin, alignment can be made using visual builder. Indeed it’s your personal choice and you are free to make the changes as per your requirement but I was just thinking that.

Thanks.

[cglobal]

Hi @Prasant,

Thank you so much for taking a look! It all of a sudden appears to be working now. And it definitely was not yesterday. So I am not sure what is or was going on. All is well now, though.

As for why I am using custom CSS, the reason is simple. There will be more than a hundred pages that utilize a like page layout, and I would like to define the properties globally. Does that make sense? This is just a test page I am using to design the template. The styles will ultimately go in the global custom CSS.

The draw to Cornerstone is the ease of creating and editing pages, and I definitely appreciate the ability to create one-off pages with settings specific to that page. But when trying to design a fluent user experience across a website, it is not possible to maintain consistency if everything is defined on the per-page level.

Thanks again for the help!

[rad]

Hi there,

Yes, it’s only logical to make it global custom CSS to make it re-usable.

Another solution is using v2 elements and save its styling as Preset, then you can apply the same preset to another page’s element. Still, too long process if there are multiple pages and content.

And you’re most welcome!