Support » Plugin: Options for Twenty Twenty-One » Its good, but I stayed with my Child theme

  • bdew


    I installed this plugin and initial results were great. Instead of the usual plugin Settings panel it replaces the standard Customize drop down which is a neat idea.

    But this plugin adds css to each page where my Child Theme could not override the plugin’s css. Eventually, conflicts between the plugin and my Child Theme forced me to disable this plugin. (If they had positioned their plugin before the Link statements I might have kept it.)

    So, I guess, if you have or are familiar with Child Themes then continue that way. If not then this is a great, almost essential, add on to TwentyTwentyOne.

Viewing 1 replies (of 1 total)
  • Plugin Author Oliver Campion


    Many thanks for your review.

    Although the plugin works well with child themes, it is designed specifically so that users don’t need to go to the trouble of creating one … knowing that their theme is un-modified and will always be able to be updated to the latest version without worrying.

    That aside, the problem you are describing is caused because, as you say, the plugin places the CSS after stylesheets enqueued using wp_enqueue_style() function such as that of your child theme.

    But this is by design of WordPress Core, not our plugin …

    The plugin enqueues the customizer CSS using the wp_head hook as per the documentation in WordPress Codex.

    Our recommendation in the event that you find that the plugin is overriding CSS and you are unable to force your CSS to work (be it with more specific CSS selectors or even using the !important flag) then you can always turn that specific option off in the customizer to prevent the plugin creating the offending CSS in the first place. If anyone needs help with this, we are always on hand to do so 🙂

    Hope that helps if you choose to reactive the plugin.


Viewing 1 replies (of 1 total)
  • The topic ‘Its good, but I stayed with my Child theme’ is closed to new replies.