Project

General

Profile

Actions

Bug #46676

closed

TYPO3 TypeNum misbehaviour for ShortCut-Pages

Added by Gabriel Kaufmann / Typoworx NewMedia over 11 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2013-03-26
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.6
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

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).


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #46841: alternative page does not care about page typeClosed2013-04-01

Actions
Actions #1

Updated by Ernesto Baschny about 11 years ago

  • Target version deleted (2194)
Actions #2

Updated by Mathias Schreiber over 9 years ago

  • Status changed from New to Closed
  • Is Regression set to No

fixed on master

Actions

Also available in: Atom PDF