Bug #94244

PageTypeSuffix Enhancer buggy

Added by Bernhard Eckl 4 months ago. Updated 3 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
-
Start date:
2021-05-31
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

If I use PageTypeSuffix enhancer the type parameter in an url is not always respected even if it is defined. This is why ext media_upload does not work again. I I remove the PageTypeSuffix enhancer the type parameter works without problems.

Example:

Works: https://www.oth-aw.de/studieren-und-leben/campusleben/marktplatz/biete-suche/mediaupload.html

Doesn’t work: https://www.oth-aw.de/studieren-und-leben/campusleben/marktplatz/biete-suche/?type=1386871773

On the root page it works:
https://www.oth-aw.de/?type=1386871773

Config:

PageTypeSuffix:
type: PageType
default: /
index: ''
map:
/: 0
...
mediaupload.html: 1386871773
mediadelete.html: 1386871774

If it is solved I would remove the urls in this issue.


Related issues

Related to TYPO3 Core - Bug #86835: Static route sitemap.xml is still not working on single-page treeNew2018-11-02

Actions
Related to TYPO3 Core - Bug #87104: PageTypeSuffix removes type parameter for non mapped type valuesClosed2018-12-07

Actions
#1

Updated by Bernhard Eckl 4 months ago

  • Related to Bug #86835: Static route sitemap.xml is still not working on single-page tree added
#2

Updated by Bernhard Eckl 4 months ago

  • Related to Bug #87104: PageTypeSuffix removes type parameter for non mapped type values added
#3

Updated by Riccardo De Contardi 4 months ago

  • Category set to Link Handling, Site Handling & Routing
#4

Updated by Annett Jähnichen 3 months ago

Seems still relevant in TYPO3 v9.5.27
Tested with TYPO3 9.5.27
PHP 7.4
and site config
routeEnhancers:
PageTypeSuffix:
type: PageType

what have I done?

Configured a PageType in TypoScript to use a different view and other settings. For example generate a xml view of a news page or prevent JavaScript and CSS files from being loaded on certain pages or use AjaxReuests.
Do not map the PageTyp in site config.

what did I expect?

A certain page https://example.org/foo/?type=1 would be rendered with the page config of typeNum = 1.

what happened?

The page is rendered with the configuration of default page setup. Looks different.

technical remarks

especially <f:link.page pageUid="{currentUid}" pageType="1"> an <f:uri.page pageUid="{currentUid}" pageType="1"> loaded only the page with default configuration. I guess f:link.action does it the some way.
https://example.org/?uid=x&type=1 would work, but that is not the output of the mentioned ViewHelper

Also available in: Atom PDF