• The changelog for Version 4.0.6 (Date: 2/2/19) contains this notation:

    – Removed some features as per WordPress requirements

    Could you indicate which specific features have been removed?

Viewing 2 replies - 16 through 17 (of 17 total)
  • Thread Starter Abigailm

    (@abigailm)

    @spartelfant — you don’t have to do anything with plugins or modifications to core files to set up all font choices on a child theme — just put all specifications in your child style sheet. All of the extra fonts are still available to the theme, they just can no longer be set via customizer.

    If you set things up with your style sheet, you won’t be able to modify those particular options using the customizer. But you also don’t have to worry about specifications being overridden with a theme update if they are hardcoded into the child style.css file. And once you are comfortable using the style sheet, you may find that to be an easier and faster option than using the customizer in any case. The specs probably do all need to have the !important notation to override the inline styles set by the customizer.

    So here is what I would suggest for developing your child theme.

    Use view source to find and copy all the inline styles that show up in the section:

    <style id='evolve-style-inline-css' type='text/css'> .... </style>

    Then you can simply override anything you choose in your style.css file.

    For example, if the inline style (set via customizer) shows:

    body { font-size: 1rem; font-family: Roboto; font-weight: 300; color: #212529; }

    And if you want the Montserrat font instead, could put this in your style.css:

    body {font-family: Montserrat !important;}

    • This reply was modified 5 years, 9 months ago by Abigailm.
    • This reply was modified 5 years, 9 months ago by Abigailm.
    • This reply was modified 5 years, 9 months ago by Abigailm.

    Thanks @abigailm! I was hoping to make the fonts available through the customizer again, so that less technically inclined people working on a specific website in the future would be able to pick a different font more easily. Though there is also something to be said for your approach, since it is less likely to break with future theme updates (not to mention a lot less complicated). Right now it is like you said, the theme still fully supports all fonts, it’s just not showing them in the customizer. As an extra insurance I will probably also have my child theme import the specific Google fonts I picked, just to be sure they continue to be available (even though evolve is already very good about maintaining backwards compatibility).

Viewing 2 replies - 16 through 17 (of 17 total)
  • The topic ‘Question re changelog for 4.0.6’ is closed to new replies.