Thread

I’m having issues with the File Manager where it’s showing the following message after uploading a file:

A file with that filename already exists. You can either choose a new name and the file will be renamed, or you can use the same name and the existing file will be overwritten.

The issue is that the file does not exist - I’ve checked (twice).

It seems to happen when uploading a screenshot snapped with a mac - for example a file named: “Screen Shot 2011-11-15 at 2.32.03 PM”  throws an error even though it did not exists prior to upload (the file does actually upload).  Ideas?

Running v2.2.2

Hi Philip,

I can’t replicate this. Can you try 2 things for us.
One is, can you link to the file you are using here?
And the other is to try an upgrade to the latest EE2.3.1 to rule out any interim bug fixes in-between versions

Hey Phillip,

I can in fact replicate this, have you come to any conclusions yet?

I’m running the latest version of EE

Best,
Scott

Hey Philip,

I just tried this in ExpressionEngine 2.3.1 and was able to do so successfully. I do remember in previous versions this was an issue. I’d recommend updating if you’re still experiencing this.

scottmey, be on the lookout for an email from me.

Thanks guys!

Hey Phillip,

Thanks for contacting me.
I filled everything out, if there is anything else I can do let me know.

Appreciate it,
Scott

Hey Scott,

I took at look at the site, and can replicate the issue you are having. Unfortunately, I can only reproduce this issue on your server. I attempted to reproduce this issue using ExpressionEngine 2.3.1 both locally and on a live server, and both were able to upload the same file successfully.

As a result of that, I want to say it’s a server configuration setting that’s preventing you from uploading the files, and that you should check with your host on this.

One thing to try before contacting your host would be to take a file that won’t upload into ExpressionEngine and try uploading it via cPanel’s file manager or the like to see if it accepts that.

That way you can narrow down what exactly is causing the issue.

Do you have any other questions?

Thanks!

Hey Kyle,

I really appreciate you taking a look.

Besides the image posting problem, we’ve encountered a few other problems. Now these problems were only encountered on production, not on my dev or local versions…

1)  Initially after updating to 2.3.1, our production site was booting users from the control panel to the CP login screen,
after a while (and after messing with session types and some of the other global variables, this problem sort of faded away after a few weeks but still happens once and a while.

2)  Occasionally on larger posts, or when we use Paginated entries (entry spread over a few posts) we encounter a 403 error after clicking Publish.

3)  We have a module called backup pro, which creates a back up of the database and the file directory. Since we pushed to production this doesn’t work at all, but on local and dev it does..

I’ve been battling with some of these and some other smaller issues, now, on my local and dev we’re running Apache, but on production it’s a tricked out version of Litespeed.

So, you’re definitely right, something funky is going on in there, I’m going to investigate this some more this week. Also, curious if anyone else is running Litespeed and has encountered any similar issues.

Thanks again Kyle!

Scott

UPDATE: I was able to upload a file named bIK&LiqenColab;-3521.jpg through the Cpanel File Manager without a problem.

Hey Scott,

I’ve brought this to the dev team’s attention for them to take a look at the file upload issues.

The sessions issue you mentioned is a known issue with ExpressionEngine 2.3.1, and we’re looking in to that.

Thanks for your patience.

Scott- appreciate the access.  One of the issues only cropped up if the directory was set to ‘images only’, which may be why replication was tricky.

This was actually a bug- I’ve entered it as such: https://support.ellislab.com/bugs/detail/17134

The fix is included with the bug report for those affected- and I added it to your site while I was in there testing it.

See if that does the trick for anyone running into this one.

Robin,

Thanks so much for looking into this. Seems to be fine now!

Kindly,

Scott

Thanks for the confirmation, Scott.

Phillip- does the fix in the bug track do the trick for you as well?