-
fourthirtysixParticipant
First of all, Enlightenment is an amazing theme. Fantastic and flexible in so many ways.
One bug I’ve found is that after adding an API key to the web fonts, the interface does not list all fonts. For example, If I list all latin fonts alphabetically, it only makes it through the fonts that start with “A” and it gets several of the “B” fonts too, but there’s no way to pick a font that starts with letters C-Z. If your font happens to be popular or trending, you might get lucky and find it by resorting, but as it stands there’s no way to see all fonts.
I tried to figure out how to add it mannually in MySQL, but the option in wp_options is scary.
Would love to see this fixed or a workaround.
Best!
fourthirtysixParticipantAnyone have suggestions here? I’d like to use a specific Google font, but the problems with the theme not listing them all forces the use of some awkward plugins!
Help!
artemlimeParticipantI have a similar problem. I have entered my API key, but the fonts are not loaded. In google developer console I see the errors (Total number of project-related errors that Google sent in the last 24 hours)
fourthirtysixParticipantI ended up adding the “Per Page Head” plugin by Erik von Asmuth. Then go to Settings, Add <head> to every page, then paste in the link code, something like:
<link href=’http://fonts.googleapis.com/css?family=FONTNAMEGOESHERE’ rel=’stylesheet’ type=’text/css’>
Thunder CircusParticipantI added – @import url(http://fonts.googleapis.com/css?family=Lobster+Two:400italic);
to the CSS in Theme Options – Design
then I added the font-family to to the CSS of whatever elements I wanted to have a custom font.- This reply was modified 9 years, 9 months ago by Thunder Circus.
Thunder CircusParticipant@artemlime the @import method not working on iOS devices.
Pasted the link code into the header and it worked.
<link href=’http://fonts.googleapis.com/css?family=Lobster+Two:400italic’ rel=’stylesheet’ type=’text/css’>Daniel TaraKeymasterThank you for letting me know of this bug, it will be fixed in the next release.
You must be logged in to reply to this topic.