Project

General

Profile

Actions

Feature #90782

closed

Defect of f:widget.uri and f:widget.link

Added by Bill Dagou about 4 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Fluid
Target version:
-
Start date:
2020-03-18
Due date:
% Done:

0%

Estimated time:
PHP Version:
7.2
Tags:
Complexity:
Sprint Focus:

Description

The case is, I have a controller with list action at the first place

\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    'Dagou.Payment',
    'Pi1',
    [
        'Payment' => 'list, create, save, pay, process',
    ],
    [
        'Payment' => 'list, create, save, pay, process',
    ]
);

This action is using <f:widget.paginate> for pagination, and I have set the configuration.addQueryStringMethod to GET in the template.

<f:widget.paginate objects="{payments}" as="paginatedPayments" configuration="{addQueryStringMethod: 'GET'}">
    ...
</f:widget.paginate>

However, when I visit the web page, as the tx_payment_pi1[action] and tx_payment_pi1[controller] is missing in the URL, I can only get the pagination links like http://dagou.site/payment?tx_payment_pi1[@widget_0][page]=2&cHash=.... So, my routeEnhancers will never work for the pagination, and I can not find a way to set tx_payment_pi1[action] and tx_payment_pi1[controller] either.

So, my suggestion is, is it possible to provide the possibility to set the action and controller to make the routeEnhancers work, or maybe even extensionName and pluginName for some cases I could not foreseen. I noticed there is a widgetContext in AbstractWidgetViewHelper, but seems it never work through the child VHs.

Thank you!

Actions #1

Updated by Benni Mack over 2 years ago

  • Status changed from New to Rejected

Sorry, we removed widgets in TYPO3 v11 as they have some bad cross-cutting concerns.

Actions

Also available in: Atom PDF