@BhavaniBharani  I do have a similar ask and was able to achive it. Follow below article on virus scan that generates a report of history from var. If this is helpful let me know. So that I can help you with the coding part.    https://technolearning-jags.blogspot.com/2023/08/aem-virus-scan-part-1.h...

@Mahesh_Gunaje  Considering perfomance storing user details in browser cookies can be good appropriate for some use cases. but it's essential to implement proper security measures and consider alternatives based on your application's requirements and compliance needs.   Below are some of the guideli...

@PoovithaSelvaraj  AEM doesn't have a default configuration that explicitly limits the length of selectors.  Some older web browsers have limitations on the maximum length of URLs they can handle. While modern browsers have significantly increased this limit, it's still possible to encounter issues ...

@priyak  We are missing some thing here. As per the statements that you mentioned above there is not much that you have done. It's just that you followed very simple steps. But still you are getting this error.    My suggestion would be to try the same in a veenila instance. Expecting that you proje...

@harrib01-cusa  have you tried publishing the configs from preview distribution queue ? We once faced this issue but by publishing the configs from preview distribution queue it worked.   /libs/granite/distribution/content/distribution.html    

Hi @stiegjo22    AEM works with very lower versions of PDFBOX only. Might be this the limitation while you are working in AEM, so keep these things in mind.  

@priyak  Then its a surprise their should be some project specific issue then. Once try below solutions once    Go to the content fragment model in AEM and check if there are any warnings or indications that it is outdated. If so, follow the prompts to update the model. This usually involves review...

@priyak  Are you creating the content fragments at right place ?   You should have created your Model under a project folder (by default creating a Model at the root folder is disabled). You have to be in a folder with the same name in Assets in order to use your Models. Here is an example of what I...

@priyak  any thing in logs that you see while you publish the content fragment or on the page load ? 

@mvotos can you check the user which you are using to create folder in asset location does have permissions to create folder ?    window.btoa(`${AEM_USERNAME}:${AEM_PASSWORD}`)   I tried the same in my local using admin user and its working for me