Hey @ASP_Corp , Yes, a Groovy script can be used to fix this issue efficiently. Below is a Groovy script that recursively scans and adds the missing jcr:content nodes to cq:Page under a given path. Similarly, you can update for other node primary types. import com.day.cq.commons.jcr.JcrUtil import j...

Hi @JulioRo , To load a client library only on the AEM Author instance and never on Publish, use a Sling Model to check the run mode. Sling Model: package com.mysite.core.models; import org.apache.sling.api.SlingHttpServletRequest; import org.apache.sling.models.annotations.DefaultInjectionStrategy...

Hi @Kk35 , Below are the explanations for your queries. 1. How are different environments mapped to different run modes - AEM uses run modes to apply environment-specific configurations. These run modes are specified during startup and determine which configuration settings and bundles are activated...

Hi @nbg19a , Below are the responses to your queries: The session obtained from resolver.adaptTo(Session.class) is not thread-safe.You do not need explicit concurrency control since a new session is created per call, but you should be aware of JCR node conflicts when calling session.save().Your use ...

Hi @Nandheswara , The ConcurrentModificationException error during the bnd-maven-plugin execution in your core module typically indicates issues with Maven dependencies, Java versions, or plugin compatibility. You can try below steps to resolve this issue: 1. If your project is on Java 8, consider u...

@Sai_Krishna_1404 , Modify the Sling Model JSON export by using Jackson annotations as below: 1. Use the @JsonIgnore annotation to exclude allowedComponents @Inject @JsonIgnore // Exclude allowedComponents from model.json private List<AllowedComponent> allowedComponents; 2. If modifying the ...

Hi @KARTHIKAV1 , If you are using AEM Translation Projects, verify the translation job setup to ensure that en_gb is being used instead of en-gb.In some cases, manually setting the language root in the translation configuration may help. Regards,

HI @GPhillips58 , Boss EAP 7.4.10 primarily utilizes the JBoss Logging framework, which does not inherently include the vulnerable components of Log4j. Therefore, the core JBoss EAP is not directly affected by the Log4j vulnerabilities. However, if your applications deployed on JBoss EAP incorporate...

 This issue commonly occurs when upgrading from javax.servlet to jakarta.servlet. The primary reason is that jakarta.servlet introduces breaking package changes, which require recompiling and updating dependencies accordingly. You can try below steps to resolve this issue: 1. If your project has dep...

Hi @jezwn , Your package-lock.json file specifies npm@11.0.0, but your client environment is using npm@9.9.4. In this case you can try below steps: 1. If your sandbox uses npm@11.0.0 but the client environment is on npm@9.9.4, update npm in the client environment. npm install -g npm@11.0.0 2. npm ci...