Hi, I think that is caused because the parsys(and btw, you should use a container instead) are being included without a wrapper, try to use this: <div data-sly-resource="${ department.name @ resourceType='wcm/foundation/components/parsys'}" style="margin: 10px;"></div>   Hope this helps

Hi,   Can you replicate this locally and then remove the directive you think is causing the conflict to confirm that it is the source of the issue?   Hope this helps.

Hi,   I am not sure if I am understanding correctly, but can you update the workflow to publish the page at the desired time?   Hope this helps.

Hi,    You can manage this scenario using granite:renderconditions. 1. Create a metadata that contains the metadata for all of the different type of assets 2. Go to your metadata definition, (usually under: /conf/global/settings/dam/adminui-extension/metadataschema) 3. Add a granite render condition...

Hi,   I don't think you can use a service token for Adobe's git repository. However, if you follow the recommended approach and use your own git repository in front of Adobe's, you should be able to connect your Jenkins to your own git, and then mirror your git with Adobe's. You can learn more here:...

I don't fully understand your question, but if you start AEM using the script under the bin folder, then you must stop it using the stop script under the bin folder.   Hope this helps.

Hi, Short answer: No. The project from wcm.io is the main mocking framework for AEM. If needed, you can examine how some of those objects are implemented to create something similar for the CryptoSupportService. But conceptually, it is acceptable not to use the real CryptoSupportService because you ...

Hi, Please try this: https://aemsimplifiedbynikhil.wordpress.com/2022/01/14/troubleshooter-1-pkix-path-building-failed-sun-security-provider-certpath-suncertpathbuilderexception-for-node-js-installation-error-in-ui-frontend/    Hope this helps

Hi, Please check this article which describes the issue you are facing; https://helpx.adobe.com/experience-manager/kb/users-randomly-getting-your-request-could-not-be-completed-because-you-have-been-signed-out-in-aem.html . Can you also elaborate on what you were trying to accomplish when this happe...

@thirumurthy, did you try the code I shared? Did you notice any differences with your code? Can you tell us which version of AEM you are using? As you can see, this works fine in a vanilla AEM 6.5.17 instance and also in AEMaaCS. My advice is to validate whether you have any custom code (CSS) causin...