We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

Confirmation on Uploading Duplicate File Names

Feature Requests

Jeremy S.'s avatar
Jeremy S.
353 posts
9 years ago
Jeremy S.'s avatar Jeremy S.

In ExpressionEngine 2.x if you uploaded a file that already existed it would notify you and ask if you wanted to rename the file.

In 3.x if you upload a file with the same name, it provides no similar functionality, if just overwrites without question. Could that be added back into 3? A modal that says something like: This file already exists: Rename or Replace?

How would a user possibly know they named a file the same as a previous one? That could cause a great deal of headaches, especially on a larger site.

       
James Mathias's avatar
James Mathias
225 posts
9 years ago
James Mathias's avatar James Mathias

Hi Jeremy,

This is a regression bug, could you please report it in the bug tracker so we can get it triaged and fixed?

https://support.ellislab.com/bugs

Thanks!

       
Jeremy S.'s avatar
Jeremy S.
353 posts
9 years ago
Jeremy S.'s avatar Jeremy S.

Curious about this bug: https://support.ellislab.com/bugs/detail/21446/no-notice-or-confirmation-when-uploading-overwriting-an-existing-file

In 3.1.2 it looks like File Manager just blindly creates a copies of a file, again with no notification to the user of whether this file exists, if you prefer to overwrite or rename etc. like in 2.x.

When a user uploads a duplicate/revised file and the system just assumes to make copies, the file manager is going to be a REAL mess of redundant files in a short time. This seems pretty fundamental to the user experience.

It’s nice to have this functionality as an option, but not the only available one.

       
James Mathias's avatar
James Mathias
225 posts
9 years ago
James Mathias's avatar James Mathias

Hi Jeremy,

Looks like the bug has been accepted, but no fix has been released yet. Once a fix is applied the bug will be marked as fixed in upcoming release.

       
Jeremy S.'s avatar
Jeremy S.
353 posts
9 years ago
Jeremy S.'s avatar Jeremy S.

Hopefully. I am just more curious how it will be addressed. Also, being accepted is not definitive to being fixed. There are a few “accepted” bugs listed for as far back as 2.3.1 still in the bug tracker 😊

       
James Mathias's avatar
James Mathias
225 posts
9 years ago
James Mathias's avatar James Mathias
Hopefully. I am just more curious how it will be addressed. Also, being accepted is not definitive to being fixed. There are a few “accepted” bugs listed for as far back as 2.3.1 still in the bug tracker 😊

Correct an accepted bug does not guarantee a fix.

I can’t comment on how the bug will or will not be fixed as we haven’t discussed a final solution internally yet. If I were to guess it will likely work like it did in 2, as it was a regression, and not a purposeful omission.

       
SChristy's avatar
SChristy
23 posts
about 9 years ago
SChristy's avatar SChristy

Is this being looked at? When using channel:form to upload a file, it is overwriting the current file if they have the same name. This is in EE 3.3.2. Any option would be better than that - whether a silent renaming so both exist or letting me rename the file.

       
James Mathias's avatar
James Mathias
225 posts
about 9 years ago
James Mathias's avatar James Mathias
Is this being looked at? When using channel:form to upload a file, it is overwriting the current file if they have the same name. This is in EE 3.3.2. Any option would be better than that - whether a silent renaming so both exist or letting me rename the file.

Hi,

We look at every bug submitted, and we accept any that can be replicated. An accepted bug doesn’t guarantee a fix, or a timeline for potential fixes. But we encourage you to watch any bugs that may be affecting you as we commonly (but not always) add a known solution to the bug report prior to it’s proper release.

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.