Project

General

Profile

Actions

Bug #89641

closed

Routing configuration with 3rd party url segments

Added by Roman Büchler about 5 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Caching
Target version:
-
Start date:
2019-11-11
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
pending-close
Complexity:
Is Regression:
Sprint Focus:

Description

An extension configures a speaking url segement as following:

routeEnhancers:
  JobvacPlugin:
    type: Extbase
    limitToPages:
      - 119
    extension: Jobvac
    plugin: Joblist
    routes:
      -
        routePath: '/{job_title}'
        _controller: 'Job::show'
        _arguments:
          job_title: job
    defaultController: 'Jobvac:joblist'
    aspects:
      job_title:
        type: PersistedAliasMapper
        tableName: tx_jobvac_domain_model_job
        routeFieldName: slug

In the global configurations the following is present:

[FE][cacheHash][excludedParameters] = L,pk_campaign,pk_kwd,utm_source,...

Calling the url

...{page}/{slug}

works fine where calling

...{page}/{slug}?utm_source=test

causes a runtime exception:

(1/1) #1544172838 RuntimeException

Error handler could not fetch error page "/pages/startpage", reason: Couldn't get URL: /pages/startpage

Without the routing configuration it works fine.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #86895: routeEnhancer not working correct for paginate widgetClosed2018-11-09

Actions
Actions #1

Updated by Susanne Moog almost 5 years ago

  • Sprint Focus set to On Location Sprint
Actions #2

Updated by Oliver Hader almost 5 years ago

Side note: exception 1544172838 is caused by internal page request for errorHandling

Actions #3

Updated by Oliver Hader almost 5 years ago

  • Status changed from New to Needs Feedback
  • Tags set to pending-close
  • Sprint Focus deleted (On Location Sprint)

cHash handling probably has been fixed with issue #86895 on Git 9.5 branch (I could not reproduce with and without that change using your ?utm_source=abc example being configured in excluded parameters as mentioned)

Error message Couldn't get URL: /pages/startpage stems from sending an internal HTTP request to resolve 404 page. Could you please try to temporary disable 404 error handling just to check whether there's still a misbehavior in route resolving and cHash or whether it is related to error handling? Thanks in advance for your feedback!

Actions #4

Updated by Oliver Hader almost 5 years ago

  • Related to Bug #86895: routeEnhancer not working correct for paginate widget added
Actions #5

Updated by Oliver Hader about 4 years ago

  • Status changed from Needs Feedback to Closed

Seems to be fixed, closing issue.

Actions

Also available in: Atom PDF