2014-10-27 04:40:02 +01:00
title: Extending DataObjects
summary: Modify the data model without using subclasses.
# Extending DataObjects
2017-07-03 03:22:12 +02:00
You can add properties and methods to existing [DataObject ](api:SilverStripe\ORM\DataObject )s like [Member ](api:SilverStripe\Security\Member ) without hacking core code or sub
classing by using [DataExtension ](api:SilverStripe\ORM\DataExtension ). See the [Extending SilverStripe ](../extending ) guide for more information on
[DataExtension ](api:SilverStripe\ORM\DataExtension ).
2014-10-27 04:40:02 +01:00
2017-07-03 03:22:12 +02:00
The following documentation outlines some common hooks that the [Extension ](api:SilverStripe\Core\Extension ) API provides specifically for managing
2014-10-27 04:40:02 +01:00
data records.
## onBeforeWrite
2016-03-30 02:17:28 +02:00
You can customise saving-behavior for each DataObject, e.g. for adding workflow or data customization. The function is
2014-10-27 04:40:02 +01:00
triggered when calling *write()* to save the object to the database. This includes saving a page in the CMS or altering
a `ModelAdmin` record.
Example: Disallow creation of new players if the currently logged-in player is not a team-manager.
2017-08-03 02:51:32 +02:00
```php
2017-08-07 05:11:17 +02:00
use SilverStripe\Security\Security;
use SilverStripe\ORM\DataObject;
class Player extends DataObject
{
private static $has_many = [
"Teams"=>"Team"
];
public function onBeforeWrite()
{
// check on first write action, aka "database row creation" (ID-property is not set)
if(!$this->isInDb()) {
$currentPlayer = Security::getCurrentUser();
if(!$currentPlayer->IsTeamManager()) {
user_error('Player-creation not allowed', E_USER_ERROR);
exit();
}
}
// check on every write action
if(!$this->record['TeamID']) {
user_error('Cannot save player without a valid team', E_USER_ERROR);
exit();
}
// CAUTION: You are required to call the parent-function, otherwise
// SilverStripe will not execute the request.
parent::onBeforeWrite();
}
}
2017-08-03 05:35:09 +02:00
2017-08-03 02:51:32 +02:00
```
2014-10-27 04:40:02 +01:00
## onBeforeDelete
Triggered before executing *delete()* on an existing object.
2015-02-28 01:09:15 +01:00
Example: Checking for a specific [permission ](permissions ) to delete this type of object. It checks if a
2014-10-27 04:40:02 +01:00
member is logged in who belongs to a group containing the permission "PLAYER_DELETE".
2017-08-03 02:51:32 +02:00
```php
2017-08-07 05:11:17 +02:00
use SilverStripe\Security\Permission;
use SilverStripe\Security\Security;
use SilverStripe\ORM\DataObject;
class Player extends DataObject
{
private static $has_many = [
"Teams" => "Team"
];
public function onBeforeDelete()
{
if(!Permission::check('PLAYER_DELETE')) {
Security::permissionFailure($this);
exit();
}
parent::onBeforeDelete();
}
}
2017-08-03 05:35:09 +02:00
2017-08-03 02:51:32 +02:00
```
2014-10-27 04:40:02 +01:00
< div class = "notice" markdown = '1' >
Note: There are no separate methods for *onBeforeCreate* and *onBeforeUpdate* . Please check `$this->isInDb()` to toggle
these two modes, as shown in the example above.
< / div >