@RahulSi13 , You can try reactivate and/or page/asset. For the permanent fix, set the dispatcher rule shown below. <Location ~ ".+.{1}(?i:adsklib|asc|avi|csv|dfx|doc|docx|dot|dwg|dfx|dxf|edrw|enc|eps|flv|gif|gsm|ico|ifc|igs|jfif|jpe?g|lcf|mov|mp3|mp4|mp?g|pdf|pln|png|ppt|pptx|psd|rar|raw|rfa|rvt|svg...

Hi @AnushaAt  Add the filter condition like blow in you dispatcher filter.any file. { /type "deny" /suffix '(.*infinity.*|.*children.*|.*tidy.*)' } 

You can try something like this as 'Validate' script of date field: if (event.value) { var currentDate = new Date(); // Adjust current date to start of day for accurate comparison currentDate.setHours(0, 0, 0, 0); // Use util.scand to convert the entered date string to a Date objec...

Hi @HanLu1 ,You need to uncheck the required and use custom JS / clientlib to validate the fields. 

Hi @fastdo ,If your requirement is to restrict the author to not select a past date then it could be achieved with the minDate property with value as "today". Or you can achieve it using Jquery: $(function() { $( "#datepicker" ).datepicker({ minDate: 0}); });

Hi @SyntaxError_07 ,  You can use the attributes to add defer. please refer below link. https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/developing/including-clientlibs#attributes <sly data-sly-use.clientlibs="${'com.adobe.cq.wcm.core.components.models.ClientLibrar...

This behavior is expected in AEM as a Cloud Service. When you update metadata through the UI, AEM automatically creates the required node structure (like /metadata/default) because the UI respects the metadata schema and ensures compliance with the repository model. Once that node exists, the Assets...

@Mailyn_TMo Several factors could cause assets uploaded via Postman to appear in AEM but not in the AEM Assets UI:Workflows Not TriggeredAEM relies on workflows like DAM Update Asset to generate renditions, extract metadata, and index the asset in the repository. If these workflows didn’t run, the a...

To effectively mitigate this alert, direct access to the endpoints /bin/querybuilder.json and /bin/querybuilder.feed should be disabled. Instead, implement a custom servlet that encapsulates query execution logic. This servlet must enforce strict input validation and explicitly define the permissibl...

Hi @MateuszNo2,  If a deployment introduces a critical bug that breaks important functionality or causes the website to go down, the immediate recommended action is Redeploy the last known stable build using Cloud Manager.   This is the safest and fastest way to roll back because AEM Cloud Service d...