-
-
Notifications
You must be signed in to change notification settings - Fork 224
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.
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
Augmenting wrapped content elements not working as expected #2988
Comments
In case anyone else finds this issue: The original PR got denied some years ago and we have been using an augmenter modification like this ever since:
|
Hi ;) Thanks for this issue, i never though of this usecase ^^ The fact that there are Once we have reworked the content element wrapping, you should not face this problem any longer. But i also have to admit that this will still likely take some time until it is ready (if it ever will be). |
The script tag is gone now with #3770 |
I already attempted a fix 1.5 years ago: #2281 but it got rejected. I keep running into this issue while developing modular Neos components.
The issue:
When passing wrapped content elements to a fusion renderer via @props, a script tag gets added when evaluating:
This leads to the xPath query in HtmlAugmenter.php not detecting a root element since the html is of structure
<div></div><script></script>
. It will break functionality for the Neos.Fusion:Augmenter since it will wrap the actual root element one more time.More specific: It is not possible to use the Neos.Fusion:Augmenter to augment Neos.Neos:ContentCollection passed via props Context to a Neos.Fusion:Renderer because instead of augmenting the attributes on the ContentCollection div, the HtmlAugmenter can't detect a single root element and now wraps the ContentCollection div into another div.
Neos 5.2
Neos UI 5.2
The text was updated successfully, but these errors were encountered: