We are trying to turn on the AEM link checker and I am seeing some strange behavior. If I create a new page in Sites and make any change to it e.g. add a new component or edit the properties dialog then the page itself will show up in the link checker e.g.http://localhost:4502/mnt/overlay/wcm/core/content/sites/properties.html?item=%2Fcontent%foo%2Fen%2Fthe-pageor http://localhost:4502/editor.html/content/foo/en/link-checking.htmlHowever any links I add to the page are never shown in the link ch...

I'd like to expose our content fragments models as JSON for consumption in a mobile app. However I'd rather not have to include them on a sites page first. Is there a way OOTB to get a content fragment using .model.json?

I'm struggling to override the default out of the box json servlet. I want to create my own for a specific resource type and when a specific selector is used. However it seems to keep calling the default. To be clear I want to keep the default servlet in all other scenarios. My annotations for the custom servlet are:@SlingServlet(methods = {HttpConstants.METHOD_GET}, metatype = true, resourceTypes = {"wtr/components/structure/offertypepage"}, selectors = {"mapper"}, extensions = {"json"})and if ...

We are on 6.2 SP-1 and when I create a new launch the blue toggle button to disable including sub-pages can't be clicked, it just stays on so we always have to include sub-pages. Is this a bug or can you not always disable including subpages?

We need to get access to the "csp" value that is part of the cq tag written out on the author for a parsys component. e.g.{ "path": "/content/test/jcr:content/header/extendednavigationca/parsys/*", "slingPath": "/content/test/jcr:content/header/extendednavigationca/parsys/*.html", "type": "wcm/foundation/components/responsivegrid/new", "csp": "testpage|page/header|responsivegrid/extendednavigationcardwrapper|componentwrapper|responsivegrid/parsys|responsivegrid/new|newpar", "editConfig": { "acti...

We have a content package as part of our standard deployment e.g following the maven archtype. In our filter we include the DAM as we setup some folders at the base of the DAM and also some root pages for our site in sites. This seems to be causing a huge snapshot to be taken prior to the install and also means the install takes a long time. What is the best practice for handling this to avoid these large snapshots? Also how can we housekeep the package snapshots other than manually deleting?The...