Project

General

Profile

Actions

Bug #75299

closed

Behaviour of escapeChildren for self closing ViewHelpers

Added by Timo Hund about 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Fluid
Target version:
-
Start date:
2016-03-29
Due date:
% Done:

0%

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

Description

Hi,

in an Extension i have the problem that the whole content is escaped. As mentioned in the release notes of 8.0 the property escapeChildren could be changed if needed. But for me when is change this in the first view helper in the template that is self closing it effects als nodes, so it seems that "escapeChildren" also effects nodes after self closing node.

Is this intended or a bug?

<ext:viewhelper />

<ext:nextviewhelper></ext:nextviewhelper>

In this case escapeChildren would also be set in the scope of ext:nextviewhelper

Actions #1

Updated by Claus Due about 8 years ago

Please report on https://github.com/TYPO3Fluid/Fluid and reference this issue so we can investigate. I suspect the escaping isn't reset when there is no closing tag because the resetting only happens when processing closing tags and should also happen when detecting a self-closing tag.

You may be able to work around the issue for now by switching to inline syntax instead of tags.

Actions #2

Updated by Helmut Hummel about 8 years ago

  • Status changed from New to Needs Feedback

There is an esacapeChildren and an escapeOutput property.

Which one of those did you set to false?

From what class do you exactly inherit?

How exactly does your template code look like?

Can you provide the code for the view helpers to reproduce?

Actions #3

Updated by Benni Mack almost 8 years ago

Can you recheck in master? Should be fixed with master and fluid standalone 1.0.7

Actions #4

Updated by Claus Due almost 8 years ago

Fixed in Fluid 1.0.7 via https://github.com/TYPO3Fluid/Fluid/commit/70314b168d14fc38315e554b82238dd966744377 (with apologies for the commit message, that particular PR was merged a bit outside our normal rules and something went wrong)

Actions #5

Updated by Claus Due almost 8 years ago

  • Status changed from Needs Feedback to Resolved
Actions #6

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF