Issue Bug Closed

#46676TYPO3 TypeNum misbehaviour for ShortCut-Pages

Gabriel Kaufmann TYPOworx GmbH | NewMedia 03/26/13, 10:33 updated 01/23/15, 16:15

Description

I set-up an additional Page-Type (one for XML-Sitemap and one for RSS serving).
The Types itself work fine!

Now we wanted to set-up our Rootpage (Page ID=1) to fetch those types:

www.my-typo3-site.com/?id=1&type=1234

TYPO3 throws an Exception, that the given TypeNum isn’t setup. The Rootpage is configured as ShortCut to it’s first sub-page – this seems to be the problem!

Any other “normal” Page without ShortCut-Mode works fine with the TypeNum. So there seems to be a bug in TYPO3 that causes this misbehaviour.

What I would expect:
———————————
TYPO3 should serve the correctly configured Page-Type regardless it’s Type “0” or any other and of course regardless the called Page is a ShortCut or not.

I think the best behaviour would be to serve the configured Page-Type without doing the redirect. The second choice would be to redirect to the ShortCut given by respecting the GET-Params (incl. “type” with the TypeNum).

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.