Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #1194369

    Dear Kriesi-Mods!

    I’m building a new website and since last week I’m having trouble with the displayed font in some elements. The main content like text and headlines is ok (heading: Asap bold / text: roboto regular – both fonts are imported zip-files).

    But a wrong font is displayed for example in:
    – Main menu submenu links
    – icon list
    – footer menu
    – simple slider

    And probably in more elements (for links see private content). It worked well for weeks but all of a sudden this error occured.

    I tried a few things like importing the fonts once again or changing fonts. Nothing worked.

    What to do?

    Thx in advance

    #1194673

    Hey larsjohow,

    Please send us a temporary WordPress admin login and login URL so that we can have a closer look. You can post the details in the Private Content section of your reply.

    Best regards,
    Rikard

    #1194743
    #1194987

    Hi,

    Thanks for that. I removed this from your Quick CSS:

    li {font-family: 'Roboto'!important;
        font-style: normal!important;
        font-weight: 400!important;
    }

    And it seems to be back to normal after that. Please review your site.

    Best regards,
    Rikard

    #1197982

    Thx a lot!
    I put the code into the Quick CSS because I don’t want the heading-font (Asap) in the submenu links. So I just put the Code back in and however it now works pefectly again.

    #1198000

    UPDATE: It didn’t work on the mobile menu. So I again deleted the code in Quick CSS. Is there a possibility to have Roboto (the normal text font) for submenu links?

    • This reply was modified 1 week, 6 days ago by  larsjohow.
    #1198027

    One more question: The &-sign is not displayed correctly in Special Heading. See here “Einsatzgebiete & Module”: http://h2860849.stratoserver.net/wordpress/index.php/logbuch/

    I would really like to use this sign in headings but I need to use Special Heading because in regular text/heading the font size doesn’t change on mobile devices, which of course causes real problems on small displays.

    Once again thx in advance!

    #1198218

    Hi,

    Thanks for the update. I couldn’t see any problems on your mobile menu, could you post a screenshot of it please? Or maybe I’m misunderstanding you, do you want the Roboto font for the sub menu items?

    You can remove the styling from the special amp by adding this CSS:

    .special_amp {
        font-family: inherit;
        font-style: normal;
        font-size: inherit;
        line-height: inherit;
        font-weight: normal;
    }

    Best regards,
    Rikard

    #1198274

    “do you want the Roboto font for the sub menu items?”

    Yes, exactly! The problem is: I now put back this code into Quick CSS:

    li {font-family: 'Roboto'!important;
        font-style: normal!important;
        font-weight: 400!important;
    }

    So now the menu on desktop-screens works well. But on mobile displays the font is completely wrong again (on all levels). And as I mentioned above, it worked well a few weeks ago.

    • This reply was modified 1 week, 5 days ago by  larsjohow.
    #1198506

    Hi,

    Thanks for the clarification. Please try this CSS instead:

    nav.main_menu .avia_mega_div ul li a, #av-burger-menu-ul ul.sub-menu li a span {
        font-family: 'Roboto'!important;
        font-style: normal!important;
        font-weight: 400!important;
    }

    Best regards,
    Rikard

    #1199033

    I’m afraid that does not work. Not on big screens and not on mobiles either. I left that code on Quick CSS so you can check.

    #1199655

    Hi,

    Thanks for the update. Please try this CSS instead:

    nav.main_menu .avia_mega_div ul.sub-menu .avia-menu-text, #av-burger-menu-ul ul.sub-menu li a span {
        font-family: 'Roboto'!important;
        font-style: normal!important;
        font-weight: 400!important;
    }

    Best regards,
    Rikard

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

You must be logged in to reply to this topic.