I have added the CAPTCHA and Image CAPTCHA modules to a Drupal 7 site that is using Imagemagick as the Image Toolkit due to the Imagemagick (http://drupal.org/project/imagemagick) module's hooks into the D7 core.

However, the Image CAPTCHA module seems unaware that Drupal is now using Imagemagick as it complains about:

No TrueType support
The Image CAPTCHA module can not use TrueType fonts because your PHP setup does not support it. You can only use a PHP built-in bitmap font of fixed size.

I remember my current server being able to use custom fonts with Image_API_Imagemagick on my D6 site, so it would seem like the custom fonts are being denied to me for no reason. This may have a lot to do with how Image Toolkits are implemented in D7, I'm not sure, but I couldn't find an answer to my question via search, so I went ahead and submitted this ticket.

Comments

soxofaan’s picture

tagged as "D7 stable release blocker" per #1269702: Blockers to a 7.x-1.0 release?

tim.plunkett’s picture

So, this is the only remaining blocker? What needs to be done?

soxofaan’s picture

Version: 7.x-1.0-alpha2 » 7.x-1.x-dev
Category: bug » feature
Issue tags: -D7 stable release blocker

What needs to be done?

I haven't looked into this issue in detail, but I guess it involves quite a bit of refactoring as the Image CAPTCHA uses GD functions directly instead of the drupal image API.

So, this is the only remaining blocker?

Hmm reconsidering here. This is not a critical thing, given the low interest in this issue.

tim.plunkett’s picture

So in that case, there can be a stable release now! :D

soxofaan’s picture

So in that case, there can be a stable release now

True, but the problem is that I'm the only maintainer of the CAPTCHA module, and I have virtually no time nowadays to do it properly. So I'm not so keen on switching to stable modus, when I can't guarantee any level of "maintainership".
I've been searching for co-maintainers for almost 2 years now, without much success unfortunately.

tim.plunkett’s picture

There are 43356 sites are already using the 7.x-1.x branch.

And if it were stable, you might have more success looking for a comaintainer.

But either way, if a module is stable you should tag a release. The project page already indicates "Seeking co-maintainer(s)" and "Maintenance fixes only".

wundo’s picture

Issue summary: View changes
Status: Active » Closed (outdated)