Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author John Regan

    (@johnregan3)

    You are correct, it is not adding a new custom.css file or folder anywhere on your site.

    It saves your CSS into the WordPress options table in your database, and when it is called in your <HEAD> it adds the CSS to your page via a custom link. Because this is saved in the database, it will not be overwritten by a theme update.

    If I can add any more information to help you out, please let me know!

    John

    Thread Starter delidoodle

    (@delidoodle)

    I have used your plugin on sites where I am only making a few modifications. Works quite well. When making multiple modifications I prefer working with a text editor using a child.css file in the child theme directory. Does updating a purchased child theme like Canvas/Uno leave the custom.css alone? I have searched ww.wp.xz.cn without success. Thanks.

    Plugin Author John Regan

    (@johnregan3)

    Hi delidoodle,

    I’m glad you’re enjoying the plugin!

    I don’t know the specifics of updating paid child themes, but it’s safest to assume that the custom.css will be overwritten. As you probably know, the WP method of updating themes does delete then replace the theme with the latest version, and I’d assume that updating a paid theme would do the same.

    Personally, I’m looking forward to the day when we can create “grandchild” themes to customize child themes. 😀

    I hope this helps!

    John

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

The topic ‘Simple CSS vs custom.css’ is closed to new replies.