-
-
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
Navigations can't access group data when it has a condition #10055
Comments
@robdekort Do you have any conditions anywhere? That is what seems to be messing mine up, but only for groups. |
What do you mean with groups? Even without conditions the data doesn't seem available on root items. Only on children (in my case). |
Group fieldtypes (and possibly other fields that produce the same data structure, but I didn't test them) |
Gotcha! |
Mine might be a separate issue. We'll see :-) |
It seems like both issues are related 😄 Reverting the changes made in #9636 seem to fix both issues. |
Ah good. Jason suggested I create a separate one so it doesn’t get lost. I’ll do that tomorrow. |
Bug description
When you create a group and give it a condition of show when, you can no longer access the data if a child precedes it.
Copy the data below and try re-ordering them inside your navigation to see what I mean.
How to reproduce
inside antlers:
content/navigation/test.yaml
content/trees/navigation/default/test.yaml
resources/blueprints/navigation/test.yaml
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: