Easily add Google fonts to your WordPress website. With multiple options, this is perfect for regular and advanced WordPress users alike.
You will need a Google API key to make use of this plugin. Your key is free and easy to get. However, many people get confused on this. It's really quite simple:
1) logged in to your Gmail account; 2) go here https://cloud.google.com/console; 3) create a project (example: "my google fonts"); 5) under "APIs & auth" click APIs and add "Web Fonts Developer API"; 4) under "APIs & auth" click credentials (create new key); 5) copy the API key under "Key for browser applications", that's it.
Once you have selected fonts and added them to your site, you must either add them to your style sheet manually, or apply them within your blog post or pages by using the visual editor or overriding your themes style sheet by configuring options under the "Default Styles" tab (make sure you have enabled the "Style Defaults" and apply them to your site elements).
If you have done all of the above and you still can't see any changes, you should turn on the "!important" CSS constructor, rebuild your style sheet and refresh your page. Also, make sure to delete your cache and refresh your page - particularly if you are using a cache plugin. Please note, that not all of your website's styles can be manipulated with the "Default Style" options. In some cases, you will have to use "inline styles" or CSS to achieve your desired result. We are only able to provide a basic framework for you with this plugin.
Yes. By default, we assume that you don't know how to code or do not want to. So, font selection in the visual editor, along with web safe fonts option are enabled by default. This plugin allows you to turn off all of these added utilities for applying fonts. You may do so under the settings tab.
Yes. As of version 1.0.1 of the plugin, you are able to activate the plugin for all the sites in your network. If you do this, you must enter your API key within the Network Admin (under settings) for the plugin to work.
Make sure that your API key is entered into the space provided without any leading or trailing spaces. Next, you must click the button "Update Configuration" (or "Activate Google API Key Globally" in Network Activation). Unlike many of the other options, which are set via ajax and do not require a page refresh or submit button, setting the API key requires a full form submission to complete. If you follow these instructions and still have issues, check and make sure that you are using the correct API key ("Key for browser applications" aka "Browser Key").
Apparently, with some server configurations the curl module in PHP may be required to validate the API calls. For more information on this you can read the posts in this support thread: http://wordpress.org/support/topic/api-wont-load-1?replies=8
Thanks to @foundationstestprep who pinted out an error that occurs when a referrer is specified: "I couldn't get the Google Font Manager plugin to accept my Google API until I went back to Google and removed the referrers from the API key. Although I'm certain I had the referring url correct, it wouldn't work until it was removed. If you're having problems with the API key and have a referrer associated with it, try removing it to see if it helps."
I have no idea! This has been an ongoing issue for at least one user. I suspect it has to do with the caching system HostGator forces you to use in their shared hosting environment which is adding a space to the header file. I have wrestled with that before on HostGator, to no avail. If you have any ideas or can figure it out, I would be very interested in a solution to this!
Yes. We make a living by doing this sort of thing. You can learn more about us and what we can do for you by visiting our home page at: http://butlerconsulting.com.
For further information and step-by-step instructions you can go here: http://plugins.butlerconsulting.com/docs/google-font-manager/.
Requires: 3.1 or higher
Compatible up to: 4.2
Last Updated: 2015-4-23
Active Installs: 6,000+
0 of 2 support threads in the last two months have been resolved.
Got something to say? Need help?