Image::Magick playing hide and seek

[Sara]

This is beyond frustrating for me right now.

According to perldiver on copper Image::Magick is installed, but according to http://www.serialpurrs.org/mt/mt-check.cgi Image::Magick is not installed (At least not in the usual place where it should be found. Or the install of Image::Magick is faulty).

I've been running back and forth between Jag Support and the MovableType support people and each of them seems to think I should check in with the other part to get things sorted out.

Does any of the MT people around here have any clue about what to do or have any of you experienced the same problem with MT 3.x not finding Image::Magick?

[Connie]

Sara,

Why not ask support through the ticket system?

[Sara]

Have to admit that I kinda gave up on it since all I got was a link to perldiver and the note that it was installed.

[Connie]

Jag is pretty good about uploading, updating, on installing new whatever a customer needs. I f it is something important to you I still think a request to through the ticket system would be the best way to go. I would submit that kind of request during normal business hours. Support seems to be a little better. You would have an official rresponce to your question.

[Sara]

I know they're good about doing stuff for us (Had some modules installed earlier this week in half an hour). Just frustrating when things isn't that easy to solve.

[JPC-Les]

Apparently MT or that script has a problem when running in a subdirectory. check out http://www.serialpurrs.org/mt-check.cgi

[Sara]

Arghh Wonder if I should go ahead and reinstall MT to the cgi bin?

*scratching head*

[Vin DSL]

I don't know if this will help you, but here is the location of PerlMagick on Neutron:

whereis Image::Magick
Image::Magick: /usr/man/man3/Image::Magick.3 /usr/share/man/man3/Image::Magick.3pm

[Sara]

Ugh

Tried installing MT in the cgi-bin, but asides mt running slower than $#()@#*$ it still couldn't find the darn module. And ofcourse Copper now appears to be down so I can't do anything at all.

Wouldn't surprise me if it was me bringing it down.

[jason]

You shouldn't install any programs in your cgi-bin for security rasons. If you need to install your own programs, you should install them somewhere outside of your public_html directory. Personally, I use a directory called "bin" inside my home directory. When you set up your scripts to refer to those programs, use /home/USERNAME/bin.

--Jason

[jason]

Nevermind, I misread the post I was replying to.

--Jason

[Sara]

And to end this saga (For now anyway) When copper came back up I pulled MT out of the cgi-bin and installed it as I've always done. It still can't find Image::Magick, but for now I can live without it and do it the hard way when needed.

[Spathiphyllum]

OK, so accordint to MT diagnostics:

Image::Magick
Your server does not have Image::Magick installed, or Image::Magick requires another module that is not installed. Image::Magick is optional; It is needed if you would like to be able to create thumbnails of uploaded images. Please consult the installation instructions for help in installing Image::Magick.

My guess is that since perldiver is detecting the perl module to allow access to Image::Magick libraries, that the module does exist and it is the libraries that are lacking. If you don't trust perldiver, then just install the Perl::Magick module from CPAN's repository into your own webspace and define the library path at the top of the MT script (is it a perl based script?). At least then you'll know that the module is available. If MT still fails (assuming you compiled the module correctly), then you are verifying that it is an Image::Magick library that is not available for a fully functional application.

If that is the case, you could submit a ticket to support requesting them to confirm that Image::Magick (ImageMagick libraries and not pm module) is indeed installed on your server and is operational. They may need to confirm that all symlinks are current since OS upgrades ocassionally interfere with shared server libraries. The Image::Magick libraries would most certainly be shared. You might also give them a link to the most current version of Image::Magick in case they want to reinstall with the latest and greatest. I don't think anyone would mind since if the current library isn't installed for you, it won't be installed for anyone on your server. Upgrading wouldn't sabotage anyone else's application.

Just top of the head thoughts to move the process along. Hope it helps. Then you can worry about DSA/crypt issues.

[Sara]

Running mt-check again and comparing it to the results when running it like Les did above I'm starting to get convinced that it's not MT that's got a problem but Copper

When running mt-check as Les did it sees Magick but not

Crypt::DSA

and

XML::Atom

Running it as I originally did in my first post it sees

XML::Atom

but not

Crypt::DSA

and Magick.

Now how to explain all this in a TT so I don't get just a "canned" response about Magick being on the server?