Files Deleting On Small Thumbnail Rebuild
 

Here is what this script does when the path to ImageMagick doesn't work. It starts DELETING files!

I moved servers and ran all the other database scans individually and they all seemed to work but as soon as I tried to rebuild All thumbs it decides to start deleting files.

Processing may take a while... please be patient and wait the for FINISHED message...

Checking photo #4: image /home/extremea/public_html/gallery/data/500/28-Orion-Final.jpg not found, removing from database... done.
Checking photo #5: rebuilding /home/extremea/public_html/gallery/data/500/thumbs/28-Orion-Final-Annotated.jpg from /home/extremea/public_html/gallery/data/500/28-Orion-Final-Annotated.jpg ...

Error creating thumbnail! Error code: 126

Command:

"/usr/bin/convert/mogrify" +profile "*" -size 100x67 -quality 100 -geometry 100x67 -unsharp 10 '/home/extremea/public_html/gallery/data/500/thumbs/28-Orion-Final-Annotated.jpg'

Yes that is a possibility it will delete that one file and stop with the DIEWELL command that is displaying the message.

If you move servers part of the move process involves making sure the proper image processors are selected etc.

http://www.photopost.com/forum/photo...rectories.html

Its always very important to check everything after a server move.

If for some reason ImageMagick isn't setup right or you enter the wrong path and try the Rebuild All Thumbs it will delete a file every time you try that selection. I would imagine it would do it until there's nothing left.

This should not be happening and it needs fixing regardless of a server move given the way it occurs. I mean just because a path statement is wrong or ImageMagick isn't installed correctly makes it acceptable that the script starts deleting files from the server and database.

One of the requirements to run the program is a functioning image processor. The whole code is dependent on this so its really not a bug. One of the things that move document states is check uploads. Therefore if the program was moved correctly and everything updates this issue would not be happening.

You could maybe try line 408 changing it to this

would instead be

But really if the program was properly installed this issue would not be here.

I agree the issue wouldn't be here if it was setup perfectly the first time. Switching over to GD works just fine. It just doesn't seem reasonable that because of a simple path statement not being right, things start getting hacked out of the database and deleted off the server. I would have expected a better response from any script.

I'll try your code out.

Thanks

okay well the change simply prevents it being deleted if the path is wrong to mogrify

&& is_file( $Globals['mogrify_command'] )

Therefore what this says if your only going to get a file deleted if the checkfile can not be created and mogrify does exist. So if it doesnt exist that if clause does not run.