- Select 'manage' on an existing attachment, e.g. "RFP_Document.doc"
- Attach a new local file, which you've named e.g. "RFP_Document_Bosses_Changes.doc"
- Hit upload.
Boss expects to be wowed by the fact that her changes are 'revision controlled' thus no matter how many people upload with whatever names they choose, the first name is the official one and the other ones are filed behind it,
Not so, this creates multiple named files in the attachment table.
This is not "managing an existing attachment"
Correct. This is consistent with Cairo behaviour. I proposed fixing it some time ago, but got no support. Too late to fix for Dakar, so deferred. CC
Additionally, programs like MS Excel cannot cope with two files with the same name open at the same time. This means that comparing an old version to a new one has to mean they download with different names.
So, on the one hand we force users to have the same filename, on the other Excel forces them to have different file names.
For pointy haired managers, Excel will win.
Undeferred, post Dakar CC
MC, do you know how MS deals with this excel/office-compare peculiarity in their own software having versioning - i.e. SharePoint? (As far as I can tell, they simply do the same thing, old versions are downloaded under the same original name, always).
But hey, offering "old" files as also downloadable with revision_number or/and upload time added to filename doesn't sound too hard (perhaps even a configurable naming scheme for this). Don't know how much value it would add though.
Me neither. Discarding. This is appropriate for a brainstorming discussion in Codev, not a bug report.