Tagged: , ,

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
  • #192484

    I get it that you don’t want to support Typekit, but not everyone wants Google’s fonts. I am not asking you to support everyone’s font services, but there are a lot of people using it and a lot of people requesting support. Other themes have support.

    But, if you do not plan to consider or support in the future Typekit, PLEASE allow us the ability to shut off your Google fonts integration. It is making it a nightmare to integrate any other font service.





    You don’t need to do anything special to not use google fonts. Just choose “no font” from the dropdown for the google font choice.

    Just an FYI as well, self bumping puts your items to the back of our queue and does not move it to the front. I keep an eye out for self bumps the first time but just keep that in mind for the future.



    Understood. I was not sure if you would still see them if they got lost deeper in the list. My apologies.


    Nope! We actually see and answer every single post that comes through unless it gets resolved before we get to it. Something like 100-200 a day I think at this point.


    Howdy guys. I have the same issue, but seems the ‘no font’ choice no longer exists in the menu? Also, I tried to select the ‘select’ heading or anything that wasn’t a font name, but couldn’t find a way to do so.

    • This reply was modified 1 year, 9 months ago by  itchybrain.


    The following code in functions.php will remove the Google Fonts inclusion:

    add_action( 'init', 'enfold_customization_switch_fonts' );
    function enfold_customization_switch_fonts() {
        global $avia;
        $avia->style->print_extra_output = false;



    It is really frustrating to have to do these things in functions when they used to be easier in the settings. Why can’t we just have options to disable it, period? The code above did not work until I hard coded the css with important tags.


    @Jason E… mine didn’t disable either… what were the CSS important tags you mentioned?


    I just defined the fonts manually in the child theme css file, but this can be done in the quick css area as well.

    This is what I used in this one case, but your’s will vary, based upon the typeface you are using.

    body {
    font-family: “colosseum”,sans-serif !important;
    font-style: normal !important;
    font-weight: 300 !important;

    h1, h2, h3, h4, h5, h6 {
    font-family: “colosseum” !important,sans-serif;
    font-style: normal !important;
    font-weight: 500 !important;



    Thank you @Jason for sharing the tips :)

    @itchybrain please let us know if it worked for you.



    Thanks guys. I’m familiar with specifiying fonts using CSS, my confusion came from my dev site retaining the ‘previously set’ fonts even after I put the function in, so I thought it hadn’t worked. But it did, and I can manage the fonts ok. What I was hoping to find was an option in the Google font pulldown lists that just said ‘don’t use any of these’ or some such button to check/uncheck usage of the facility. Maybe a wishlist item, i’ll pop it in the wishlist.
    Thanks for your responses, much appreciated.


    I agree. For those not wanting to use Google fonts, it inserts extra code and overhead that is not needed. Plus, it also portrays the effect of there being no other choices than Google Fonts, when there are many. In my opinion, if Enfold is to support custom fonts, it needs to do so in a way that is agnostic, or else leave it to plug-ins completely. Just my opinion, but the same issues keep coming up year after year and we need a better solution than just hacking things to make them work.



    I kinda agree with you, the fonts functionality is certainly something that can be improved, please post your request here so Kriesi can see it.

    Best regards, 

Viewing 14 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic.