Remove hardcoded Google Fonts references in views

  • It’s impossible to circumvent the references to webfonts.js (calling ajax.googleapis.com) in the blank.php and html.php files in the /framework/public/views folder without modifying core plugin files. Since this breaks GDPR compliance, I would love for you to remove this reference OR at least use the wp-enqueue functions, so we can hook into the calls and make them local OR at least provide us with an completely blank theme from the getgo – one that does literally nothing at all – unlike the current blank-theme, which still calls the webfonts.js.

    In Austria alone 1.000s of website owners received a cease & desist letter last week, including a damages bill from a overzealous lawyer for this very reason. Using your plugin makes it virtually impossible to run a website within the EU that’s GDPR compliant, without modifying its core-files.

    Thanks, Mario

    • This topic was modified 2 years, 3 months ago by Mario Rader.
Viewing 1 replies (of 1 total)
  • Plugin Author WebFactory

    (@webfactory)

    Hi,
    We’re aware of the issue and have plans to fix it. This particular one for the blank template is much easier to fix than Google fonts in general, so it’ll definitely be fixed in the next release.

Viewing 1 replies (of 1 total)
  • The topic ‘Remove hardcoded Google Fonts references in views’ is closed to new replies.