So after thinking my webhost was insane because the rosterdiag indicated that freetype support was OFF even though they said they have freetype enabled on my server, I continued to back and forth with them via email to try and solve the problem. I was convinced that they really didn't enable it.

They came back and told me that when they upgraded my server they installed the LATEST version of Freetype, (version 2.2.1) and that is the reason that siggen isn’t' working for me anymore.

At first I thought maybe it was my fault for not upgrading from roster 1.6 to 1.7 so I did that next but got the same GD error... just more verbosely.

http://freetype.sourceforge.net/freetyp ... 2.2.0.html

That webpage gives some indication of what problems may occur because of the new version.

Is there something I can edit in siggen that will make it compatible with the newest version of freetype? My server said that if it comes down to it they will downgrade me to make the siggen work again but I'd rather see if you guys could come up with some sort of compatibility fix before I go back to a version of freetype that has security issues.

I really love siggen and my users miss it very much. I don’t want to retire it because of a server upgrade. =(

/EDIT oh! and the version of freetype I was running on before was 2.0.28. It worked on that version.

I honestly have no clue...
Is this the glyphs error?

I don't know what the glyphs error is but my problem is that siggen doesn't think freetype is installed so it's not working. My webhost tells me fretype 2.2.1 is installed on my server.

So either they are lying and it's really NOT installed or siggen isn't working with freetype 2.2.1

/EDIT So I've checked three different scripts and all three seem to indicate that Freetype isn't installed on my server. My hosts insist it is but my info.php Configure Command reads like this:

'./configure' '--enable-pic' '--with-libdir=lib64' '--prefix=/usr' '--with-xml' '--enable-bcmath' '--enable-calendar' '--with-curl' '--enable-ftp' '--with-gd' '--with-jpeg-dir=/usr/local' '--with-png-dir=/usr' '--with-xpm-dir=/usr/X11R6' '--with-gettext' '--with-iconv' '--enable-mbstring' '--enable-mbstr-enc-trans' '--enable-mbregex' '--with-mcrypt' '--with-mhash' '--enable-magic-quotes' '--with-mysqli' '--with-mysql=/usr' '--enable-discard-path' '--with-pear' '--enable-sockets' '--enable-track-vars' '--with-xmlrpc' '--with-zlib'

GD-TEST.php reads like this:

GD is supported by your server!

GD Version Yes
FreeType Support No
T1Lib Support No
GIF Read Support Yes
GIF Create Support YesJ
PG Support Yes
PNG Support Yes
WBMP Support Yes
XBM Support Yes
JIS-mapped Japanese Font Support No

The rosterdiag reads like this:

GD Support

GD Status On
GD Version bundled (2.0.28 compatible)
FreeType Support No
T1Lib Support No
GIF Read Support Yes
GIF Create Support Yes
JPG Support Yes
PNG Support Yes
WBMP Support Yes
XBM Support Yes
JIS-mapped Japanese Font Support No


Three DIFFERENT SCRIPTS and NO WHERE in there is anything about freetype. I've written my fifth email to my host trying to figure out what the problem is.

I have to belive it's them and not all these scripts.

Yeah, seems fishy to me
Rosterdiag uses a basic php script to figure out if GD has access to freetype, straight from the php site

Finally... someone fixed the problem. I'm SO happy! It was my host and now everything is peachykeen.

So what was the problem. I just recently got the wow roster running and now playing with all these adoons but I'm having the very same problem with SigGen. Any suggestions?

The problem was that my host DID NOT have freetype enabled on my server though they claimed they did. It was resolved when they finally enabled it.