I first got this error ("Error while moving uploaded file to its destination.") when I installed version 1.4 but when I went back to 1.3 it was still there.
I have no clue what it means. I checked permissions on both files and temp folder, it's building the directory tree all by itself, old files are showing up fine, etc.
I googled the phrase and the only thing that comes up is the code for image picker, but I can't figure out from there what it actually *means* when you get this error. Help, please? Our site just went live, and I'm not able to train people how to post news with images because I can only do it manually now.

Comments

hmb_site’s picture

hmb_site commented

Another thing I noticed: it is building .TMP files in the folder where the images should go whenever I try to upload something, but just not actually putting the images there. Don't know what that means

hutch’s picture

hutch commented

the web server creates uploaded files in wherever has been set up as the temp folder, on *nix usually /tmp
This can be over-ridden in php.ini, or you can enter it in admin/settings/file-system.
If /tmp will not work then create a tmp folder inside files (using ftp or shell), set permissions to 777 on files/tmp, enter it in admin/settings/file-system and try again.
Some ISP's have restricted /tmp because of hackers, if so just roll your own.
Once /tmp or wherever is set up php will copy the file to wherever it has been instructed to by imagepicker. If it doesn't then it couldn't because of file permissions on the folder.

By the way, 1.4 and 1.3 are identical except for a couple of bugs, neither of them anything to do with uploading. In fact the code for uploading, resizing and copying has remained unchanged since the start of the imagepicker project. If it ain't broke don't fix it.

Hope this helps

hmb_site’s picture

hmb_site commented

Thanks! I made a new folder, that didn't work (and it worked before with the tmp folder that was already there, so that couldn't have been the problem...) but I then figured out that it probably got stuck AFTER that. It turned out that after a recent upgrade the final files folder was no longer writable by the tmp folder... I checked that last week, and didn't catch it (it's windows, so I'm basically just looking at a bunch of boxes that are checked or not, instead of having the 777 etc. number codes)

hutch’s picture

hutch commented
Status: Active » Closed (fixed)