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...

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 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...

In a scalable solution if I were to do this, I would rather create an super class sling model (parent class). This super class would have all the common methods that you would be using in your sub classes. Each sub class would inherit from the parent class, and so when you create 3 components, each ...

Here are the differences between AEMaaCS, AEM On-Prem, and AMS, broken up in the contexts: 1. Infrastructure and Maintenance: AEM as a Cloud Service (AEMaaCS): Infrastructure: Fully managed by Adobe on cloud infrastructure.Maintenance: Adobe handles all updates, patches, scaling, and infrastructure ...

No, I found out the problem, its because Adobe Core Components, latest version have introduced a bug,https://github.com/adobe/aem-core-wcm-components/issues/2736   As you can see in this commit, https://github.com/adobe/aem-core-wcm-components/commit/27fda047ff40ca7f7be8889320b428bf5adc3e4c#diff-e28...

This is a recruitment post... reporting.

I agree with this.

The issue you're experiencing with publishing templates from the Author instance to the Publisher in AEM 6.5.16, where templates appear as "null" on the Publisher, seems to be related to an exception thrown by the com.adobe.cq.mcm.campaign.impl.CampaignPageCopyEventHandler. The NullPointerException ...