Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • So…yeah, child themes. That’s what I’ve done in the past. But I downloaded this ColorWay theme, was about to make my child theme, dug into the CSS, and found this line, which is why there are all these posts asking about custom.css:

    To make it easy to update your theme, you should not edit the styles in this file. Instead use the custom.css file to add your styles. You can copy a style from this file and paste it in custom.css and it will override the style in this file. You have been warned! 🙂

    Even those of us who have used a child theme before are sitting here scratching out heads thinking, “is there something different about this theme that we don’t know”, and second-guessing the whole child theme thing. Why wouldn’t a developer suggest the standard practice? What’s more, as others have pointed out, what they direct you to do just doesn’t work.

    I’m going to go in and try doing the child theme as I had originally intended, but to anyone reading through this chain and feeling puzzled about the custom.css in ColorWay, you’re not alone and you’re not crazy.

    In the child-theme copy of front-page.php, replace all occurrences of the function get_template_directory()

    with

    get_stylesheet_directory().

    get_template_directory() always paths to the parent. get_stylesheet_directory() paths to the current child-theme directory.

    I was having the same problem with Zerif Lite and was about to pull my hair out when I stumbled upon this difference between the two functions. (I’m a WP theme modding newbie.) So, that’s what fixed it for me. So far so good. If there’s some reason why front-page.php should be pulling from the parent for this theme, I haven’t figured out why. Let me know if you know something I don’t.

    Hope this helps someone. I was about to give up on this theme, but I like it so much, I decided to stick to it until solved.

Viewing 2 replies - 1 through 2 (of 2 total)