david g.
@kwin the other question is - do we just wait till we drop 6.4.x support entirely, and use R7 + `-` support? (6.5.0+ supports this right?) .. keep in mind...
@jyothishey hi - this is an enhancement as reports feature was not designed to handle pulling complex structures like this. @pahupe was looking at this as something to possibly work...
Can you set loggin to `DEBUG` on `com.adobe.acs.commons.errorpagehandler.impl` and reproduce the erroring condition? I would double-check all your `errorPages` properties - it sounds like one isn't updated (or maybe not...
@AnupamaKarru - few observations 1. I assume your `errorPages` property is set on all your cq:Page trees properly. Your OSGi only lists 1 mapping in `paths`, so i assume other...
@samarthP24 the Vulnerability was resolved in https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/2933 and released in 5.3.4 .. the others still need work :)
Interesting use case... what would your expectation be if: 1. The tag spaces had a mix of numbers and strings? For example, how would you expect the following to be...
EDIT: IDK why i thought you were on AEM CS -- if you are not, then you can include ACS Tools using the maven coordinates at: https://search.maven.org/search?q=acs-aem-tools You'll need bundle...
Fixed in 5.3.0
Fixed via https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/2807