Hi @ErneOchoa ,The components are enabled by adding them into the policy of the template.  Ideally this shouldn't happen, I have never seen this issue with an upgrade to service pack, but to fix this, you can just re-enable the components on the we retail template. Check this post. I have explained ...

Hi @gavya ,Please go through these reference links:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-read-the-count-of-components/m-p/204041http://suryakand-shinde.blogspot.com/2016/08/aem-get-list-of-components-templates-or.html 

@Raja-Karuppsamy you can create a workflow model which will trigger email to the specified group. It will be process step so no intervention would be needed. As soon as the page gets unpublished, the email would trigger.

Hi @sue1976 ,There could be an issue with the stat level at the dispatcher. When you don't set your stat level correctly, on activation, the complete cache will be invalidated. check this documentation.

AEM dispatcher is not supported on nginX web server. There is a similar thread: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/does-aem-support-using-nginx-as-a-dispatcher-server/td-p/310494 

Hi @odabio,You need to create a separate custom component which will be your re-captcha component. Please refer to this link: https://aeminmyway.blogspot.com/p/google-recaptcha-v3-in-aem.html It documents the steps to create component and integrate AEM with Google re-captcha. 

Done!!

hi @simirving ,You are trying to check at the wrong place. Please follow the below steps:1. On the page, click on the three lines shown in the image and click on edit template from the dropdown.2. New tab will open, there select the parsys and click on the policy icon as shown in the image. 3. When ...

Hi @Raja-Karuppsamy ,We don't have AEM page expire as an OOTB feature similar to asset. But same can be achieved using manage publication option. You can set timer to unpublish the page. Below screenshot are for the reference:

Ideally if there is no reference of old site in new site, publish shouldn't impact. Can you share the scenario again, is the same page in old site is also getting published ?