You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When having a grid fieldtype that only shows on some condition (e.g. a toggle set to true) and having set Always save to false, the Stache behaves weird after saving an entry when it comes to default values.
The default value is not shown after editing and saving an entry and setting the toggle to true again, even though the grid field hasn't been saved to the file. I would expect the default value to show once the field is shown again.
Create an entry and see the field showing/hiding depending on the toggle state. Now save the entry with the grid being hidden. Reload the tab and set the toggle to true. You get an empty grid, instead of the prepopulated one. I would expect it to have the default values.
Once the stache has been cleared, everything works again as expected.
Bug description
Screen.Recording.2025-01-14.at.15.48.37.mov
When having a grid fieldtype that only shows on some condition (e.g. a toggle set to true) and having set
Always save
to false, the Stache behaves weird after saving an entry when it comes to default values.The default value is not shown after editing and saving an entry and setting the toggle to
true
again, even though the grid field hasn't been saved to the file. I would expect the default value to show once the field is shown again.How to reproduce
Create a blueprint with the following example:
Create an entry and see the field showing/hiding depending on the toggle state. Now save the entry with the grid being hidden. Reload the tab and set the toggle to true. You get an empty grid, instead of the prepopulated one. I would expect it to have the default values.
Once the stache has been cleared, everything works again as expected.
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: