First up thanks for getting cufon into a module. I was readign about cufon in .net magazine at the weekend and thinking how cool it would be to use that in a drupal site - and then lo' and behold a module pops up!

So my problem

I've installed and enable the module and the cufon scripts
I've created sites/all/libraries/cufon-fonts/
I've uploaded the converted font in to the cufon-fonts folder
When i go into the module config it lets me pick my uploaded fonts
I can't find anything in the site permissions apart form administer

And now here's the possibly stupid question;

I put 'h1' in the Selector: field, click save, cleared the caches and nothing changes. Any ideas as to what i'm doing wrong?

Comments

davideads’s picture

Assigned: Unassigned » davideads
Category: support » bug

I'm tentatively changing this to a bug report: That sounds like a bug, because based on your description, you did everything correctly.

Some questions:

  • Are cufon-yui.js and your font definitions getting loaded in your document head and is cufon-drupal.js getting loaded at the end of the page?
  • Did you associate the selector with a font family? My apologies, that configuration form is a little whack from a UI/usability standpoint.
  • Did you specify a domain when generating the font? Are you sure it matches? When I was first testing this, I assumed I just needed the domain name (happily skimming the help text, to my own detriment), when I also needed to use a wildcard or specify the subdomains, which made me scratch my head for a few minutes.
  • What browser / OS? I assume other things using Cufon are working fine for you, but it's worth knowing.
danbuntu’s picture

* Are cufon-yui.js and your font definitions getting loaded in your document head and is cufon-drupal.js getting loaded at the end of the page?

In the source header I can see;

and tucked away down the bottom of the source I can see

* Did you associate the selector with a font family? My apologies, that configuration form is a little whack from a UI/usability standpoint.

In the selector I entered 'h1'
and then in the drop down box below it I selected the font
Assuming I've done that right then the UI isn't to whack as ididn't strugle to work it out

* Did you specify a domain when generating the font? Are you sure it matches? When I was first testing this, I assumed I just needed the domain name (happily skimming the help text, to my own detriment), when I also needed to use a wildcard or specify the subdomains, which made me scratch my head for a few minutes.

i didn't use any domain security on the font at all first time round. I have just generated a new font file using domain security and still no cigar.

* What browser / OS? I assume other things using Cufon are working fine for you, but it's worth knowing.

I'm using ubuntu with firefox 3.5 and also Win XP with friefox 3.5 and IE 8

when I first started looking at Cufon I was trying to use the instructions at;

http://aaronwinborn.com/blogs/aaron/cuf%C3%B3n-alternative-sifr-image-re...

Whilst i couldn't get these instuctions to work for me the font rendering on the page is working fine.

I hope that gives you something to go on

davideads’s picture

Status: Active » Closed (fixed)

Fixed in http://drupal.org/project/cvs/518250 ... with a test, no less.

davideads’s picture

Status: Closed (fixed) » Fixed
davideads’s picture

Status: Fixed » Closed (fixed)

I believe we've resolved all the problems here. Reopen if more issues arise.

hmmdinger’s picture

Status: Closed (fixed) » Active

Forgive me if reopening this issue was not the ideal way for me to introduce my question, but the original problem described by danbuntu is exactly what I am facing, even with the most recent release of the Cufón module (6.x-1.0-beta4).

All scripts and font definitions are showing as loaded in the source code, and I have used the admin interface to associate h1 tags with a font family. The page loads, but without the cufón change being applied to the h1 tag.

I am using Firefox 3.5.2 on OS X 10.6.I have seen cufón working fine on other example non-Drupal websites.

akalata’s picture

In trying to troubleshoot the font rendering issue I've been having, I ran into an interesting bug.

Using the Drupal module, some would fonts render but others did not.

Both fonts would render fine when added to the theme without using the module.

I tried changing the file name of the font which did not work to be more like the font which did -- all lowercase, "_###" at the end, no "_" which translates into a space in the drop-down selector, without any luck.

Eventually I hit upon something that did work -- using the font filename that is created by the Cufon generator (case didn't matter). For instance, trying to use "TimesNewRoman.font.js" instead of "Times_800.font.js" would fail when using the Drupal module, but not when placed directly into the theme.

Now I need to decide whether I'll continue to use the module, or switch to adding cufon on a per-theme basis since I can have more semantic (and designer-friendly) font names. But, hopefully my discovery will help somebody else with this issue!

troky’s picture

Status: Active » Closed (won't fix)

Closing this since there is no 6.x maintainer.