-
-
Notifications
You must be signed in to change notification settings - Fork 541
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
Augmentation not working on markdown fields in navigation #11223
Comments
Thank you for the quick response! The behavior I observed has become even less comprehensible to me after the weekend: While my attempts with the markdown modifier were unsuccessful on localhost last week, this morning the text suddenly started being correctly formatted. However, this is only happening on the localhost and not on the server where the site will eventually go live. The data in the field is identical, and all local changes have been deployed to the server. I dumped the variables in both environments: Localhost {{ depth_1_options }}:
{{ depth_1_options:header_section_text }}:
Server {{ depth_1_options }}:
{{ depth_1_options:header_section_text }}:
|
Just to confirm: both local & your server are running exactly the same code, with the same versions of dependencies? Can you provide the output of |
Bug description
A Markdown field in the navigation is ignored by the augmentation process and passed through to the frontend in Markdown syntax. Even the Markdown modifier does not resolve this issue.
How to reproduce
Place a markdown field within a navigation blueprint. In my case it's part of a group fieldtype.
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: