Invoking .ttf file from wrong path / page not found errors

At first glance, this sounds like a bug. I'll look into it.

I haven't been able to reproduce this problem. The folder name comes directly from the font family name you entered, so myriadpro_regular is the correct name. Do you maybe have an earlier import still enabled with a different name? That's the only reason I can think of it would be looking for something in another directory. You can see what's enabled at admin/build/themes/fontyourface.

I haven't been able to reproduce this yet. It may be related to #1118806: Cron disables local font. Can you try re-uploading the font with the dev version and see if this still happens?

Are you still having this problem?

I'm closing this, as I haven't been able to reproduce it. If anyone is still having this problem, please re-open.

Actually I am experiencing the same event - Page not found in Watchdog logs, but all fonts display correctly, no problems with file/folder permissions. Just large amount of such notifications. What I did noticed, is that something is calling font with a wrong path (almost). Font path is correct, but it is appended with " sign or %22 symbol only once at the end of whole string, e.g. ....ttf%22. And it is correct, that such path does not exist, as the actual path is ... ttf (ends only with .ttf or other file extension). This happens only with one .ttf font using Local fonts sub-module.

As I mentioned, fonts are displayed more or less correct. I was going through module files, to find some string forming this path, but as I am not a programmer, actually didn't manage to find anything useful, what I understand. What may be the cause for such strange path request with only one " symbol at the end? Actual folders and folder paths are correct. Using module's v2.8.

I think this is probably a bug in whatever is requesting that URL. The CSS has quotes around the URL for the font files, following the CSS spec. I'm guessing something (a browser, web spider, etc.) is wrongly including the closing quote as part of the URL. Since we can't fix that in the module, I'm closing this. If I have any of this wrong, please re-open.

I'm not sure if my error is related, but it seemed close. I'm using 7.2x dev and getting 404 errors in my report log trying to access:

http://xxxxxx/http://fonts.googleapis.com/css?family=Gudea:400,bold,ital...

Obviously the error here is that it's prepending my domain url to the start. Any ideas?

edit: forgot to mention the fonts work fine, just getting spammed in my logs

jarchowk, I think that's a separate issue. If you want to create a new issue for it, please include some detail on how we might reproduce the problem.

FYI, I have this issue too. It does not seem to cause a problem with my site. I just see a lot of errors in the log.

The log shows this as the location for the page not found:

http://www.mywebsite.com/sites/default/files/fontyourface/local_fonts/Francois_One-normal-normal/FrancoisOne.ttf)%20format(%22truetype%22

This is the css:

@font-face {
  font-family: 'Francois One';
  src: url("FrancoisOne.ttf") format("truetype");
  font-style: normal;
  font-weight: normal;
}

It does not seem like a big deal. I just thought I would let you know.

Ken

kenmiller35, what browser are you seeing that in? And did you only upload a .ttf file?

The upload form takes multiple file formats because different browsers support different formats. My guess is you didn't upload the right format for your browser (I'm guessing IE) and it doesn't understand the CSS syntax for TTF files. The solution to that is to upload all formats. Or, better yet, use the font from a dedicated font server that already has all formats and can serve them faster than your server. FrancoisOne is available on Google:

http://www.google.com/webfonts/specimen/Francois+One

You should really only be using the local fonts module if you can't find the font anywhere else.

I am having same issue,
It seems that the Drupal loader cannot process stylesheet.css for fonts in a correct way
Using Drupal 7 and @font-your-face 7.x-2.7

camilohollanda, Drupal doesn't process stylesheet.css for fonts at all. That happens entirely in the browser. That's why I asked which browser this was in #15. Since no one has been able to provide both the CSS and the browser, I haven't been able to reproduce this, so I'm marking as "closed (cannot reproduce)." If anyone can provide the requested detail, please change the status back to "active."

User agent:
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)

stylesheet.css

@font-face {
font-family: 'AspectRegular';
src: url("aspect-webfont.eot");
src: url("aspect-webfont.eot") format("embedded-opentype"), url("aspect-webfont.ttf") format("truetype"), url("aspect-webfont.woff") format("woff"), url("aspect-webfont.svg#AspectRegular") format("svg");
font-style: normal;
font-weight: normal;
}

Apr 3 10:49:27 drupal: http://www.xxxx.org|1364996967|page not found|200.144.28.24|http://www.xxxx.org/sites/default/files/fontyourface/local_fonts/AspectR...)%20format(%22embedded-opentype%22),%20url(/sites/default/files/fontyourface/local_fonts/AspectRegular-normal-normal/aspect-webfont.ttf)%20format(%22truetype%22),%20url(/sites/default/files/fontyourface/local_fonts/AspectRegular-normal-normal/aspect-webfont.woff)%20format(%22woff%22),%20url(/sites/default/files/fontyourface/local_fonts/AspectRegular-normal-normal/aspect-webfont.svg|http://www.xxxx.org/pt-br/satsang/110213|0||sites/default/files/fontyourface/local_fonts/AspectRegular-normal-normal/aspect-webfont.eot) format("embedded-opentype"), url(/sites/default/files/fontyourface/local_fonts/AspectRegular-normal-normal/aspect-webfont.ttf) format("truetype"), url(/sites/default/files/fontyourface/local_fonts/AspectRegular-normal-normal/aspect-webfont.woff) format("woff"), url(/sites/default/files/fontyourface/local_fonts/AspectRegular-normal-normal/aspect-webfont.svg

camilohollanda, your CSS syntax doesn't match the code in 7.x-2.7. Specifically, you can see in the source there's a ?#iefix in the second .eot statement, which is missing from the CSS you posted. Do you maybe have something re-writing CSS on your site? That's the only explanation I can think of. The missing ?#iefix is, as the name implies, what should fix the IE bug that triggers those 404 requests.

I made a change, removed the iefix trying to fix the problem, but without success,
I reverted, the result is the same.

@font-face {
font-family: 'AspectRegular';
src: url("aspect-webfont.eot");
src: url("aspect-webfont.eot?#iefix") format("embedded-opentype"), url("aspect-webfont.ttf") format("truetype"), url("aspect-webfont.woff") format("woff"), url("aspect-webfont.svg#AspectRegular") format("svg");
font-style: normal;
font-weight: normal;
}