Merge pull request #9076 from open-sausages/pulls/4/docs-cascade-publish-delete

DOCS Clarify cascade publish/delete perm checks
This commit is contained in:
Robbie Averill 2019-06-18 18:09:24 +12:00 committed by GitHub
commit ca0949057d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 11 additions and 0 deletions

View File

@ -511,6 +511,11 @@ If your object is versioned, cascade_deletes will also act as "cascade unpublish
on a parent object will trigger unpublish on the child, similarly to how `owns` causes triggered publishing. on a parent object will trigger unpublish on the child, similarly to how `owns` causes triggered publishing.
See the [versioning docs](/developer_guides/model/versioning) for more information on ownership. See the [versioning docs](/developer_guides/model/versioning) for more information on ownership.
<div class="alert" markdown="1">
Declaring cascade_deletes implies delete permissions on the listed objects.
Built-in controllers using delete operations check canDelete() on the owner, but not on the owned object.
</div>
## Cascading duplications ## Cascading duplications
Similar to `cascade_deletes` there is also a `cascade_duplicates` config which works in much the same way. Similar to `cascade_deletes` there is also a `cascade_duplicates` config which works in much the same way.

View File

@ -63,6 +63,12 @@ SilverStripe makes this possible by using the concept of _cascade publishing_. Y
A non-recursive publish operation is also available if you want to publish a new version of a object without cascade publishing all its children. A non-recursive publish operation is also available if you want to publish a new version of a object without cascade publishing all its children.
<div class="alert" markdown="1">
Declaring ownership implies publish permissions on owned objects.
Built-in controllers using cascading publish operations check canPublish()
on the owner, but not on the owned object.
</div>
#### Ownership of unversioned object #### Ownership of unversioned object
An unversioned object can own other versioned object. An unversioned object can be configured to automatically publish children versioned objects on save. An unversioned object can own other versioned object. An unversioned object can be configured to automatically publish children versioned objects on save.