Closed (cannot reproduce)
Project:
@font-your-face
Version:
7.x-2.3
Component:
Code (general)
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Jun 2012 at 17:04 UTC
Updated:
13 Feb 2013 at 09:53 UTC
Jump to comment: Most recent file
Comments
Comment #1
fakingfantastic commentedPatch
Comment #2
fakingfantastic commentedThat inadvertently threw an error about css_fallback not being a valid property. Instead of checking if($obj->val), better to do if(isset($obj-val))
Patch is patch #1, with this isset() patch as well..
Comment #3
sreynen commentedThis sounds like a duplicate of #1613760: Calling css from fonts.googleapis.com broken in 2.3, which was resolved by re-importing the Google fonts. Please try that and re-open that issue if it doesn't work so we can have all related discusion in one place.
Comment #4
fakingfantastic commentedJust an update: enabling the new font had no effect for me, still needed to apply my patch. IMO, the Font objects should have a valid URL and should not be encoded.
Comment #5
Drave Robber commentedFor me, the URL is just fine:
<link type="text/css" rel="stylesheet" href="http://fonts.googleapis.com/css?family=Yanone+Kaffeesatz:regular,300,700&subset=latin,latin-ext" media="all" />Did you go to Configuration > @font-your-face settings and click
Update Google fonts?Comment #6
sreynen commentedfakingfantastic, did you re-import after updating?
It's not really a question of whether fonts should have valid URLs. They clearly should. The question is whether this problem has already been solved.
Comment #7
Drave Robber commentedThis hasn't been possible to reproduce for some time now.
Feel free to reopen if you can provide steps to reproduce with the latest release.