- This topic has 24 replies, 4 voices, and was last updated 7 years, 6 months ago by ProDesigns.
-
AuthorPosts
-
July 16, 2017 at 6:55 am #6796ProDesignsKeymaster
Hi @satojin,
Thanks for 5 stars and good feedback.
July 16, 2017 at 6:58 am #6797ProDesignsKeymasterHi @dbookbinder,
Try to compare your child theme with you created for your friend. If it does not work, try to create new child theme and add codes one by one from your existing child theme.
Thank you.
July 16, 2017 at 5:33 pm #6798AnonymousInactiveI restored the child theme from a backup of the site I made a few days ago and updated it with my latest tweaks. It seems to work fine now.
One thing that puzzles me is why the child theme was affected by the glitch in the 2.03 theme release. I thought the main point of child themes was to protect against changes to the main theme. Do you know why that didn’t work in this case?
I have given you a ***** review on WordPress.org, by the way.
– David
July 17, 2017 at 3:49 am #6799AnonymousInactiveHey there! Sorry, I have not responded to my initial comment – it’s been a very long day. Thanks for the update, most everything appears to be back to normal. One quick bug though – my header font doesn’t change no matter which font I choose. Kind of odd. I cannot remember what font I was using prior to the 2.0.3 update, but I know last night I changed it to was Montez. I have tried under both the default fonts (H1) and the new header font category.
July 17, 2017 at 4:57 am #6800ProDesignsKeymasterHi @hopeinthechaos,
Are you using Blog Way or Blog Way Plus? Blog way do not have option to change font. Please let us know which theme and how have you used font on your site.
Thanks.
July 17, 2017 at 5:15 am #6801ProDesignsKeymasterHi @dbookbinder,
Thanks for feedback and 5 stars. Child theme in version 2.0.3 is not working because of bug in CSS file. Child theme loads CSS from parent theme so same bug have been reflected in child theme too.
Anyway, you got your child theme working again. Congratulations!!!
July 17, 2017 at 12:28 pm #6802AnonymousInactiveOkay, I understand. Then what is the best way to temporarily recover, in case there’s a bug in the future? I thought replacing the theme with the 2.01 version would do it, so I deleted Blog Way 2.03 and reinstalled 2.01, but the CSS problem didn’t seem to go away. Are themes cached, somehow, so a cache must also be cleared if I wanted to revert back to an earlier version of the theme while bugs were being worked out?
Thanks. Using third-party themes is new to me, and updates to themes never caused a problem for me before.
July 17, 2017 at 2:16 pm #6803AnonymousInactiveThanks for the reply! I am using Blog Way and I was able to change the font for my header using the 2.0.3 (the only thing I liked about the update). In the customize section it does show a header font so I thought maybe that was not working correctly.
July 18, 2017 at 12:28 am #6804AnonymousInactiveIf you poke around in the style.css file for the Blog Way theme, you can find the settings for some of the text elements, then copy them from style.css to a child theme’s style.css or, if you have JetPack installed, you can add them to the theme as “Additional CSS.” It’s a pretty big text file, and most of font-related settings appear to be about halfway through the file in a section called Main Index. If you don’t know CSS (I don’t), the changes you’ll be able to figure out to modify the defaults will be somewhat limited, but changing the font and font size are pretty obvious.
Hope this helps!
David
July 21, 2017 at 8:42 am #6805ProDesignsKeymasterHi @hopeinthechaos,
Hope @dbookbinder answer will help you.
-
AuthorPosts
- You must be logged in to reply to this topic.