phMagick :: Testing the instalation
phMagick requires 2 things ImageMagick and the ability to issues systems calls with the exec() function
The easiest way to test the installation is to issue a system call to the convert binary
You can also activate phMagick Debug Mode and see if after running a command you get any errors.
One common error on windows systems is "invalid parameter", it usually means that windows is using the convert.exe from system32 (convert is used to convert a file system to NTFS) instead of the ImageMagick convert
Hi -
Your library works great on my local MAMP install; however, I would also like to use it on our server (which has imageMagick installed).
I have permissions to run shell “exec” commands, but one (small) problem I am having is that if I would like to call the script from a browser, the default web-user doesn’t know the full path to the ‘convert’ program that your phmagick class wrapper is calling. I noticed that ‘convert’ is called in several of your plugin files, and rather than changing the path in all of them, I would like to set a path variable in one place (or once in each file that uses convert) and then append this to the convert calls — e.g., $cmd = $p->getBinary(‘convert’); ==> $cmd = $p->getBinary($path.’convert’);
Where is the best file to add the path to, so it will cascade through the dependent files, and so it will minimize editing through all your plugin files?
Alternatively, I suppose I could set a $PATH variable for the web-user so that it finds the ‘convert’ program without modifying anything. I just thought the path might be a nice option to have.
Thank you again for the phmagick class and scripts!
@ Elizabeth
please see this link http://www.francodacosta.com/blog/phmagick/examples/error-convert-invalid-parameter it has information how how to change the path of imagemagick binaries
IF you need more help, just ask