Thread

My Client is using EE 1.6 Build: 20070815

They recently moved servers, and this morning they reported a file upload issue:

Basically, when they went to upload an mp3 file using the “Upload File” button in one of their weblog entry forms the “File Upload” pop up window went blank (white) after they pressed “Upload”.

I replicated the problem and updated to the most recent EE build ( Build: 20070815 ) this morning.

After updating I uploaded a file with no problem and let the client know the problem was fixed.

However, when my client went to upload a file they received this error:

“1 of 2 completed” and it just hangs there and eventually the page goes blank (white)

I went back in and tried uploading a file and received the same error as my client.

Any help would be appreciated.

I’m not sure about the error your getting, but I just completed a site using mp3s and I created a separate directory from EE for the client to upload mp3s too.  I didn’t want to reveal my directory structure and wanted to make the user download the mp3 to their desktop.  Keeps bandwidth usage to a minimum.

The only downside is that the client has to type in the link, but its a simple /download.php?filename=file link which I just included instructions in custom field notes. 

The /download.php is a script that sits in your root directory and keeps your mp3 directories hidden from hacks and forces the user to download the mp3.  Let me know if you want the script and instructions.

Double check the file size of the .mp3 file they’re trying to upload. A blank page can mean not enough memory allocated.

Thanks grantmx, I’m actually using that script and the mp3’s are uploading to their own directory. That’s not the issue.

I’ve not encountered the issue I’m getting prior to this post. I have a feeling it has to do with migrating the site to the new server. However at this point I’m not certain.

On an aside, I’m not sure why your client would have to type in the link when you can place the path to the directory containing the mp3’s inside the download.php script and have it so that when the link to the mp3 is clicked the file automatically downloads to their desktop.

> Sue

Thank you for your post.

This is odd. I received the same error on a file that I uploaded moments before.  (note: I renamed the second file)

I just tried again and now I’m not getting the error and it’s uploading perfectly fine.

Ok, before I waste any one elses time I’ll contact the client have them try and see if the issue has been resolved.

The link they have to type in is /download.php?filename=file.  Yep, the path is in the download.php script.  Some clients aren’t that savvy.

But when I think about it I could have created a custom field, maybe “mp3_filename” that populated the =file.  could have done something like: /download.php?filename={mp3_filename}

All they would have to do is add the name of the mp3 to the field.  something.mp3

Thanks!

Exactly grantmx!  np.

I have repeatedly uploaded MP3 files, and now I am not receiving any error.  Which is a good thing!

They were odd errors which resulted in my post. I’m in discussion with the client and hopefully this issue is either server related or just good old patience.

It would be great if the Upload File pop up window had a status bar that showed the file’s uploading progress. Many of my clients upload files that are larger in size, and MP3 for example.  I can see how they would get frustrated not knowing if the upload had frozen or if the file was still uploading.

Hi Drew,

Just a quick question but are you using Safari at all to upload the files with?
There is a problem with Safari if you have the cache turned off where files will not upload properly or sometimes at all with this feature turned off.

If not then please ignore this post!! 😊

Regards,

Mark

> Mark

Thanks for your post.

Yes I am using Safari when I am uploading files.  I’m not sure what browser my client is using. However, I will be speaking with them today and find out.

Hi Drew,

If you have a program such as Mac Pilot then you can check to see whether or not the cache has been disabled. If it has then uploads will pretty much always fail using EE as Mail needs the cache to place the files into a temporary place on your computer whilst it uploads them.

If your client is using Safari then this might be something to check out also. If not then maybe there is a similar reason on their system?

Hope this all helps though.

Best wishes,

Mark

> Mark

This sounds like a very good possibility, and thanks for the Mac Pilot application tip.  It is strange however that I would have no problem uploading files pre server switch, then experience the same problem as my client at one point in the day yesterday (post server switch) and now everything seems fine on my end, yet the client is still experiencing a road block.

Just so we get closer on this thread I will post back when some new light is shed.

The cause of the issue has been found and Sue was definitely on the right track (thanks Sue).  The new host has their “post_max_size” set at 8MB, which would shed light on why I wasn’t having problems uploading a 5MB file and the client was having problems with a 9MB file.  I’ve never seen a “post_max_size” that low but the host has been contacted and the issue is being worked out.

Thanks for all the help!