I installed cbb 3.0 finally.

Now when i go at the index of the forum in the adminCP, it says that:

ImageMagicK: Not available
NetPBM: Not available
GD1 library: Not available
GD2 library: Not available

In my php.ini file i removed the ; which is in front of the php_gd2.dll.

What are the differences between imagemagick, netpbm and gd2?

How can i install gd2 or the others?

Note that i have a homeserver.

A little help guys...

I have the same problem.

I installed myalbum-p and it detects ImageMagick and netPBM just fine when you put in the right path.

The problem seems to be CBB 3.05 (and judging by the earlier messages I searched through), which can't detect it through the environmental variable in FreeBSD or Windows, and has no way to set the path correctly.

Not sure how this will affect functionality, if it does at all, but it'd be nice if we could set the path.

u will need the GD2 library to be installed.. it's usually done on most php installations as standard.. but you will have to check that the correct library is actually on your computer.

google will probably be a better place to search for help with that..

click here for a few pages.. i can't tell you which to choose as i don't know what system you have or what versions of php etc. but i'm sure you'll find the answer somewhere there.

or try http://www.php.net

Thanks m0nty, I really appreciate the quick response :)

I'll follow up on the links you left me. I know that the gd library is already there, but maybe it will need to be updated.

Another odd thing is that I also have myAlbum-P instead, and it finds both ImageMagick and netPBM with no problems. So I copied the path statement from that, and plugged it into the CBB preferences (where there is an option for a path setting). This didn't work either. Even using the exact same auto-detected paths that myAlbum-P uses, CBB still doesn't see it.

An idea; perhaps XOOPS itself could have the ability to manually set the path for ImageMagick, netPBM, and the gd libraries, and then offer it as a variable to future modules, so that something system-wide like this doesn't have to depend on the individual module developers to each implement in different ways. Just an idea.

Thanks again, I'll continue searching for the answer with your suggestion.

-LionHeart