Viewing 12 posts - 1 through 12 (of 12 total)
  • #146048
    MaartenPex
    Member
    Post count: 21

    Dear Team,

    After updating to the latest version of the theme my @font-face in my stylesheet does not to seem working. Before I encountered difficulties as well with this and it had me importing the fonts through placing them in the font folder of the parent theme, because adding them to the child theme in a fonts folder did not seem to work.

    Can you resolve the issue for me. In such a way that when I update to the latest version of the theme I do not encounter this anymore?

    your help is appreciated,

    Regards,

    Maarten

    #146398
    Swift Ideas – Ed
    Keymaster
    Post count: 15264

    Getting an incorrect password error.

    – Ed

    #146402
    MaartenPex
    Member
    Post count: 21
    This reply has been marked as private.
    #146494
    MaartenPex
    Member
    Post count: 21

    Dear Ed,

    I checked the password I sent in the last reply and it should be OK. Could you please have a look.

    Regards,

    Maarten

    #146508
    Brookebot
    Member
    Post count: 112
    This reply has been marked as private.
    #146543
    Swift Ideas – Ed
    Keymaster
    Post count: 15264
    #146599
    MaartenPex
    Member
    Post count: 21
    This reply has been marked as private.
    #147016
    Swift Ideas – Ed
    Keymaster
    Post count: 15264

    Thanks for the reply @Brookebot, really appreciate it.


    @MaartenPex
    – your font links are all returning 404s, hence why it isn’t working. @brookebot kindly offered her child theme solution, which is this:

    =======================================================

    My @font-face works great w/ my child theme and this is how I did it:

    I added this to child theme’s functions.php (child theme name is ‘brookebot’):

    // Add Fetching Font
    function myfetchingfont_headlink() { ?>
    <link rel="stylesheet" type="text/css" href="http://brookebot.com/wp-content/themes/brookebot/fetching-font/fetching-regular.css">
    <?php }
    add_action('wp_head', 'myfetchingfont_headlink');

    Then add entire font folder named “fetching-font” to child theme folder which contains:
    fetching-regular.css
    fetching-regular-webfont.woff2
    fetching-regular-webfont.woff
    fetching-regular-webfont.ttf
    fetching-regular-webfont.svg
    fetching-regular-webfont.eot

    Here are the contents of the fetching-regular-webfont.css file:

    @font-face {
        font-family: 'fetchingregular';
        src: url('fetching-regular-webfont.eot');
        src: url('fetching-regular-webfont.eot?#iefix') format('embedded-opentype'),
             url('fetching-regular-webfont.woff2') format('woff2'),
             url('fetching-regular-webfont.woff') format('woff'),
             url('fetching-regular-webfont.ttf') format('truetype'),
             url('fetching-regular-webfont.svg#fetchingregular') format('svg');
        font-weight: normal;
        font-style: normal;
    }

    And finally to put it to use, here is an example of CSS for using it in my Custom CSS/JS box:

    h1, h2, .impact-text-large {
    font-family: 'fetchingregular';
    }

    I also had trouble getting the @font-face to work with my child theme until I finally figured out how to put everything in its right place. Maybe this can help solve issue. Just ignore if this does not help.

    ===============================

    Hope that helps!

    – Ed

    #147022
    Brookebot
    Member
    Post count: 112

    Typo correction:

    Here are the contents of the fetching-regular-webfont.css fetching-regular.css file:

    #147091
    MaartenPex
    Member
    Post count: 21

    Dear both,

    Still no luck with the solution offered by Brooke. Strangely enough all was well since the last update. @ed if my font links are returning 404s what does that indicate? As I do not see what is wrong about the links. They direct to the webfonts.

    Please help me out on the matter which should be a simple task, but is taking up at least three days already.

    Regards,

    Maarten

    #147166
    MaartenPex
    Member
    Post count: 21

    Dear All,

    Just found the solution to my problem. As it turns out the solution of Brooke was sufficient. The thing that was not, was the webfont converter I used. It made wrong conversions of the fonts. Font Squirrel turned out to be my hero. It converted the font as it should have done in the first place.

    Thanks for the help and time to Brooke and Ed,

    Regards,

    Maarten

    #147290
    Swift Ideas – Ed
    Keymaster
    Post count: 15264

    Glad to hear it!

    – Ed

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

You must be logged in and have valid license to reply to this topic.

License required for one of the following items
Login and Registration Log in · Register