-
-
Notifications
You must be signed in to change notification settings - Fork 518
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
Bard Field with antlers parsing outputs additional Paragraph Tags #10825
Comments
Hey @duncanmcclean thanks for looking into it. I also stripped down the repository now and the issue still occurs. Strip Down Commit: Jubeki/statamic-bug-antlers-and-bard@1324105 I also have deploy the same repository, without any changes (except enabling production mode and disabling debug) to https://statamic.kiekbjul.de Where I also can see the same issue (Safari and Chrome): |
The problem lies within using |
Oh, I see it now. Thanks! Out of curiosity, why are you using Antlers inside a Bard's content, instead of using a Bard set? |
I must say, I didn't really think about using a set for this, because I only thought about outputting the globals value like with antlers, and that was the simplest thing I could think of in that moment. One of the main reasons may be: That I use the contact details in different contexts:
So they are different Bard Fields and I would need to configure them accordingly. (I will take down statamic.kiekbjul.de to prevent miss use) |
Bug description
If you use a globals with a Bard Field. And try to output it inside another Bard Field you get one additional paragraph tag before and after the globals output.
I would expect no additional tags before and after.
How to reproduce
https://github.com/Jubeki/statamic-bug-antlers-and-bard
test@example.com
password
Steps for setting up:
contact
, Bard Field:details
){{ contact:details }}
Changing the
Remove Empty Nodes
Option fromDon't remove empty nodes
toRemove empty nodes at start and end
does not change the behaviour.Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered: