Segment lookup failing when Backend User logged in about typo3-realurl HOT 6 CLOSED

Will try to debug more details

from typo3-realurl.

The problem lies in $pagesEnableFields and $disallowedDoktypes.
I locally changed the page doktype to shortcut so this is 'bypassed'.

The pagesEnableFields adds the "(pages.endtime=0 OR pages.endtime>1457177640) AND (pages.fe_group='' OR pages.fe_group IS NULL OR pages.fe_group='0' OR FIND_IN_SET('0',pages.fe_group))" lookup.

The user object is not yet initiated in this stage and cause the user is logged in, the page segment is not read as intended. When you are not logged in the backend, it just reads the cache (which does work).

I will create a PR to 'fix this'. You can review it then!

from typo3-realurl.

Spacers are not supposed to have subpages. Sorry, this will not be changed.

from typo3-realurl.

Hi Dmitry, where is this documented?

I figured this would lead to some discussion that's why i spliced both bugfixes in different PR's. You can decline the doktype PR then :-)

from typo3-realurl.

1. https://www.google.com/search?q=typo3+spacer+page+type You will find multiple questions and answers concluding that it is not really possible to have subpages for spacers.
2. https://docs.typo3.org/typo3cms/TyposcriptReference/MenuObjects/CommonItemStates/Index.html, see SPC menu type and its description: "Spacers are pages of the doktype “Spacer”. These are not viewable pages but “placeholders” which can be used to divide menu items.". Just placeholders, not viewable. They are not really pages!

They are only visual separators. If you need subpages, use some other page type: folder, page-not-in-menu, etc.

from typo3-realurl.

Fine by me! =)
Thanks for the merge!

from typo3-realurl.