Hi,
I am on 6.5.12 version of AEM, noticed that using tagid as A, results in unclosed resource resolver and using B works fine . But using B means i will have to add the like operation to it. Tried this using Querybuilder OOTB
Question-
1. Is there an alternate way to achieve subtags retrieval if parent tag is chosen?
2. I could think of "like" operator but Is "like" operation ok for performance reasons?- option C
3. Does anyone else notice the unclosed resolver warnings using "tagid"?
A.
path=/content
group.1_tagid.property=cq:tags
group.1_tagid=properties:style/color
group.2_tagid.property=cq:tags
group.2_tagid=properties:style/monochrome
orderby=path
group.p.or=false
p.offset=0
p.limit=-1
B.
path=/content
group.1_property=jcr:content/@cq:tags
group.1_property.value=properties:style/color
group.2_property=jcr:content/@cq:tags
group.2_property.value=properties:style/monochrome
orderby=path
group.p.or=true
p.offset=0
p.limit=-1
C.
path=/content
group.1_property=jcr:content/@cq:tags
group.1_property.value=properties:style/color%
group.1_property.operation=like
group.2_property=jcr:content/@cq:tags
group.2_property.operation=like
group.2_property.value=properties:style/monochrome%
orderby=path
group.p.or=true
p.offset=0
p.limit=-1
Solved! Go to Solution.
Views
Replies
Total Likes
Anyone facing the issue ,received confirmation from adobe .. this is a bug and that has been existing with tagid and the KB still holds good since the issue exists since I guess 2017
ignoring the info messages is the suggestion.
Anyone please ?
Anyone knows about this ?
Anyone facing the issue ,received confirmation from adobe .. this is a bug and that has been existing with tagid and the KB still holds good since the issue exists since I guess 2017
ignoring the info messages is the suggestion.
Views
Likes
Replies
Views
Likes
Replies