-
Bug
-
Resolution: Obsolete
-
Neutral
-
None
-
None
-
None
-
None
Founded on Swissre project, client somehow managed to upload more same assets into one folder (not sure how they did upload process exactly) but as a result they have same image 3 times in dam, and to differentiate jcr add 0 a 1 at the end of the name for duplicates (see screenshot). Unfortunately because this number is part of name, which dam templating function damfn.getAssetLink() generate the link including .jpg0 (/dam/jcr:bd5f60df-0776-46f9-b5c6-438515d5868e/GFZ_90m_resolution.jpg0) and imaging module then fails to render such a image (seems like he is doing mime type recognition based on extension, not real mime type saved in dam workspace).
Suggested improvements:
- when duplicate in dam app is created make sure that 0 will no be added after .jpp (or any else extension), rather before.
- if link for image contains uuid (e.g. /dam/jcr:bd5f60df-0776-46f9-b5c6-438515d5868e/GFZ_90m_resolution.jpg0) use mimetype in saved in dam instead of recognition from extension in url
- is related to
-
MGNLDAM-736 File renaming not persisted in node's name
- Closed