Yes, simply to remove all /tools/* paths, from sitemap.xml on your EDS website, include:1. on Google Drive, create "metadata" google spread sheet, and then place what you see in the table.2. on Sharepoint, create "metadata.xlsx", and then place what you see in the table. URLrobots/tools/** noindex,...

When using AEM dispatcher locally, the local dispatcher typically won't start or function properly if your dispatcher validation rules fail. Dispatcher configuration validation is critical in AEMaaCS to ensure that the rules adhere to the strict configurations enforced by the cloud environment. Use ...

It’s best practice to keep clientlibs cached at the dispatcher and CDN levels to ensure your website is as performant as possible, so I would not remove the rule. In fact, you don’t need to do anything because when you release a new change to AEMaaCS, the website cache is deleted. Assu...

@NidhiKu , follow this tutorial and you will be soon on your way In the tutorial you'll learn how to setup multi-field, next you will be abler to iterate through each item and render HTML elements on the page.   <?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:jcr="http://www.jcp.org/jcr/1.0"...

A scenario for this could be that a dispatcher filtering out and limiting rendering of that specific file.Check your dispatcher, does it allow webp files? /filters { /0001 { /type "allow" /url ".*\\.webp" } /0002 { /type "deny" /url "/etc/.*" } ... }

If you're using a dispatcher in front of the publisher, the servlet endpoint (e.g., /bin/checkStatus) might not be accessible due to the dispatcher rejecting or blocking the /bin/ path. /filter { /0069 { /type "allow" /url "/bin/checkStatus" } }  

To set up the new Content Fragment (assuming you meant by 'CF') editor in AEM, the process differs slightly depending on your version. For local AEM 6.5 version, ensure that the the latest service pack is installed, as the availability of the new CF editor may depend on specific updates. Once your i...

Yes, Deploying a bundle (software package) built with Java 11 to an AEM instance running Java 8 can cause problems. Java 11 has new features and changes that Java 8 doesn’t recognize, so this could lead to errors. AEM bundles compiled on Java 11 to an AEM instance running on Java 8 will indeed cause...

Hey, sorry nope, your own custom solution is required. 

Hello, your link TextUtil must be not working as expected….  you can simple return hard coded text, to see if the method is retuning anything correct, and if so, must be your TextUtil. Something is not working there.  public String getFormattedText() {   return "I love sourcedcode.com!";}