-
Notifications
You must be signed in to change notification settings - Fork 333
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
Scaffold fields for SiteTree #2767
Comments
6 tasks
This was referenced Aug 8, 2024
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
This was referenced Aug 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you define DB fields for a regular DataObject,
getCMSFields
will scaffold them for you.SiteTree doesn't do that. So you have to manually created all the fields. We should remedy this.
Maybe we provide an option to disable that to minimise upgrade pain.
Note
Acceptance Criteria
SiteTree::getCMSFields()
callsparent::getCMSFields()
(which will autoscaffold fields)SiteTree::getCMSFields()
is wrapped in$this->beforeUpdateCMSFields()
so extension hooks are called appropriatelygetCMSFields()
in their page classes to ensure things are working the way they expect (e.g. autscaffoldedhas_many
andmany_many
relations may be giving them new tabs that weren't there before)CMS 5 PRs
CMS 6 PRs
kitchen sink CI run
recipe-reporting failure is expected because we're forking framework for that CI run.
Compare with normal CMS 6 run for other failures.
The text was updated successfully, but these errors were encountered: