We just got out of this challenging problem as well. Jumped into a call with Adobe, and pinpointed the problem. The problem here is that the latest AEM Core Components introduced this bug.     Let's take a look at what I am pointing to here, so what was removed was the ability to have customers set...

Adobe wants to provide the best experience to their customers, and so this CDN layer is by default enabled for all AEMaaCS websites.   Disabling or configuring the Fastly CDN on your AEM as a Cloud Service (AEMaaCS) environment requires coordination with Adobe support, as Fastly is a key part of the...

We just got out of this challenging problem as well. Jumped into a call with Adobe, and pinpointed the problem. The problem here is that the latest AEM Core Components introduced this bug.   Let's take a look at what I am pointing to here, so what was removed was the ability to have customers set w...

How you can resolve this is by passing the string to a backend Sling Model Utils Class. like:   <option value="message" data-sly-use.stringHelper="${'com.sourcedcode.core.utils.use.stringHelper' @ string='<p>Message here with a <a href=&quot;/content/project/site/en/about.html&quot;>link</a> to an i...

You can try to setup your AEM publishers with https(SSL) - Adobe Experience Manager Tutorials: Configure the https(SSL) on AEM instance quickly (aemtutorial.info)

I got a code snippet laying around that you can try: import static org.junit.jupiter.api.Assertions.*; import static org.mockito.Mockito.*; import com.day.cq.tagging.Tag; import com.day.cq.tagging.TagManager; import com.day.cq.wcm.api.Page; import com.day.cq.wcm.api.PageManager; import io.wcm.testi...

I have created a blog article for this problem in the past. I have provided detailed tutorial on how to hide tabs based on style systems selected by the content author.   How the solution works:The AEM developer will add code configurations to the cq_dialog.xml which targets one or more tabs with so...

When using the wcm.io mocks library in your JUnit5 tests for AEM, ensuring that cq:tags are correctly retrieved requires proper setup of the mock objects and their properties. Here's how you can make sure cq:tags are correctly mocked and accessible in your tests. Steps to Mock cq:tags Property Corre...

Resolving tags in AEM can sometimes encounter issues due to configuration differences between author and publisher instances, or due to differences in the content repositories. Here are a few steps you can follow to troubleshoot and resolve this issue: Steps to Troubleshoot and Resolve Tag Resolutio...

Looks like you may have tampered with the replication agents on your local machine. You'd need to ensure that you are pointing to the correct AEM instance for example 4503.