Configuration error - GD Library

I’ve noticed the following error in the Manager backend on a modX 1.0.3 installation- any ideas?

Configuration warning: ’GD and/or Zip PHP extensions not found’



What does this mean?

MODx needs the GD and Zip extension enabled for PHP. While MODx will work without them, you will not be able to take full advantage of the built-in File Manager, Image Editor or Captcha for logins. 

I suspect that it’s a case of the web host not having enabled the library on the server / in the config files, however I wanted to check- is there anything that can be done before we try and get the hosts to reconfigure? (particularly as they might refuse)

At the moment images aren’t displaying in FCKEditor (nor in TinyMCE).

You can check what’s available in your PHP at Reports -> System Info, then the phpinfo() view link. In the first block, the Configure Command field, look for something like ’--with-gd’, then further down in the alphabetical list of configurations look for GD and Zip.

If your hosting won’t add these, then you’re not going to be able to have thumbnails and other image manipulation that depends on the GD library. Zip isn’t important unless you want to upload zip archives and unzip them from the Manager’s file manager (Elements -> File Manager).

If you do have GD, there are a number of other reasons why the thumbnails aren’t showing in the resource browser.

From the config it looks as if GD is enabled, which begs the question why is modX complaining about it not being... I noticed that zip isn’t enabled but if as you say that isn’t required anyway, I should be able to view images within the backend.

So probably no point going to the host as they’ll say it’s already enabled, so I need a way of getting images viewable for the editors... any other ideas?

Check your path in Configuration, the Interface and Features tab, and also the File Manager tab. The url can probably just be assets/, but it may need /assets/ (or /installdir/assets/ if it’s not in the web root).

Make sure that the filesystem folders/files involved are readable/writable.

I have the permissions on /www/images set to 774 (all the images for the site are in here rather than the assets area). It was also previously set to 777 amnd the images were not viewable then either (by any account).

The user accounts can upload to the folder but the images are still not showing.

Other settings in the configuration are:

File manager path: /home/sitename/public_html/
File base path in Interface & Features: /home/sitename/public_html/assets/
File browser path: assets/

No errors seem to be happening in the File Manager...

Check your error logs. Sometimes a security setting limits the recursive directory depth a script can drill down for including or calling other scripts; the resource manager needs at least six levels, and I’ve had failures where this setting was set to 4 or 5.

Unfortunately there’s nothing in the error logs related to this problem.

I’ve also tried changing the URL for the file manager / interface settings to be the root (i.e path/to/public_html/ ) but to no avail...

Just to confirm, the site pages are in path/to/public_html/ (not assets) and images are in path/to/public_html/images. So on that basis should the paths be different in the config?

I’ve also che4cked the folder permissions for the root and /images folders and these are set to 755.

The resource manager is configured to look for images in assets/images, and files in assets/files. If you are storing your images somewhere else, the resource manager can’t access them.