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.

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

[Cms] $page->update() also for field-values that are not in blueprint #603

Closed
distantnative opened this issue Jul 9, 2018 · 3 comments
Closed
Labels
type: bug 🐛 Is a bug; fixes a bug
Milestone

Comments

@distantnative
Copy link
Member

distantnative commented Jul 9, 2018

$page->update() etc. should be able to write values to the content file no matter whether the field is defined in the blueprint or not. Kirby\Cms\Form::for() currently prevents that since we most times will fall back to a default blueprint.

@distantnative distantnative added the type: bug 🐛 Is a bug; fixes a bug label Jul 9, 2018
@distantnative distantnative added this to the Beta milestone Jul 9, 2018
@texnixe
Copy link
Member

texnixe commented Jul 10, 2018

Same for file metadata

@distantnative
Copy link
Member Author

And I'd assume user files too (basically anything using Kirby\Cms\HasContent).

@bastianallgeier
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug 🐛 Is a bug; fixes a bug
Projects
None yet
Development

No branches or pull requests

3 participants