yes, I believe that you're supposed to manage it through the dispatcher configs. 1. Allow the dam path where the collection of these specific images is stored. 2. Allow the extensions, if not allowed in the filtered already. 3. Please make sure you follow the standard dispatcher configuration best p...

There you go, that package(org/apache/commons/lang3/StringUtils) is missing from the dependencies. As the code is working for your colleagues then no need to add the dependency again on the POM file. Please add this dependent jar/files to your .m2 repo and rebuild the code.

Hi @ChaoXiong,   To debug better, I would like to know the component that you are using. If it is custom-made, could you please give me the dialog XML?  Make sure that you are not loading any unnecessary extra client libs at the dialog level.   Thank you.   -Sravan    

Hi @sakd,   This has nothing to do with the OS.As you are sure on the versions already, just incase please make sure of these things:1. AEM Version including service pack 2. Java version    Firstly, main thing to check is if your bundles are active on the system console: http://localhost:4502/system...

Hi @Nikita___Garg,   After reading through your above comment, besides the Groovy script, I suggest creating a workflow process step where you could perform the logic (preferably using query builder API).  In spite of a one-time action, you can also utilize this process step if you want to add/remov...

Hi @Ravikanithi1,   Earlier this year, I remember someone saying that the workItem API is not working correctly (I don't have any more info). As a workaround, you can update the priority number through node API.Thank you.   -Sravan

Hi @maheswaraiah_m,the best way to deal with this is to override the layout container class through a delegation pattern and return the resource list based on run mode as told in the above components. more on customizing the logic: https://experienceleague.adobe.com/docs/experience-manager-core-comp...

Hi @Nandheswara ,   "allowBlank" is not pathfield property, please remove it and just keep the "required" property and check.if it doesn't work, please copy a pathfield from core components, to avoid wasting time in debugging this.Regards, Sravan

"Tags can be applied by authors and site visitors. Irrespective of their creator, all forms of tags are made available for selection, both when assigning to a page, or when searching."- source: https://experienceleague.adobe.com/docs/experience-manager-65/administering/contentmanagement/tags.html?la...

1,2 – if it is not constant or not to be authorable, isn't that contradictory?   "3.it always get the first child page url ."- Yeah, handle the logic in your java class!