ASSET filename blacklist | Community
Skip to main content
C
culver-king
Level 2
October 20, 2023
Solved

ASSET filename blacklist

  • October 20, 2023
  • 2 replies
  • 1135 views

Hi again community, I've been managing assets for a client for some years and for the first time had a file blacklisted from the dam and wouldn't allow users to access it. It would show in the library as an asset, but the thumbnails were absent and when you clicked on it, AEM would return a block error.

 

I worked with my dev team and they determined that it was because a specific string/word was used in the filename. In this case it was `frames`. I asked them if they could provide a list of blacklisted strings/words/phrases and they said they didn't have one. I'm guessing it was an OOB best practice filename blacklist. Is there such a list in the AEM documentation that I'm missing? I did a search in the support section but couldn't find anything. I'm sure its there, but I probably used the wrong search terms to get the desired result.

 

Anyone have it handy, or know if one exists?

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

2 replies

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
October 24, 2023

Hi 

 

I just uploaded an image with the name "frame.png" without any problems (1). This implies that if the asset's name is indeed conflicting with AEM functionality, it must be due to some unusual customization on top of it.

 

That being said, the assets have two "names": the title and the name. The title can have any character in it, and it is the name that is displayed on the screen. However, the name will follow the JCR rules for nodes, which are not too restrictive. It doesn't allow certain special characters but not any specific "string" in the name. Therefore, my advice would be to reconsider why the image is causing such unusual behavior.

 

(1).

 

 

Esteban Bustamante
    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    October 26, 2023

    @culver-king Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

    Kautuk Sahni
    C
    culver-kingAuthor
    Level 2
    October 26, 2023

    It is helpful knowing that there isn't an OOB restriction on name/string other than standard exceptions for special characters in their testing. However, I was still looking for any documentation that indicated as much. I wanted to use it to discuss with my development team about the current blacklist they have implemented.

      EstebanBustamante
      Community Advisor and Adobe Champion
      EstebanBustamanteCommunity Advisor and Adobe ChampionAccepted solution
      Community Advisor and Adobe Champion
      October 26, 2023

      @culver-king this is what I was referring to in my previous answer, hope this helps: 
      https://experienceleague.adobe.com/docs/experience-manager-65/developing/platform/naming-conventions.html?lang=en
      https://jackrabbit.apache.org/archive/wiki/JCR/NodeNamingConventions_115513460.html

      Esteban Bustamante
        Terms & ConditionsAccessibility statement

        Loading footer...