Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] Fractor change '>' sign with '>' #259

Open
Oktopuce opened this issue Dec 3, 2024 · 1 comment
Open

[BUG] Fractor change '>' sign with '>' #259

Oktopuce opened this issue Dec 3, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Oktopuce
Copy link

Oktopuce commented Dec 3, 2024 •
edited
Loading

Minimal PHP Code Causing Issue

In the code below, you have a ViewHelper {f:uri.page(pageUid: 1, absolute: 'true') -> f:format.htmlentities()} wich will be transformed in {f:uri.page(pageUid: 1, absolute: 'true') -'&gt; f:format.htmlentities()} I guess because it's between <link> tag.

<?xml version="1.0" encoding="utf-8"?>
<html xmlns:content="http://purl.org/rss/1.0/modules/content/"
      xmlns:atom="http://www.w3.org/2005/Atom"
      xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers"
      data-namespace-typo3-fluid="true">
		<channel>
			<link>{f:uri.page(pageUid: 1, absolute: 'true') -> f:format.htmlentities()}</link>
		</channel>
	</rss>
</html>

Applied rules

No fractor specific rule required.

Expected Behaviour

The ViewHelper {f:uri.page(pageUid: 1, absolute: 'true') -> f:format.htmlentities()} musn't be transformed like this {f:uri.page(pageUid: 1, absolute: 'true') -'&gt; f:format.htmlentities()}, it should remain like it was before appliying fractor.

Package Version

0.4.2

PHP Version

8.2.0

TYPO3 Version

12.4

Notes

No response
@simonschaufi simonschaufi added the bug Something isn't working label Dec 3, 2024
@andreaswolf
Copy link
Owner

True, but AFAIK what we do here in TYPO3 is not really valid XML/HTML, thus this might be hard to change. First step would be to identify which component exactly messes stuff up here – my guess is that this already happens when the XML is read, so it's probably just a missing libxml parameter. Should be easy to spot with a simple test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@andreaswolf @simonschaufi @Oktopuce