Can you post a link to your site with the child theme active?
You can view it here: http://www.vitabliss.co
The entire site used to be in shades of green with Patua One as the font.
I can’t tell exactly which CSS file has the error because of your optimizing plugin, but at line 6894 of your giant concatenated stylesheet you’ve got an extra opening bracket:
#colophon .widget-wrap {
{
color: #6ea624
}
which is causing parsing errors down the rest of your stylesheet. After you find the file that has the error, you’ll likely have to clear your optimizing plugin and run it again.
Thank you for taking the time to go through that! That was my custom styling so I knew exactly where to find it and I cleared the optimizing plugin’s cache after fixing this. The problem still persisted so I checked the site in a different browser and also tried deactivating the optimizing plugin entirely. EDIT: I see the colophon at the bottom is now displaying in the appropriate color, but everything else is unchanged.
I’ve deactivated that plugin for now, if it helps pinpoint the file.
Everything seems to be okay with your site now except for the font, which doesn’t appear to be loading correctly. How are you loading the Patua One font?
I put the code through a CSS lint and it didn’t find any more errors. Then I decided to go through the code elements on the page manually to see if I could spot if I forgot to put something in. That’s when I noticed some elements’ names appeared to have changed. I updated the child theme’s CSS with the new names and those elements started working.
I updated from version 1.2 to 1.5. Is this something that happened in between those version? Is there a changelog containing the updated names?
For now, I copied the @font-face rule directly from Google into the child theme’s CSS till I figure out what happened to the previous way I was getting the fonts (via linking to the stylesheet as Google instructs.)
I updated from version 1.2 to 1.5. Is this something that happened in between those version? Is there a changelog containing the updated names?
You can check out previous versions of the theme at https://ww.wp.xz.cn/themes/interface/developers/ Developers also typically provide a changelog in readme.txt (or similarly-named file), although it usually doesn’t go into that much detail.
For now, I copied the @font-face rule directly from Google into the child theme’s CSS till I figure out what happened to the previous way I was getting the fonts (via linking to the stylesheet as Google instructs.)
What was the exact code you used to link to the stylesheet and what file did you add it to?
The code was from Google Fonts (<link href='http://fonts.googleapis.com/css?family=Patua+One' rel='stylesheet' type='text/css'>) but what I can’t remember is where I put it. As you must have guessed, it’s been a while since I’ve come back to the site. I suspect it might have been somewhere in the parent theme since I can’t find it referenced anywhere in the page source.
I think the solutions beyond this point are my responsibility now, since it appears the theme itself is working fine, so I’m going to close this support thread. Thank you for helping me figure out the issue! 🙂
