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 storing global sets in the file system but global set variables in the database, it seems that saving a global set through the cp saves correctly the data to the database but also saves duplicated data in the flat files.
That data isn't actually the source of truth as modifying the yaml file directly and reloading the cp doesn't change the data, proving it's correctly being loaded from the database. However it would be nice if it still wasn't happening has I'd like to keep the yaml files in version control for consistency and use the git features, but editing the global through cp will trigger a git push and a deployment, which is the whole thing I was trying to avoid by having the global set variables in the database.
How to reproduce
Install the eloquent driver and set the globals as such:
Bug description
When storing global sets in the file system but global set variables in the database, it seems that saving a global set through the cp saves correctly the data to the database but also saves duplicated data in the flat files.
That data isn't actually the source of truth as modifying the yaml file directly and reloading the cp doesn't change the data, proving it's correctly being loaded from the database. However it would be nice if it still wasn't happening has I'd like to keep the yaml files in version control for consistency and use the git features, but editing the global through cp will trigger a git push and a deployment, which is the whole thing I was trying to avoid by having the global set variables in the database.
How to reproduce
Install the eloquent driver and set the globals as such:
Create a global, such as footer:
Add a field:
This correctly creates
content/globals/footer.yaml
:And
resources/blueprints/globals/footer.yaml
Now, modifying the content of the footer will correctly update the entry in the database:
But this will also update
content/globals/footer.yaml
:Logs
Environment
Additional details
No response
The text was updated successfully, but these errors were encountered: