I just updated to 2.6
It seems possibly the loading order of the child theme custom style.css has changed so that they’re not overriding existing parent enfold css?
Is this the case?
Edit:
I’ve moved the css customizations from my child theme style.css to the Quick CSS in theme admin and now css changes are working so that indicates that something must have changed in regards to the priority of the child theme style.css
Anything one can do to fix this?
Hey ttem!
Looks like Kriesi changed from registering to enquing. I’ll add in a fix for this and it will get rolled out with the next update.
Regards,
Devin
Hi Devin / Kriesi
If you could make this a priority – as this updated has just killed 1 development site – and I will not upgrade the additional 5 sites until the custom child style.css has been give priority.
Many thanks!
If you want to apply it yourself its very small from the looks of it. I’m currently updating downloading the update and pushing things to my live server so I’ve not tested this:
In functions.php look for:
wp_enqueue_style( 'avia-style' , $child_theme_url."/style.css", array(), '1', 'all' ); //register default style.css file. only include in childthemes. has no purpose in main theme
Change the first part (wp_enqueue_style) to wp_register_style and it should then get enqueued further down for child themes like its supposed to.
Final line:
wp_register_style( 'avia-style' , $child_theme_url."/style.css", array(), '1', 'all' ); //register default style.css file. only include in childthemes. has no purpose in main theme
Thank you Devin changed enqueue to register – that fixed it.