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

[5.x] Global fields with Antlers enabled not parsing anymore #10001

Closed
o1y opened this issue May 5, 2024 · 0 comments · Fixed by #10003
Closed

[5.x] Global fields with Antlers enabled not parsing anymore #10001

o1y opened this issue May 5, 2024 · 0 comments · Fixed by #10003
Assignees
@JohnathonKoster
Labels
augmentation

Comments

@o1y
Copy link
Contributor

o1y commented May 5, 2024

Bug description

Global Fields are no longer being parsed as expected when Antlers is enabled. This could come from #9636, if I revert the commit parsing works as expected.

How to reproduce

  1. Add a Field to a Global Set (Bard, Text Field etc.)
  2. Enable "Allow Antlers"
  3. Add content, e.g. {{ homepage }} and put field variable to your template.

Logs

No response

Environment

v5.0.0-beta.3

Installation

Fresh statamic/statamic site via CLI

Antlers Parser

None

Additional details

No response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JohnathonKoster JohnathonKoster

Labels
augmentation
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[5.x] Ensures values are resolved when checking Antlers parsing settings JohnathonKoster/cms
3 participants
@jasonvarga @o1y @JohnathonKoster