@jayv25585659 My bad; I meant to send the LogLevel with `Debug`. If you want, you can go with `Trace2` to get more detailed logging on why it is blocked. Tail this log file `tail -f /var/log/httpd/dispatcher.log` and check what is happening. Here are a few things you can focus on to debug:  Is the r...

@jayv25585659  There must be another rule in dispatcher filters which might be blocking it. Change the dispatcher log level to debug or trace and restart the dispatcher to notice which rule is blocking it.  Define DISP_LOG_LEVEL Warn Debug   Instead of allowing everything -> /0001 { /type "allow" /g...

@akshaybhujbale In AEM as a Cloud Service Publish and Preview servers, internal pages (login, sites, assets), including operational and health check pages, are not accessible. Alternatively, you can use Developer Console -> Repository Browser to look at the JCR structure for debugging. Developer Con...

@mayurthedev  As mentioned in the JavaDoc, it is throwing because of missing elements when instantiating the Sling Model - https://sling.apache.org/apidocs/sling10/org/apache/sling/models/factory/MissingElementsException.html   Add a try-catch block to catch the exception and get the missing element...

@mayurthedev Yes, you can get the page model json using the ModelFactory API like the following    @Reference private ModelFactory modelFactory; -------------------- // this gives you the page.model.json if the request is associated with the page you requesting modelFactory.exportModelForRequest(re...

@YuSheng  You only need the keys from the map (assetReferencesMap.getKeys()) and ignore the values, which will give you the asset paths  /content/dam/asset1.xls /content/dam/asset2.pdf /content/dam/asset3.PNG Next step is to publish the paths using the Replicator service  @Reference protected Repli...

@Veena_Karnik Other than the error in browser console, do you see any errors in the logs when loading the page or interacting with container?    Also, check if there is any custom code that could break the editor functionality?  

@RooRue There must be an error in the logs on why it is breaking.  It may be because of any of the following reasons:  Form component code or its internal dependencies (services) missing or not satisfied Missing content or misconfigured content or configsComponent code in dev is different than in pr...

Where was it failing?    You need something like the following to cover the line #40, which should give you more than 80% coverage except the exception block.  // BeforeEach method runs before running any test case, so you need to create page under non-content directory to test the negative scen...

Yes, @mcoh in template component, find the head section (mostly -> head.html) where you notice the following line of code or something similar  <title data-sly-test.pageTitle="${page.title}">${pageTitle}</title> replace it with  <sly data-sly-test.editOrDesign="${wcmmode.edit || wcmmode.design}"/> ...