[TASK] Mention tree.level starting at 1 not 0

[garvinhicking]

As mentioned in https://forge.typo3.org/issues/96385 the former treeLevel started at 0 but with the change to tree.level this was changed to be based at 1 for root level.

The docs need to reflect this fact.

[kitzberger]

@garvinhicking, that's only half the truth though. IMHO it's important to mention the fact the pages.is_siteroot is not having any effect on the backend tree level as it used to have.

[garvinhicking]

@kitzberger Thanks... I must admit I don't really understand how to document this, do you have something in mind, how we should address it? (Sadly I also didn't really understand the feedback in the Forge Ticket - I'm not working much in that area so I'm unsure how it is used, not my area of expertise - I thought the treeLevel vs. tree.level thing was "straight enough")

[linawolf]

I would suggest we merge the part about the root level. The fact that pages.is_siteroot does not exist anymore in conditions seems to be unrelated?

[kitzberger]

Maybe add something like this to that hint:

Unlike the frontend TypoScript condition tree.level this backend tree level is not affected by pages.is_siteroot . This means for nested sites it cannot be used to match "site roots" or in general any n-th levels of page tree depths. It's the absolute depth of the entire page tree, starting with 1.

[garvinhicking]

Great, thanks for adding the hint, this sounds good to me, merging now!