Support » Plugin: Fonts Plugin | Google Fonts Typography » Post Title header links no longer respect “Headings Typography” setting

  • Resolved egcarpenter

    (@egcarpenter)


    Hi there,
    I’m testing an upgrade to the Google Fonts plugin on my staging instance (old version: 3.0.13, new version: 3.0.17). With the upgrade, my list of posts is no longer displaying the correct font for Post Title links. Details about my setup and what is breaking below.

    Setup: A list of posts each containing a Post Title element displayed as an H2, with a hyperlink contained to link to the post’s page.

    Google Fonts settings:
    “Headings Typography” – “WindSong”
    “Title and H1 Typography” – “Spectral SC”
    “H2”, “H3”, etc. – “Default Font”

    Formerly, the H2 Post Titles respected the font I had selected for “Headings Typography” (Windsong). Now it is using the font I had selected for “Title and H1” (Spectral SC). I did notice some new CSS applied from your plugin

    
    .wp-block-post-title, .wp-block-post-title a, .entry-title, .entry-title a, .post-title, .post-title a, .page-title, .entry-content h1, #content h1, .type-post h1, .type-page h1 {
        font-family: "Spectral SC";
        font-weight: 300;
    }
    

    which appears to be treating post-title a elements as h1 elements now.

    Is this expected behavior?

    P.S. Unfortunately I can’t give you access to my staging instance to see the issue, but I can link you to the production site so you can at least see my page layout. The lists of posts is on the home page: https://www.kosmeomag.com

    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Danny Cooper

    (@dannycooper)

    Hi @egcarpenter,

    Thanks for raising this issue. On the surface level it does look like this is the expected behaviour, as the list on your homepage uses post-title classes. However, I will look into this and see if there is a solution for you.

    Thread Starter egcarpenter

    (@egcarpenter)

    Awesome. Thank you so much, @dannycooper ! I have a workaround, so it’s not a huge deal if I have to change my page to work with the upgrade. I did want to at least check in case it represents broken behavior.
    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.