Project

General

Profile

Actions

Bug #79542

closed

Fluid command <f: switch> very slow

Added by Thomas Hohn about 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Category:
Fluid
Target version:
Start date:
2017-01-30
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
8
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

There seems to be a problem with the fluid <f: switch> - performance is horrible.
Try to go into the "Log" module in the backend - very sloooow


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #79546: f:switch should be avoided (causes uncompilable templates)Closed2017-01-30

Actions
Actions #1

Updated by Gerrit Code Review about 7 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/51464

Actions #2

Updated by Anja Leichsenring about 7 years ago

just for the records: slow is NOT broken. Please adjust the issue title accordingly. Thank you.

Actions #3

Updated by Claus Due about 7 years ago

The ViewHelper isn't broken as such - but it does intentionally disable template compiling. The reason:

  • The TYPO3 CMS specific version of `f:switch` was initially removed in favor of the one that ships with Fluid itself (in an attempt to limit the number of overrides TYPO3 provides)
  • A backwards compatibility issue was determined to be too severe to simply drop the ViewHelper (arguments are different on Fluid's `f:switch`).
  • The ViewHelper was reinstated, but was not marked as deprecated.

Properly deprecating the ViewHelper would be the appropriate solution to that problem. But solving this problem is possible by simply avoiding `f:switch` in the template, which is easily done.

Actions #4

Updated by Georg Ringer about 7 years ago

  • Subject changed from Fluid command <f: switch> broken to Fluid command <f: switch> very slow
Actions #5

Updated by Anonymous about 7 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #6

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF