I know it's been a while, but I did want to close this out. Turns out all three properties were related to the same nodes/pages so a single index did indeed work, like you have @DEBAL_DAS. This is what mine looks like: If you were deploying via package, this is the entry that would go in /jcr_root/_...

I know it's been some time, but I did want to follow up on this. Those SQL queries did indeed work, so thank you @lukasz-m. I also added rep:Restrictions. They don't line up with the allow/deny results so you have to manually sort them with the correct allow/deny. DM me if you want the entire packag...

Thank you. I found that post also but it's quite old so I didn't know if those methods were still valid.

Correct. But it really just boils down to searching multiple paths regardless of type. /content/mypages /content/dam/mypagespdfs

So you are talking about the Query Builder API search. I can confirm that works. You can just remove the type= and it will search all types, for example: fulltext=Management group.p.or=true group.1_path=/content/geometrixx/en/company/management group.2_path=/content/geometrixx/en/company/bod But is ...

I need to create a search page that queries multiple paths. For example, /content/mypages and the corresponding PDFs in assets (/content/dam/mypages). Using Quick Search, it looks like Search Root only accepts one path. Is there a way to accomplish this using Quick Search or other method?

I also see that when you create a new content fragment in SP10, Simple Fragment does not appear on the model selection screen. In service pack 11, 12, 13, and 14 it does appear and indicates it is deprecated (screen shot below). I wish to hide that as an option. How is this accomplished in SP10? It ...

I think you would have to ask your sales rep or licensing folks. I happened to have 6.3 sitting around. I believe you can obtain versions back to 6.0 through Adobe's Solution Partner Program, if you are part of that. Was there something specific you were looking for? Maybe I can pull it for you. Or ...

So I had opened a support ticket prior to this post and didn't get a satisfactory answer, which is why I posted here. However, eventually I got this response: "If you have one index for all properties it will index all nodes that contain one of the properties, which can make the query less efficient...

I need to create a search index to address the traversing errors in error.log. Specifically:.../* xpath: /jcr:root/content/solutions//*[(jcr:content/@page-category = 'category:news')] */, path=/content/solutions//*, property=[jcr:content/page-category=[category:news]]); consider creating an index or...