Hi @Vani1012,Navigate to the lower-left section and locate the "JSON QueryBuilder Link". Click on this link to access a list of page paths along with their associated tags.

If I have understood your requirement correctly, you can use the query builder to obtain paths and their associated tags as shown below. path = /content/masters/en type = cq:Page tagid = atlas-copco:industrial-tools/expert-hub/industries/industrial_assembly tagid.property = jcr:content/cq:tags p.hit...

We used acast.com for hosting podcasts and broadcasting them to platforms like Apple Podcasts, Google Podcasts, and Spotify. Acast provides an embedding feature that allows us to seamlessly integrate podcasts into an AEM component using an iframe.

Hi @sean12341, You can add default content to nested components using cq:template. For a detailed step-by-step guide, you can refer to this resource: http://prashantonkar.blogspot.com/2019/01/composite-components-in-aem-using.html 

Hi @n_radhakrishna, It seems like the request is being blocked by filters. To identify which filter rules are causing this, I suggest reviewing the dispatcher.log where you should be able to pinpoint the specific filter rules responsible for blocking the request.

I have tested the same configuration on my local dispatcher, and it's working as intended. If you want to make the URL matching case-insensitive, be sure to add [NC] after the RewriteCond rules. Also, confirm that the URL is a child of /us/en/xyz/ and not the /us/en/xyz.html itself. RewriteCond %{QU...

If I understand your needs correctly, you want to broadcast the modifications from the blueprint version to the live copies. This can be accomplished by employing the "Rollout" operation (from the blueprint) and the "Synchronize" operation (from the live copies). 

AEM has two variations: AEM 6.5 and AEM as a Cloud Service (AEMaaCS). You can find the Latest Version by following the links provided below.AEM 6.5: Latest version is 6.5.18.0 [0]AEMaaCS: Latest version is 2023.9.0 [1][0]: https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/r...

It mostly depends on your use case. You can add the OSGi configuration for the scheduler only for the author run mode, ensuring it executes just once.

Hi @anasustic,I guess that you have multiple author and publish instances where the scheduler is running, possibly three instances in your case. This is why the email is sent three times at 2 AM.