Project

General

Profile

Actions

Bug #87817

closed

PageLinkBuilder fails adding pagetype parameter, if routeEnhancers for PageTypeSuffix is defined

Added by Philipp Seiler about 5 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
-
Start date:
2019-03-01
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
routing,enhancer,sitemap,seo
Complexity:
Is Regression:
Sprint Focus:

Description

  • Define a RouteEnhancer for a certain page type:
    routeEnhancers:
      PageTypeSuffix:
        type: PageType
        default: ''
        map:
          foo: 1234
  • Call some method that uses TYPO3\CMS\Frontend\Typolink\PageLinkBuilder, including a typeNum as parameter.
    <f:uri.page pageType="{type}" additionalParams="{sitemap: sitemap.key, page: sitemap.page}" absolute="true" noCacheHash="false" />
    $uri = $uriBuilder->setTargetPageUid($pageUid)->setTargetPageType($pageType)->build();
  • The typeNum used in the example code above should NOT be registered in the RouteEnhancers. E.g. '5678' to fit the defined RouteEnhancer above.
  • TYPO3 then tries to use \TYPO3\CMS\Core\Routing\Enhancer\PageTypeDecorator to add the defined page type in the RouteEnhancers to the URL, although for the selected typeNum ('5678') there is no RouteEnhancer defined.
  • This leads to method decorateForGeneration() removing the typeNum:
    $deflatedParameters = $existingRoute->getOption('deflatedParameters') ?? $parameters;
    if (isset($deflatedParameters['type'])) {
        unset($deflatedParameters['type']);
        $existingRoute->setOption(
            'deflatedParameters',
            $deflatedParameters
        );
    }
  • Results in a link without typeNum added to it.

I stumbled across this, when defining a RouteEnhancer for a typeNum I used in a plugin. I also had the TYPO3 seo-extension installed, which defines the typeNum 1533906435 for getting the sitemaps. However the sitmap extension didn't create valid URLs with typeNums, and were therefore useless.

A quick fix is, to also add the typeNum defined by the seo-extension to the RouteEnhancers:

routeEnhancers:
  PageTypeSuffix:
    type: PageType
    default: ''
    map:
      foo: 1234
      sitemap: 1533906435


Related issues 6 (1 open5 closed)

Related to TYPO3 Core - Bug #87087: StaticRouteResolver ignores additional parametersClosed2018-12-05

Actions
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 #88836: page type not respected under some circumstancesClosed2019-07-24

Actions
Related to TYPO3 Core - Bug #87087: StaticRouteResolver ignores additional parametersClosed2018-12-05

Actions
Related to TYPO3 Core - Bug #87016: Seo sitemap does not note routeEnhancer on extensionsClosed2018-11-27

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

Actions
Actions

Also available in: Atom PDF