Upgraded 1.54 to 2.02 ... Upload Broken

[rlkingston]

Hi

I Upgraded EE 1.54 to 2.02 yesterday. Everything looked grand until I attempted to upload a new image. The first step ... sending photographs to the upload folder ... works fine. But when I try and execute the subsequent resizing/uploading/database insertion steps it fails. EE CWD's to the correct directory. Then I get this

msg 12687 | internal ftp: TYPE I
msg 12688 | internal ftp: TYPE: 200 Type set to I.
msg 12689 | internal ftp: PASV
msg 12690 | internal ftp: PASV: 227 Entering Passive Mode (130,216,184,21,192,19)
msg 12691 | internal ftp: Parsed data connection address is 130.216.184.21:49171
msg 12692 | internal ftp: OPENING NEW DATA SOCKET 130.216.184.21:49171
msg 12693 | internal ftp: DATA SOCKET OPEN
msg 12694 | internal ftp: 4517281 bytes to cache
msg 12695 | internal ftp: local file ./UPLOAD/A904_14_web.jpg cached (4517281 bytes)

And that's where it hangs. No file is ever written and it is perpetually working on photo "A904_14_web.jpg"

Tests of the ftp server and the resize methods show no problem. All was working routinely in EE 1.54

Suggestions anyone ?

One thing I noticed. The files in the UPLOAD folder, which were formerly (EE 1.5.4) owned by me, are now (EE 2.02) owned by www. Is this expected ?

Thanks

Richard

[UweB]

I have this problem sometimes with a single image out of a bunch of many others depending on the EXIF IPTC Data within the image... I prepared the image one more time with the same procedure and then it works...

[rlkingston]

After some troubleshooting I found that a file will eventually get uploaded to the exhibit directories ... however the process is *really* slow. It's taking 60-80 seconds to get a single 2 MB jpeg file from the UPLOAD folder into EE (with no resizing !!). Yikes. This same process took seconds in EE 1.5. So this is now more explicable but still very problematic. What's taking so much time ??

[Pete]

This same thing is happening with me as well. I'm using the GD method for resizing, and the upload will refuse to work when resizing to 1200px wide, when it'll be fine for small (320px) and normal (800px).

I have no idea why this is happening, must be a bug in GD? My next step is to work out how "large" I can make "large" without it crashing.

It's somewhat disappointing, since it seemed to work perfectly happily with EE 1.5.

[aperry]

This same thing is happening with me as well. I'm using the GD method for resizing, and the upload will refuse to work when resizing to 1200px wide, when it'll be fine for small (320px) and normal (800px).

I have no idea why this is happening, must be a bug in GD? My next step is to work out how "large" I can make "large" without it crashing.

It's somewhat disappointing, since it seemed to work perfectly happily with EE 1.5.


I had a similar issue for larger images (anything 3 megs or above). Some of them would just refuse to work. I solved the problem by increasing the php memory limit from 8M to 16M. It's located in php.ini. After changing it I think you need to restart Apache.

I'm not sure if you'll be able to change this setting if you're running in an ISP.

Hope this helps.

Aaron

[Pete]

Thanks, Aaron. Not too sure I'll be able to do anything with the php.ini file as I'm using hosted web space. I'll simply resize the shots to a reasonable size before the upload.