The html code you are getting happens when the client ID is not correct. You must be using some domain for your dispatcher, did you register that domain to get a new client ID. For author and publish domain, it will be different and for dispatcher domain it will be different. Check if you are using ...

Hi @TB3dock ,As per the documentation AEM as a Cloud Services does not support custom log files, however it does support custom logging.For Java logs to be available in AEM as a Cloud Service (via Cloud Manager or Adobe I/O CLI), custom log statements must be written the error.log. Logs written to c...

Hi @mallipanchal007 ,Does it work when you pass a query parameter in the browser url? If so, clear all the cache in the dispatcher and check. If not we can look at other things

Hi @hr-empd ,I tried and did see the exact same error you have mentioned. But as per documentation, I did installed the given package in the acs commons documentation here and it did work for me.Try restarting your instance and then go and do the search, ignore the message if it still appears but th...

Hi @aem-enthu27 ,You can setup jenkins on your local. There is a jenkins plugin "Adobe Cloud Manager Plugin". Once you install this on your local jenkins, it does allow you to run different scripts on your codebase. This will perform similar checks that happens on Cloud Manager. There are some confi...

Hi @Giuderos ,You can generate a new project using the latest archetype forAEM 6.4.5 and then copy the ui.content in your code base. You will have to update the pom.xml as per your project version and dependency. Also, include this new content structure in your parent pom.xml.Once this is done, You ...

Hi @ZdenekK ,There are two ways to fix this. You can write a rule at dispatcher rule so that this header will be updated from attachment to inline like this. <LocationMatch "\.(?i:txt)|(?i:pdf)|(?i:xml)|(?i:png)$">. -->add all your extensions hereHeader set Content-Disposition inline</LocationMatch>...

Hi @andmiccrew ,For junit, code coverage is required to be 50% for the cloud manager code quality to pass the check. But this is not mandatory which is going to fail the build. If the coverage is lower than 50%, you will get a notification and your deployment will be paused. You can still override a...

This looks like an OOTB the feature rather than an issue where that garbage collector clears out the unused tags after the merge. Reference Link: https://experienceleague.adobe.com/docs/experience-manager-65/developing/platform/tagging/framework.html?lang=en#moving-and-merging-tags 

Hi @Kaibalya_123 ,Layout container is nothing but an open parsys, where you can drop any allowed component. If you have to sort/count the number of Teaser component dropped inside a specific layout container, The easiest approach would be overlay the OOTB layout container component and then iterate ...