danielpataki

This plugin allows you to create a Google font selector field with different options. The plugin also creates the font request in the theme header to autoload the fonts if you’d like. Font variants and charsets can be selected separately to make font loading more flexible and optimized.
Font options added to any options page will always be enqueued. Any fonts added to post pages will only be enqueued when that specific post is displayed.
<h4>Google API Key</h4>
To grab the font list from Google you’ll need an API key. This is free and easy to do, take a look at <a href="https://developers.google.com/api-client-library/python/guide/aaa_apikeys" rel="nofollow ugc">this guide</a> to get an API key.
<h4>ACF Compatibility</h4>
This ACF field type is compatible with both ACF 4 and ACF 5.
<h4>Thanks</h4>
<ul>
<li><a href="http://www.advancedcustomfields.com/" rel="nofollow ugc">Advanced Custom Fields</a> for the awesome base plugin.</li>
<li><a href="https://www.iconfinder.com/Icojam" rel="nofollow ugc">Iconjam</a> for the T icon.</li>
</ul>
<h3>Usage</h3>
Once installed the list of Google Fonts will be retrieved from a static file included in the plugin. If you would like the list to be pulled from the Google API you will need to define your API key. You can do this in Settings->Google Font Selector in the admin.
<h4>For Developers</h4>
There are a few more advanced controls you can set to make the plugin do your bidding. If you would like to hard-code the API key and disable users from seeing the nag screen and setting panel you can define the <code>ACFGFS_API_KEY</code> constant.
<pre><code>define( 'ACFGFS_API_KEY', 'your_google_api_key' );
</code></pre>
The <code>ACFGFS_REFRESH</code> constant can controls how frequently the plugin checks the Google API for updates. The value is in seconds, 86400 would be a day. The default is set to 7 days.
<pre><code>define( 'ACFGFS_REFRESH', 259200 );
</code></pre>
If you would like to disable the automatic enqueueing of fonts you can use the <code>ACFGFS_NOENQUEUE</code> constant. The fonts are only enqueued automatically when this constant is not defined. Define the constant to disable enqueueing.
<pre><code>define( 'ACFGFS_NOENQUEUE', true );
</code></pre>
If you want to modify the fonts that are loaded on a page you can use the <code>acfgfs/enqueued_fonts</code> filter. This should return an array of fonts with variants and subsets needed, something like this:
<pre><code>array(
 'font' => 'Open Sans',
 'variants' => array( 'regular', '700' ),
 'subsets' => array( 'latin' )
)
</code></pre>
New in 3.0.1 is the ability to control the fonts displayed in the dropdown. If you only want to give your users access to a smaller portion of Google fonts you can use the <code>acfgfs/font_dropdown_array</code> filter to modify the array that is used to generate the dropdown. Please return an array where the key and the value are both the names of the font.
<pre><code>add_filter( 'acfgfs/font_dropdown_array', 'my_font_list' );
function my_font_list( $fonts ) {
 $fonts = array(
 'Raleway' => 'Raleway',
 'Lato' => 'Lato'
 );
 return $fonts;
}
</code></pre>

ACF: Google Font Selector

A field for Advanced Custom Fields which allows users to select Google fonts with advanced options

Daan van den Bergh

OMGF can be downloaded for free without any paid subscription from <a href="https://wordpress.org/plugins/host-webfonts-local/" rel="ugc">the official WordPress repository</a>.
<blockquote>
How could using fonts via Google’s service possibly run afoul of GDPR? The fact of the matter is that, when a font is requested by the user’s browser, their IP is logged by Google and used for analytics. 
 — Lifehacker
