Google fonts self-hosted but still in cookie policy

  • Resolved stuartb3502

    (@stuartb3502)


    2 years, 1 month ago

    I’ve self-hosted my Google font since configuring Complianz. I self-hosted using css in a child theme. I then used Autooptimize to block the Google fonts script. I removed Google fonts from the list of services in Complianz and regenerated the cookie policy.

    Checking page source and in developer tools Network (search for fonts) shows me no trace now of Google fonts other than the self-hosted copy. I have purged the Autooptimize cache and purged/turned off Litespeed caching while testing.

    But Google fonts is still shown in the cookie policy. Grateful for any tips. Thanks.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor jarnovos

    (@jarnovos)

    Hi @stuartb3502,

    Most likely this is because Google Fonts had been detected at an earlier point in time, and it’s still displayed on the Cookie Policy as a result.

    I’ve done a quick check of the attached website, and indeed, it looks like the Google Fonts API is no longer being requested here.

    If you’re also positive that this is the case, you may navigate to Complianz > Wizard > Consent > Cookie Descriptions and find Google Fonts in the list. It will have a cookie “Google Fonts API” listed under it.

    Click “Google Fonts API” to expand its’ options, disable the “Show on Cookie Policy” checkbox, and hit the Save button.

    That will be sufficient to stop the Google Fonts service from appearing on the Cookie Policy.

    Kind regards, Jarno

    Thread Starter stuartb3502

    (@stuartb3502)

    Jarno, Sorry I didn’t spot that easy and obvious fix. Thank-you again for your help. All working great now.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Google fonts self-hosted but still in cookie policy’ is closed to new replies.