Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author lilaeamedia

    (@lilaeamedia)

    Shapeshifter, thanks for the heads up.

    I get something on this topic every few days or so. The reality is that the vast majority of themes (including the WP default themes through twenty-fifteen, which isn’t even out yet) use get_stylesheet_uri() and do not use the so-called “new” method at all.

    Therefore the only way for a plugin to be sure to load the parent styles first and then override with the child styles without additional functions is @import.

    We could add a function to the child theme functions.php that dequeues the parent and child stylesheets to get to a baseline, then enqueues the parent and child to get the correct cascade order, but that starts to smell a lot like spaghetti code to me.

    I will come up with a solution in a future release that will calm the Google performance police but for now, having seen hundreds of good, bad and ugly themes come across my support desk, CTC uses the best practice for the many.

    Thread Starter Shapeshifter 3

    (@shapeshifter-3)

    Quick Response APPRECIATED !!

    Plugin Author lilaeamedia

    (@lilaeamedia)

    I am actually testing a solution for this as we speak.

    Plugin Author lilaeamedia

    (@lilaeamedia)

    UPDATE: As of version 1.5.5, CTC will no longer use @import to load the parent theme stylesheet.

    The new version will provide the option to install an action that loads the parent stylesheet via wp_enqueue_style. For themes that already handle their core styles separately from the style.css file, you will now be able to skip the action.

    This complies with the move away from @import and also reduces the overall load time.

    We plan to release v.1.5.5 later in November, 2014.

    Thread Starter Shapeshifter 3

    (@shapeshifter-3)

    Thank you, Sir!

    Plugin Author lilaeamedia

    (@lilaeamedia)

    Version 1.6.0 is available and includes a new “Parent stylesheet handling” option.

    You can now choose between using wp_enqueue_style, @import or “none”.

    A bunch of other new goodies, too. I gave you a mention for kicking me in the arse about this.

    Thread Starter Shapeshifter 3

    (@shapeshifter-3)

    lilaeamedia,

    Super Duper Thank You…

    I’ve already updated your plugin and changed my Child Themes in 3 sites!

    I really like the 3 different options you offer. I’ve noticed in the past that some Theme Developers were already doing this, so your “none” is a good option for Themes from them.

    Please accept my apologies if I came across too pushy. I just think that you offer a Great Plugin, and wanted it to be the “Best It Could Be”.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘WordPress Codex Child Theme Changes ?’ is closed to new replies.