WordPress "Customizer" over-riding child theme css

  • jiraiya

    (@jiraiya)


    11 years, 6 months ago

    I am not new to the web dev/design game but for sometime I have been dealing with a ridiculous but annoying issue with my child themes. In the past when I created child themes the child theme styles would always take priority. However I notice that if you experiment with the “Customize” panel in the appearance section of the admin dashboard, it does not seem possible to undo those changes and turn the customize settings off.

    For example, I have a 2012 child theme. I at one time took a look at the different fonts in the “Customize” panel. However it was only to view them since I always like to code all the look and feel settings myself in my child theme rather than relying on options in mysql.

    The issue now is that my child theme css will not be honored. The “Customise” panel is taking precedence. The only workaround is to copy the effected child theme CSS into the “Edit CSS” area of the apprearance section which of course is honored as it is loaded in-line I believe. Howevere this is inefficient and annoying to do.

    Does anyone else have this issue or has anyone found a solution for it.

    Thanks,
    Barry.

Viewing 4 replies - 1 through 4 (of 4 total)
  • stephencottontail

    (@stephencottontail)

    11 years, 6 months ago

    That’s basically how the Customizer is supposed to work; it allows the end user to override certain aspects of the theme without having to write custom CSS. And yes, unfortunately, it doesn’t appear that you can easily undo the changes made by the Customizer.

    If you have MySQL experience, you could try deleting or editing the database directly. Backup your database before doing this. The record(s) you’re looking for are in the wp_options table and the row will be named something like xxx_theme_options. Again, backup your database before doing this.

    Thread Starter jiraiya

    (@jiraiya)

    11 years, 6 months ago

    Hey sorry about the late reply. I ended up very busy for a few days and the post slipped my mind. Also for some reason I have not been getting notified by email of replies. Yeah you have pretty much confirmed my fears on this one. I had thought as much myself. It’s a pity that it works this way since it really screws with the way child themes are supposed to work in my view. Is there a way to disable the customiser for a child theme altogether?

    Thanks,
    Barry.

    stephencottontail

    (@stephencottontail)

    11 years, 6 months ago

    You could try the suggestion in this thread: https://ww.wp.xz.cn/support/topic/feature-request-one-line-of-code-to-disable-all-customizer-stuff?replies=2

    rahyrs

    (@rahyrs)

    11 years, 1 month ago

    Sorry if this is not an approriate post in this thread.

    What if in the contrary:

    I customized my theme (not child theme) using Customizer.
    Then I made a child theme from that theme.
    Activate the child.
    Then I see that all customization via Customizer is lost (not loaded).
    I have to do all over again with my child theme active.

    Is there any way to safely copy the customization from parent theme to child theme in this case? I suspect (and read above answer) that the customizer keeps everything in database. But in what table and under what rows?

    Thank you.

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

The topic ‘WordPress "Customizer" over-riding child theme css’ is closed to new replies.