A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
AI OnAI Off
Remove display templates settings from SaaS CMS
Hello Johan and the Community,
it looks like this question has been sitting unanswered for almost a month!. While Johan has likely moved past this, I'm posting our team's solution for the benefit of others who run into this common issue.
The Root Cause
This error occurs when older or legacy content in your application is still calling a CSS style property that has since been removed, deprecated, or renamed in your current framework/library. The system can't find the style, which throws the error.
Our Project Workaround (Manual Fix)
As far as we know, there isn't a simple, automated tool to globally fix these historical references. Our method requires manual intervention:
-
Identify the Source: Trace the specific content component on the page.
-
Manually Correct: go to the style button option:
-
Update the style property name to its modern equivalent, if you don't see error value it is fine, it just required an update to trigger the save.
-
This is tedious for large projects, but for us, we were getting it for some limited components only.
Community Question: Has anyone developed or found a script to scan a codebase for these types of deprecated style calls? It would be a huge time-saver!
Thanks
Mahendra
Dec 15, 2025 11:41
In some way I have created a situation where I get this validation error message when I try to publish certain older experience pages:
Display setting with key 'colorScheme' does not exist on display template with key 'SectionDefault'.
Any advice on how to clean this up?