Uploader mod |
| Written on 10/14/05 at 07:19:43 EST by amadeaus |
| Hi there, new to webapp, but not new to Perl... I've a question regarding the uploader mod found here on this site. I've tweaked it to work with WebAPP v0.9.9.2.2 (had to change file lock stuff) and have got it to where it brings up the window to submit the file for upload. Upon hitting submit, the file seems to be transmitted to the server, but then doesn't get put into the upload directory I specified. The directory is set to 777 and it gets touched as the date stamp changes on the directory, but no file shows up. I've ensured that the file I'm uploading is in the list, is small (will want larger files later), but still no joy. Any help would be greatly appreciated. BTW. I'm running apache 2.0.40 and perl 5.8 but I've also tried this on newer versions of both apache and perl. Current OS is RH8, but the other OS tried on was Ubuntu 5.8 |
Other messages in this Thread: |
Re: Uploader mod |
| Written on 10/14/05 at 08:53:22 EST by Jack Deth |
| Which Uploader script? there are 2 of them here... I dont think you had to change any of the lock/unlock calls in any of them as they should be updated already... let me know and I can install it and check it out myself. |
Re: Uploader mod |
| Written on 10/14/05 at 09:09:56 EST by amadeaus |
| Under: Home > Downloads > Web-App Mods, the uploader mod. |
Re: Uploader mod |
| Written on 10/14/05 at 09:54:10 EST by Jack Deth |
| Thats odd... Now that I think about it, the mod is an older mod... but a goody... it needs a few fixups and additions... I probably forgot to finish playing with this one and tossed the mod up there for someone who asked me for it specifically... I will post an updated one in the future... my bad ;) Update: I have read your initial post again.. only thing I can think of is to check the directoy you set it to upload to in more then one place... I think I had a similar issue when testing it here, but got it working fine pretty quickly... as soon as I can, I will post up the working version if I can redo the changes I did to get it going... I think it has been overwritten on my end here... |
Re: Uploader mod |
| Written on 10/14/05 at 10:09:01 EST by amadeaus |
| you mentioned there there were two here... what's the other one? I've also been seeing on the various webapp, modapp forums a fileman mod, is this the same thing or similar. I've not been able to find that one anywhere for downloading. I'll check the directory locations and see if that's the case. It just seemed odd that it would change the date on the directory but not put the file there. I've compared the cgi files to those that ship with the webapp core and there's really very little difference except to accomodate the separate directory from the image file uploads. |
| Written on 10/14/05 at 11:42:01 EST by amadeaus |
| Ok, found it (I think)... the routine in uploadfile.cgi where it writes the file... directly afterwards it checks against the $max_size var to see if you've exceeded the amount.... if you have, unlink (remove) the file. So, it would seem that even though I was putting in a small file (361kb), it would remove it directly thereafter which explains the date change on the directory. I changed line 15 of that file from : $max_size = $maxuploadsize; to: $max_size = ($maxuploadsize * 1024); for testing purposes... and it uploaded just fine. There's probably a better way to do this and when my brain is not so fuzzy, I'll figure it out. Question: is there a way to automagically move the file from the upload dir to the download dir on an approval basis? Again, when I'm not so fuzzy, I'll work on that. Thanks |
Re: Uploader mod |
| Written on 10/14/05 at 13:42:53 EST by Jack Deth |
| There is this "Image Upload Manager" script here: http://www.2xlnt.com/992/0992.cgi?action=downloadinfo&cat=shakaflex&id=4 as well as another uploader script by Jane which I cant seem to find right now, but that is the one that most people are using... might be the one you downloaded.. just dont remember ;) |
The comments are owned by the poster. We aren't responsible for its content. |