That should not be the case. I hope you are also using the lower case search values in the query along with the lower case function ?

You can use the lower-case function to make it case insensitive- path=/content/x/y/ztype=nt:basegroup.1_property=fn:lower-case(headingText)group.1_property.value=%abc%group.1_property.operation=likegroup.2_property=fn:lower-case(blocktitle)group.2_property.value=%abc%group.2_property.operation=likeg...

If that is the case then you can write a custom action handler for the custom menu item as I had mentioned in my last post instead of using the activation action and listening on activate events. 

You can fire the following SQL2 query to get the list of all active pages in AEM. select * from [cq:PageContent] AS s where s.[cq:lastReplicated] IS NOT NULL AND ISDESCENDANTNODE(s,[/content])

In that case you can directly query the nt:base node like below- type=nt:base1_property=sling:resourceType1_property.value=geometrixx/components/titlepath=/content/geometrixxBut in the result now you will get full node paths instead of the page paths. 

Here is an example query which queries the sling:resourceType property of a component and returns the path of the page in the result- type=cq:Page1_property=jcr:content/par/title/sling:resourceType1_property.value=geometrixx/components/titlepath=/content/geometrixxhttp://localhost:4502/bin/querybuil...

I guess the requirement means that the users should be able to use the Microsoft Word editor for editing the word documents which lives in the CMS. The operation of creating new word document and editing a new word document should be possible from within the editor. They would not like to login into...

You can achieve this by creating a new user and give permissions to that user for only that particular site which you are activating. In the replication agent configuration set the Agent User Id field to the new user name.  The other two replication agents can have different user ids which will not ...

Have you checked the rights of the user which owns the AEM process as well ?

Yes the query is definitely going to be slower as you are doing inner joins with nested child nodes. As suggested in the first thread it would have been better if you can just process the returned paths returned by the simple query programmatically to get the page paths instead of firing query with ...