Support » Theme: Ignite » EU GDPR: Internal fonts instead of Google Fonts?

  • Resolved ArnoAnou


    Dear Ben,

    since for all websites inside the EU the General Data Protection Regulation is coming (deadline May 25), there’s gonna be a problem with integrating third party files, including Google fonts. (Font Awesome seems to be saved locally (?), so that’s um awesome.)

    The easiest solution would probably be to download the specific Google font used and upload it to the website’s server. However there is no feature inside the customizer to add own fonts, so it comes down to very tedious css-coding?

    We would appreciate your help!
    (And the same for Startup Pro.)



    • This topic was modified 2 years, 5 months ago by ArnoAnou.

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

Viewing 1 replies (of 1 total)
  • Theme Author Ben Sibley


    Hey Arno,

    You can add the following function to your child theme to disable all instances of Google Fonts from being loaded by Startup Blog and Startup Blog Pro.

    function ct_startup_blog_child_remove_google_fonts() {
    	wp_deregister_style( 'ct-startup-blog-google-fonts' );
    	wp_deregister_style( 'ct-startup-blog-pro-primary-google-fonts' );
    	wp_deregister_style( 'ct-startup-blog-pro-secondary-google-fonts' );
    	wp_deregister_style( 'ct-startup-blog-pro-site-title-google-fonts' );
    add_action( 'wp_enqueue_scripts', 'ct_startup_blog_child_remove_google_fonts', 999);

    Then you can download the fonts you’re using, and I would recommend the Use Any Font plugin to load them from your site.

Viewing 1 replies (of 1 total)
  • The topic ‘EU GDPR: Internal fonts instead of Google Fonts?’ is closed to new replies.