-
-
Notifications
You must be signed in to change notification settings - Fork 543
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
Antlers tag is rendered in bard code block #3631
Comments
If you |
Are you sure that works with a single curly brace on a non-local environment? If it does, that's new to me, never seen Antlers act like that before. |
See https://nckrtl.com/articles/speedup-page-loads-when-working-with-statamic-s-seo-pro-locally I want that snippet to be displayed in the code block in bard like:
But that actually renders the seo:pro tag in the frontend which I don't want, as I have it in a code block for demonstration purposes. So to not render the tag in the code block I used a single { instead of {{. So it's correct that that's not rendering. |
Can you post the output of |
I have the same with PHP 7.4:
Edit: This is what my code looks like when printing the snippet
|
How are you outputting the blog post contents? Does that field have |
Not sure if I follow. Do I need to set that in de markdown file? Currently its looking like:
I tried this:
I don't see an option in the bard settings of the blue print to disable antlers or anything. Neither in the specific code set. Edit: also prepending the seo:pro tag with a @ like |
I didn't realize you said bard originally. That should be enough for us to go on. Thanks. |
I was writing something about SEO Pro on my blog and I noticed the
{{seo_pro:meta}}
tag gets rendered on the page when I have it in a code block in bard content. Other antlers tags are not being rendered, as expected.Also a preceding @ doesn't work. Example bard content in a code block:
Expected behaviour would be to not render any tag when its in a code block. Is there any way to prevent this from happening?
Thanks, Nick
The text was updated successfully, but these errors were encountered: