I was trying to search all instances of "granite/comments/components/collection" this included in our content but I don't see any results when I used XPath query through Crx/de. It shows the result of instances that are under libs. I even tried using crxde home search.
But when I use /libs/cq/search/content/querydebug.html I am able to retrieve the results successfully as shown below. This happens only in 6.3.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi,
We had tried entering the search text as "foundation/components/redirect" in both Home search text box and XPath search text box. We were able to replicate the same issue. That is, were able to fetch results in query debug tool (/libs/cq/search/content/querydebug.html), but not in Home search and XPath search.
However, we've observed that when we are entering the search text that has slash in it and trying to generate query by clicking the generate query button, it is returning invalid query.
Work around for this issue:
Try copy pasting the XPath query that is generated in query debug tool (/libs/cq/search/content/querydebug.html) in XPath query box and execute it as shown in the screenshots below. You'll now be able to see the correct results.
We hope this helps!
Regards,
Views
Replies
Total Likes
The reason is because Query Builder is a better way to search then XPATH. Use Query Builder or JCR SQL/2 over XPATH.
Views
Replies
Total Likes
Hi,
We had tried entering the search text as "foundation/components/redirect" in both Home search text box and XPath search text box. We were able to replicate the same issue. That is, were able to fetch results in query debug tool (/libs/cq/search/content/querydebug.html), but not in Home search and XPath search.
However, we've observed that when we are entering the search text that has slash in it and trying to generate query by clicking the generate query button, it is returning invalid query.
Work around for this issue:
Try copy pasting the XPath query that is generated in query debug tool (/libs/cq/search/content/querydebug.html) in XPath query box and execute it as shown in the screenshots below. You'll now be able to see the correct results.
We hope this helps!
Regards,
Views
Replies
Total Likes
This issue occurs in AEM 6.3 and crxde home/query search works fine in AEM 6.1. The workaround provided by TechAspect solution works fine but it is just workaround. It doesn't solve the issue.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies