TYPO3 Core

Thanks for pointing this out.

Analyzing the problem¶

rootPidList¶

You are right, it is plugin.tx_indexed_search.settings.rootPidList, not plugin.tx_indexed_search.search.rootPidList

I think one misunderstanding is, you can't just use any page for rootPidList, it must be the root page (meaning the page with the root template). So if a page 955 is indexed and the page tree looks like this:

3
| > 14
    | > 79
         | > 54044

and page id 3 is our root page,

The page 54044 will always be indexed like this:

rl0 | rl1 | rl2 | page_id
----|-----|-----|
 3  | 14  | 79  | 54044  

You will not get any results, with rootPidList being a list of or one non-root page(s). As you found out, he will just check for the field rl0.

Now the docs do point this out (somewhat): "Notice that by "root-page" we mean a website root defined by a TypoScript Template! If you just want to search in branches of your site, use the possibility of searching in levels."

but I agree, they could be clearer. Also the statement "If you just want to search in branches of your site, use the possibility of searching in levels" is very vague and only adds to the frustration. At least a link at that point would be helpful.

settings.defaultOptions.sections¶

Actually, your method:

plugin.tx_indexedsearch.settings.defaultOptions.sections = rl1_xxx

does work, but only if the page you are using for rl1_xxx is a direct subpage of the root page. If it's a sub-subpage you must use rl2_xxx and if it is further down in the page tree, you are out of luck.

Disclaimer: I'm just guessing here, but it makes sense and tests confirm.

What to do¶

You might consider submitting a patch, even if it's just for the documentation clarification. You already proceeded so far. Please see the Contribution Guide for more information. Don't worry, your patch will be reviewed before it is merged.