I will just be trying to overlay the javascript as that seems like the only viable solution unless someone else has an alternative.

I think you are misunderstanding. My client wants each of the different extensions to be treated the same so that there won't be repeated file names the issue is when we have two assets with the same name but different extension (of the same filetype). Example examplename.tif and examplename.tiff ar...

Would it be possible for this approach to still have the same "Name Conflict" dialog? Or would I essentially need to recreate the same client lib located at /libs/dam/gui/coral/components/commons/fileupload/clientlibs/fileupload/js/fileupload.js for just tif files with my custom handling of extensio...

What would be the simplest approach to have aem 6.5 treat the various tif extension variations (tif tiff TIF and TIFF) as the same or convert them during upload? Ideally this would occur as a file is uploaded and would trigger the Naming Conflict popup if another file has the same name but a differe...

@TarunKumar Could you look at my other reply and let me know if there's a different url I should be using.

Hi Tarun,The slingjsp address you gave returned me the following message: The requested page was not found. If you are not forwarded in 3 seconds to the Web Console, please click here. I am using AEM 6.5

We have overlayed a jsp file to customize the touchUI, but some of the unaltered code from the overlayed jsp file is throwing an unexpected error: 05.09.2024 13:52:40.181 *ERROR* [10.1.204.145 [1725569559794] GET /mnt/overlay/dam/gui/content/assets/jcr:content/views/list.0.html/content/dam/my-dam/ph...

It was an issue with port forwarding in the linux firewall the dispatcher was on.

Were you able to find the solution to this issue? I'm having a similar problem with the null session. 

Thanks for flagging this, but we managed to fix this issue. It was a window's driver issue that we resolved with Microsoft's tech support.