Project

General

Profile

Actions
Copy link

Bug #91193

closed

Can't get access to GET-parameter in custom TypoScript condition when using routeEnhancers

Added by Stephan grass over 4 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2020-04-25
Due date:
% Done:

0%

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

Description

Hi.
I build a custom TypoScript condition. In matchCondition() I try to read and use the GET-parameter. It will work, until using a routeEnhancer. Only if the parameters are "visible" in the url, the parameters are "visible" in the custom condition class.
I am trying $GLOBALS['_GET'], $_GET and GeneralUtility::_GP ...

Why? A bug?

Thanks
Stephan

Actions
Copy link
 #1

Updated by Stephan grass over 4 years ago

  • Subject changed from Can't get access to GET-parameter in custom TypoScript condition and using routeEnhancers to Can't get access to GET-parameter in custom TypoScript condition when using routeEnhancers
Actions
Copy link
 #2

Updated by Georg Ringer over 4 years ago

  • Status changed from New to Rejected

this is not a bug. use code like this

    [traverse(request.getQueryParams(), 'tx_news_pi1/news') > 0]
        page.10.marks.content < lib.news_detail
    [else]
        page.10.marks.content < lib.news_list
    [end]
Actions
Copy link
 #3

Updated by Stephan grass over 4 years ago

  • Priority changed from Should have to Must have

Georg Ringer wrote:

this is not a bug. use code like this

[...]

I don't want only check the GET parameters. In my custom condition I have to use the GET parameter for further operations.
So, without routeEnhancer I have access to the GET parameters, with plain text urls via routeEnhancer not.

Actions
Copy link

Also available in: Atom PDF