Extending File Name Validation in AEM Assets | Community
Skip to main content
medhik
medhik
Level 2
October 26, 2017
Solved

Extending File Name Validation in AEM Assets

  • October 26, 2017
  • 6 replies
  • 7663 views

AEM 6.3 by default restricts some characters in file name.

How can I extend the restriction for a few more characters?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Techaspect_Solu

    Hi,

    We were able to extend the filename name validation functionality to few more characters (say '-' here) in AEM 6.3 assets successfully. The following js file is responsible for filename validation:

    /libs/dam/gui/coral/components/commons/fileupload/clientlibs/fileupload/js/fileupload.js

    For extending the restriction functionality to few more characters, we need to overlay the above node (fileupload.js) and make the required changes in it.

    Changes to be made in overlay location (/apps/dam/gui/coral/components/commons/fileupload/clientlibs/fileupload/js/fileupload.js):

    Sample output:

    We hope this helps!

    Regards,

    TechAspect Solutions

    6 replies

    smacdonald2008
    smacdonald2008
    Level 10
    October 26, 2017

    We asked Eng to look at this question. This logic is somewhere - i am not sure where as i have never read this use case before.

    manoj_devapath
    manoj_devapath
    Level 5
    October 29, 2017

    We need a jcr event listener on new node created in dam. and then add your custom logic to rename the node. use node move logic and save the asset.

    we did this custom logic implementation on page creation. its same for asset upload too.

      Techaspect_Solu
      Techaspect_SoluAccepted solution
      Level 7
      October 29, 2017

      Hi,

      We were able to extend the filename name validation functionality to few more characters (say '-' here) in AEM 6.3 assets successfully. The following js file is responsible for filename validation:

      /libs/dam/gui/coral/components/commons/fileupload/clientlibs/fileupload/js/fileupload.js

      For extending the restriction functionality to few more characters, we need to overlay the above node (fileupload.js) and make the required changes in it.

      Changes to be made in overlay location (/apps/dam/gui/coral/components/commons/fileupload/clientlibs/fileupload/js/fileupload.js):

      Sample output:

      We hope this helps!

      Regards,

      TechAspect Solutions

        S
        Shetty1191
        Level 2
        January 18, 2022

        Hi Team, 

         

        I am trying to extend the same functionality. There are few more special characters like 'à','ç' (continuous pressing of 'A' in the keyboard will popup these values). So how can I restrict those values ?

         

        Can I change the '_IILEGAL_FILENAME_CHARS' to 'Legal_FileName_Chars' and check the same functionality.

         

        Thanks,

         

        manoj_devapath
        manoj_devapath
        Level 5
        October 30, 2017

        If you are planning to use custom logic to aem asset com.day.cq.commons.jcr.JcrUtil

        API is usefull.

        <!-- https://mvnrepository.com/artifact/com.day.cq/cq-commons -->

        <dependency>

            <groupId>com.day.cq</groupId>

            <artifactId>cq-commons</artifactId>

            <version>5.8.2</version>

            <scope>provided</scope>

        </dependency>

        JcrUtil ("The Adobe AEM Quickstart and Web Application.")

        medhik
        medhikAuthor
        Level 2
        October 30, 2017

        Yes, I could find this file and it worked.

        Thanks for your correct response.

        A
        Adobe Employee
        akshaypatilAdobe Employee
        Adobe Employee
        February 28, 2023

        This character list is now moved to /libs/dam/gui/coral/components/admin/clientlibs/damutil/js/util.js file which provides a helper function getInvalidFileChars  where any additional characters could potentially be added to the list.

          Terms & ConditionsAccessibility statement

          Loading footer...