</blockquote>
Leverage Browser Cache, reduce DNS lookups/requests, reduce Cumulative Layout Shift and make your Google Fonts 100% GDPR compliant with OMGF!
OMGF is written with performance and user-friendliness in mind. It uses the Google Fonts API to automatically cache the fonts your theme and plugins use to minimize DNS requests and speed up your WordPress website.
<h4>How Does It Work?</h4>
After installing and configuring the plugin, OMGF will automatically start looking for Google Fonts whenever a page is requested on your website.
All Google Fonts are listed in the Optimize Local Fonts section of OMGF’s settings screen. There, you can choose to:
<ul>
<li>Preload fonts to reduce Cumulative Layout Shift above the fold,</li>
<li>Unload fonts that’re not used by you, your theme and/or plugins,</li>
<li>Set a Fallback Font Stack (OMGF Pro required), to further reduce Cumulative Layout Shift, or</li>
<li>Replace (OMGF Pro required) font-families with system fonts to speed up loading times!</li>
</ul>
<h4>Other Features include</h4>
<ul>
<li>The integrated Google Fonts checker notifies you if a plugin or your theme has added Google Fonts (e.g. after an update) it can’t process.</li>
<li>Variable Fonts support,</li>
<li>Automatically Remove unused subsets to reduce the size of the CSS stylesheet up to 90%!</li>
<li>Remove Resource Hints (preload, preconnect, dns-prefetch) pointing to <code>fonts.googleapis.com</code> or 
 fonts.gstatic.com,</li>
<li>Ensure text remains visible during webfont load by forcing the font-display attribute to your Google Fonts,</li>
<li>Ensure text remains visible during webfont load by forcing the font-display attribute to all your other fonts! ( 
OMGF Pro required),</li>
</ul>
<h4>Additional Features in OMGF Pro</h4>
<ul>
<li>Run the Google Fonts checker in the frontend (for all users) to organically check for present external Google Fonts throughout your site.</li>
<li>Smart Preload automatically configures which fonts should be preloaded i.e., loaded early to reduce Cumulative Layout Shift, Largest Contentful Paint and <a href="https://daan.dev/blog/how-to/ensure-text-remains-visible-during-webfont-load/" rel="nofollow ugc">Ensure Text Remains Visible During Webfont Load</a>.</li>
<li>Automatically configures itself to make sure all externally hosted Google Fonts on your site are hosted locally. OMGF Pro supports:
<ul>
<li><code>@font-face</code> and <code>@import</code> statements inside inline <code><style></code> blocks,</li>
<li><code>@font-face</code> and <code>@import</code> statements inside local stylesheets loaded by e.g. your theme and/or plugins,</li>
<li><code>@font-face</code> and <code>@import</code> statements inside externally hosted stylesheets loaded by your theme and/or 
plugins,</li>
<li>Web Font Loader (<code>webfont.js</code>),</li>
<li>Async Google Fonts (loaded using JS)</li>
<li>Material Icons.</li>
</ul>
</li>
<li>Multisite and WPML support.</li>
<li>Whitelabel stylesheets, which removes branding and comments from the stylesheets to further reduce the size.</li>
<li>Modify your fonts’ <code>src: url()</code> attribute to fully integrate with your configuration,
<ul>
<li>Use this to serve fonts and the stylesheets from your CDN, or</li>
<li>To serve fonts from an alternative path (e.g. when you’re using Security through Obscurity plugins like WP Hide, 
etc.), or</li>
<li>Anything you like!</li>
</ul>
</li>
<li>Developer Mode, which allows you to easily migrate between Development, Staging/Testing, Acceptance and Production 
environments.</li>
</ul>
<a href="https://daan.dev/wordpress/omgf-pro/" rel="nofollow ugc">Purchase OMGF Pro</a> | <a href="https://daan.dev/docs/omgf-pro/" rel="nofollow ugc">Documentation</a> | <a href="https://daan.dev/docs/omgf-pro/tested-themes-plugins/" rel="nofollow ugc">Tested Plugins & Themes</a>

OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.


Does the job flawlessly. Thanks for making this plugin!


Just works!

Good plugin

OMGF automagically caches the Google Fonts used by your theme/plugins locally. No configuration (or brains) required!

ACF: Google Font Selector vs OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.