What’s the difference between adding css stuff in the Frontier Options “Custom CSS” vs. editing the Child’s style.css? It seems like when I try putting stuff in the Child’s style.css it is ignored, while the “Custom CSS” works every time.
From a best practices standpoint does it make any difference? What am I probably doing wrong that the Child’s style.css is not picked up?
The theme’s custom css function prints the css codes on the page, you see the codes when you click “view source” on your browser. The child theme’s style.css is a separate file that is called by the page.
What am I probably doing wrong that the Child’s style.css is not picked up?
possible things I could think of:
1. You’re using the wrong ID or class.
2. Wrong property or incorrect syntax.
2. CSS Specificity
3. Caching. You’re using a caching/minifying plugin but have not refreshed the cache yet so the old style.css is being served instead of the recently modified. Browser cache might also need to be cleared.
It’s probably a caching issue in your case since you mentioned that the same codes work when added though the theme option.
Viewing 2 posts - 1 through 2 (of 2 total)
The forum ‘Frontier’ is closed to new topics and replies.