Which version are you on? I think that replacement of files was not implemented in CMS 7 but added at some later stage, probably 7.1 or 7.5 so if you are sitting on a plain vanilla EPiServer CMS 7, you need to upgrade to get this functionality.
Thanks Linus. This would likely be our solution. When we first moved to CMS7 and patched to 7.1 we lost harmony with editors who were not pleased with the new editor interface. CMS7.1, from memory, removes the ability to use Old Edit mode (or some other problem was encountered for Editors) and we were forced to revert. The problem I have initially posted is a as a result of Editor request so we are able to go back to our team with the virtues of why we need to keep EPiServer minor releases employed. This response will certainly help our case. Regards, PK
Thanks for the information Piquet. I would strongly consider an upgrade to the latest EPiServer CMS version. Since 7.1, there have been quite a lot of improvements to the user interface and if you get into the continous release flow, it's much easier to upgrade more often to get the latest updates.
This seems like it should be pretty simple but I can't find a reason for the following behavior. In CMS6 batch upload of images worked after allowing users the access permission. If they replaced images of the same name a dialog warned that they were being replaced.
In CMS7 our set up allows batch uploading for first files, but then - for upating images, the upload simple repsonds FAILED. Editors report that they have to go about creating/doing versioning for each individual file. Frustrating with hundreds of updated images.
Is ther a setting or something I'm missing? Thanks.