Hi Peter,

The template.css file also uses an extra class name, which, for the browser, is "stronger" than the override from Custom Style Preset settings. In that case, don't waste time, and just use a simple Custom CSS to set RED color

.fixed-menu #sp-header #sp-menu .sp-megamenu-wrapper .sp-megamenu-parent .sp-menu-item.active > a, 
.fixed-menu #sp-header #sp-menu .sp-megamenu-wrapper .sp-megamenu-parent .sp-menu-item:hover > a, 
.fixed-menu #sp-header #sp-menu .sp-megamenu-wrapper .sp-megamenu-parent .sp-menu-item:focus > a, 
.case-studies-page.view-dynamic #sp-header #sp-menu .sp-megamenu-wrapper .sp-megamenu-parent .sp-menu-item.active > a, 
.case-studies-page.view-dynamic #sp-header #sp-menu .sp-megamenu-wrapper .sp-megamenu-parent .sp-menu-item:hover > a,
.case-studies-page.view-dynamic #sp-header #sp-menu .sp-megamenu-wrapper .sp-megamenu-parent .sp-menu-item:focus > a 
{color: red; }

I get that we can do overrides in custom.css - I guess my question is more, why do you bother having these options in the template manager if you're just going to override them with template.css.

This makes no sense. We're fine, becuase we're developers and know how to do this, but it makes it very confusing for our clients. Why would you guys build in this wonderful facility into your templates, only to override them with template.css forcing people to then require the use of custom.css to make a colour change that should be facilitated via changes in the template manager?

Seems very backwards to me.

I get that - but this happens all the time, across multiple templates.

Seems you guys have these great features that allow customers to make changes via the template manager, only to discover these don't work because the template developers aren't doing their job properly or checking their work.

If this feedback could be passed onto them, that would be great.

Ok, I will.