My client has the wierdest problem and I wanted to see if you guys know of a way to either debugg it better or have experienced the same issue.
The client is trying to upload a file (standard EE file field) and when she has selected the file (JPG, 300kb) the loader just stands there spinning forever and nothing happens.
If I try the same file, on the same field/entry there’s no issues at all.
Is it possible for you to update the site to 2.3.0 and see if the issue still exists then please?
I know there are a few issues at the moment with Safari on Mac although to tell the truth I’ve never once had a problem with Safari and we are finding it hard to track this one down currently but if you can update to 2.3.0 then at least we will all be on the same codebase for testing with.
Right now it’s seems to be very random what works and what doesn’t. I’ve also tried to have then upload from different locations (Desktop, Home-folder, Harddrive, USB-stick) to make sure there’s no permissions error on their own system.
Also note I can upload all their files fine.
The map can’t be uploaded, but the smaller jpg can.
I downloaded those two files and tried them on multiple installations of ExpressionEngine and all times both files uploaded straight away without any problems.
The fact that we can both upload them without any problems leads me to believe that this might be a problem with your clients Internet connection maybe?
Are they behind any firewalls of any kind or is their connection perhaps a little dodgy?
Are you able to try on their connection to see if that is the problem here maybe?
Failing that are they able to try on a different connection with their user and see if the problem still arises?
Also if they try with the same file that fails on a different day does it always fail or does it perhaps upload at one point and not another?
As you can see from my previous comment the client can upload the file in FireFox, but not in Safari (spinner just spins…). Same connection. Same day. Same file.
I know this is a pain but are you able to test on Safari yourself using the clients login details?
Failing that are you able to try it for yourself on their computer using both their login details and also your login details just to see if there’s anything funny going on with the actual user accounts here?
Best I could do for you was to have the client do as I said over skype (shared desktops). Everything is as I said. Safari just spins… FireFox works. Very very strange. It’s the same EE account (just one, the super-admin account).
Is there some sort of debugger or error-log I can look at while it’s uploading? (I can hack the files if you give me direction).
If it’s to much of a hassle I guess we can close this issue. Would just be interesting to see what the **** is going on
As a point I’m experiencing the same trouble - Safari (5.1.1) spins and without an upload.
EDIT: Found it - from the root /images upwards, be sure all directories have 777 permissions. That would be:
/images/
/images/uploads/
/images/uploads/your directory name here
Explicit, but once these are set Safari works as advertised. I thought they were set but the root /images/ had a 755 on it.. newbie mistake.
I’m trying to upload again now and now it’s not working any longer… inconsistent behavior, more likely.
Perhaps looking at Safari might be a good idea.
Same here, safari works, firefox don’t. But this is something I have seen very often. Everything works fine with chrome, firefox… it’s just safari. I see a lot of errors on console, maybe these broke safari ajax behaviors
template_variables.js:6TypeError: 'undefined' is not a function (evaluating '$("a.copy").corner()') jquery-ui-1.8.2.tabs.min.js:33TypeError: 'undefined' is not a function (evaluating 'd.widget') template_variables.js:3TypeError: 'undefined' is not a function (evaluating '$('#tabs').tabs()') jquery-ui-1.8.2.tabs.min.js:33TypeError: 'undefined' is not a function (evaluating 'd.widget') template_variables.js:3TypeError: 'undefined' is not a function (evaluating '$('#tabs').tabs()')
The best we’ve been able to determine at this point is that Safari 5.1+ is having connection timeout issues. This leads to some difficulty in replicating the issue since we all primarily test on local installs or local networks, so timeouts wouldn’t be an issue. I’ll set up a test install on a remote server and see if I can get Safari to fail for the test. Thank you all for your patience and information as we try to work this out.
