Merge pull request #3682 from bendubuisson/patch-1

Update 5-dataobject-relationship-management.md
This commit is contained in:
Ingo Schommer 2014-11-26 11:53:28 +13:00
commit a61fb89e4f

View File

@ -98,7 +98,7 @@ The restriction is enforced through the `$allowed_children` directive.
} }
You might have noticed that we don't specify the relationship You might have noticed that we don't specify the relationship
to a project. That's because its already inherited from the parent implementation, to a project. That's because it's already inherited from the parent implementation,
as part of the normal page hierarchy in the CMS. as part of the normal page hierarchy in the CMS.
Now that we have created our `ProjectsHolder` and `Project` page types, we'll add some content. Now that we have created our `ProjectsHolder` and `Project` page types, we'll add some content.
@ -113,7 +113,7 @@ and collect those within a `ProjectsHolder`.
But what about creating `Student` records? But what about creating `Student` records?
Since students are related to a single project, we will Since students are related to a single project, we will
allow editing them right the on the CMS interface in the `Project` page type. allow editing them right on the CMS interface in the `Project` page type.
We do this through a powerful field called `[GridField](/reference/grid-field)`. We do this through a powerful field called `[GridField](/reference/grid-field)`.
All customization to fields for a page type are managed through a method called All customization to fields for a page type are managed through a method called
`getCMSFields()`, so let's add it there: `getCMSFields()`, so let's add it there: