CSS problem

Permalink
I'm at wits end... not sure where to even look now. I was working with the Chameleon theme, and updated a font. This broke the theme slightly, and the main.css file no longer matches what chrome is showing in dev tools.

The actual file looks like this:
.style-wrapper h1 {
/* customize_h1_title */font: normal bold 36px arial;/* customize_h1_title */
/* customize_h1_title */color: #000000;/* customize_h1_title */
margin-bottom: 10px;
text-transform: uppercase;
line-height: 38px;
}


But Chrome Dev says this:
.style-wrapper h1 {
/* customize_h1_title */ font:normal bold 36px Book Antiqua; /* customize_h1_title */
/* customize_h1_title */ color:#000000; /* customize_h1_title */
margin-bottom: 10px;
text-transform: uppercase;
line-height: 38px;
}


I looked in the pagethemestyles table of the mySQL database, it looks like it's correct.

Anyone have any ideas? (yes, I've cleared the cache and restarted everything)

dbradley
 
mhawke replied on at Permalink Reply
mhawke
Is there a public URL we could have a look at?

A few questions...

When you say you've cleared the cache, was that only your browser cache or have you turned off all the C5 caching at 'Dashboard->Systems and Settings->Cache and Speed Settings'?

Is the style being over-written by typography.css?

When you say you 'updated a font', how did you do that? Was it through the customization under 'Themes' or did you change it in the main.css file itself?
dbradley replied on at Permalink Reply
dbradley
Thanks, we figured it out. It was related to an addon that was updated right around the same time.
mhawke replied on at Permalink Reply
mhawke
Glad you got it worked out.

It would be helpful to others who pass this way in the future if we knew which add-on was causing the issue.
dbradley replied on at Permalink Reply
dbradley
I contacted the author and let them know.
mhawke replied on at Permalink Reply
mhawke
Sorry, that's not my point. If someone else runs into the same issue you had and finds this thread, they would like to know which add-on was causing the problem.
dbradley replied on at Permalink Reply
dbradley
I know what you meant. This situation will not affect anyone else as it's a custom add-on.
mhawke replied on at Permalink Reply
mhawke
No problem, Thanks.