Version 6 pre-stable
This version of Silverstripe CMS has not yet been given a stable release. See the release roadmap for more information. Go to documentation for the most recent stable version.

Form validation

Before you start implementing custom validation logic, check out validation using symfony/validator constraints and see if there's an existing constraint that can do the heavy lifting for you.

Silverstripe CMS provides server-side form validation out of the box through the Validator abstract class and its' child classes (see available validators below). A single Validator instance is set on each Form. Validators are implemented as an argument to the Form constructor or through the function setValidator.

namespace App\PageType;

use PageController;
use SilverStripe\Forms\EmailField;
use SilverStripe\Forms\Form;
use SilverStripe\Forms\FormAction;
use SilverStripe\Forms\RequiredFields;
use SilverStripe\Forms\TextField;

class MyFormPageController extends PageController
{
    private static $allowed_actions = [
        'getMyForm',
    ];

    private static $url_handlers = [
        'MyForm' => 'getMyForm',
    ];

    public function getMyForm()
    {
        $fields = FieldList::create(
            TextField::create('Name'),
            EmailField::create('Email')
        );

        $actions = FieldList::create(
            FormAction::create('doSubmitForm', 'Submit')
        );

        // the fields 'Name' and 'Email' are required.
        $required = RequiredFields::create([
            'Name', 'Email',
        ]);

        // $required can be set as an argument
        $form = Form::create($controller, 'MyForm', $fields, $actions, $required);

        // Or, through a setter.
        $form->setValidator($required);

        return $form;
    }

    public function doSubmitForm($data, $form)
    {
        // ...
    }
}

In this example we will be required to input a value for Name and a valid email address for Email before the doSubmitForm method is called.

Each individual FormField instance is responsible for validating the submitted content through the FormField::validate() method. By default, this just checks the value exists. Fields like EmailField override validate to check for a specific format.

Extensions

Extensions applied to FormField, or subclasses, can hook into the validation logic and adjust the results by utilising the updateValidationResult method. For example, an extension applied to EmailField could look like this:

namespace App\Extension;

use SilverStripe\Core\Extension;
use SilverStripe\Forms\Validator;

class FormFieldValidationExtension extends Extension
{
    protected function updateValidationResult(bool &$result, Validator $validator)
    {
        if (str_ends_with($this->owner->Value(), '@example.com')) {
            $validator->validationError($this->owner->Name(), 'Please provide a valid email address');
            $result = false;
        }
    }
}

This extension hook will not work without the ampersand (&) in the &$result argument. This is because the return value of the function is ignored, so the validation result has to be updated by changing the value of the $result variable. This is known as passing by reference.

Validation in FormField subclasses

Subclasses of FormField can define their own version of validate to provide custom validation rules such as the above example with the Email validation. The validate method on FormField takes a single argument of the current Validator instance.

namespace App\Form\Field;

use SilverStripe\Forms\NumericField;

class CustomNumberField extends NumericField
{
    // ...

    public function validate($validator)
    {
        if ((int) $this->Value() === 10) {
            $validator->validationError($this->Name(), 'This value cannot be 10');
            return $this->extendValidationResult(false, $validator);
        }

        return $this->extendValidationResult(true, $validator);
    }
}

The validate method should compute a boolean (true if the value passes validation and false if Silverstripe CMS should trigger a validation error on the page) and pass this to the extendValidationResult method to allow extensions to hook into the validation logic. In addition, in the event of failed validation, a useful error message must be set on the given validator.

You can also override the entire Form validation by subclassing Form and defining a validate method on the form.

Form action validation

ValidationException

At times it's not possible for all validation or recoverable errors to be pre-determined in advance of form submission, such as those generated by the form Validator. Sometimes errors may occur within form action methods, and it is necessary to display errors on the form after initial validation has been performed.

In this case you may throw a ValidationException within your handler, optionally passing it an error message, or a ValidationResult containing the list of errors you wish to display.

E.g.

namespace App\Control;

use SilverStripe\Control\Controller;
use SilverStripe\Core\Validation\ValidationException;

class MyController extends Controller
{
    public function doSave($data, $form)
    {
        $success = $this->sendEmail($data);

        // Example error handling
        if (!$success) {
            throw new ValidationException('Sorry, we could not email to that address');
        }

        // If success
        return $this->redirect($this->Link('success'));
    }
}

Session validation result

An alternative approach to using custom class or an extension is to define the behavior inside the Form's action method. This is less reusable and would not be possible within the CMS or other automated UI but does not rely on creating custom FormField classes or extensions.

namespace App\PageType;

use PageController;
use SilverStripe\Core\Validation\ValidationResult;
use SilverStripe\Forms\EmailField;
use SilverStripe\Forms\FieldList;
use SilverStripe\Forms\Form;
use SilverStripe\Forms\FormAction;
use SilverStripe\Forms\TextField;
use SilverStripe\Security\Member;

class MyFormPageController extends PageController
{
    // ...

    public function getMyForm()
    {
        $fields = FieldList::create(
            TextField::create('Name'),
            EmailField::create('Email')
        );

        $actions = FieldList::create(
            FormAction::create('doSubmitForm', 'Submit')
        );

        $form = Form::create($this, 'MyForm', $fields, $actions);

        return $form;
    }

    public function doSubmitForm($data, $form)
    {
        // At this point, RequiredFields->isValid() will have been called already,
        // so we can assume that the values exist. Say we want to make sure that email hasn't already been used.

        $check = Member::get()->filter('Email', $data['Email'])->first();

        if ($check) {
            $validationResult = ValidationResult::create();
            $validationResult->addFieldError('Email', 'This email already exists');
            $form->setSessionValidationResult($validationResult);
            $form->setSessionData($form->getData());
            return $this->redirectBack();
        }


        $form->sessionMessage('You have been added to our mailing list', 'good');

        return $this->redirectBack();
    }
}

Available validators

The Silverstripe framework comes with the following built-in validators:

  • CompositeValidator A container for additional validators. You can implement discrete validation logic in multiple Validator subclasses and apply them all to a given form by putting them inside a CompositeValidator. The CompositeValidator doesn't have perform any validation by itself.
  • FieldsValidator Simply calls validate() on all data fields in the form, to ensure fields have valid values.
  • RequiredFields Validates that fields you declare as "required" have a value.

There are additional validators available in community modules, and you can implement your own validators by subclassing the abstract Validator class.

Validation-exempt actions

In some cases you might need to disable validation for specific actions. For example actions which discard submitted data may not need to check the validity of the posted content.

You can disable validation on individual using one of two methods:

namespace App\PageType;

use PageController;
use SilverStripe\Forms\FieldList;
use SilverStripe\Forms\Form;
use SilverStripe\Forms\FormAction;

class MyFormPageController extends PageController
{
    // ...

    public function getMyForm()
    {
        // ...

        $actions = FieldList::create(
            $action = FormAction::create('doSubmitForm', 'Submit')
        );

        $form = Form::create($this, 'MyForm', $fields, $actions);
        // Disable actions on the form action themselves
        $action->setValidationExempt(true);
        // Alternatively, you can whitelist individual actions on the form object by name
        $form->setValidationExemptActions(['doSubmitForm']);

        return $form;
    }

    // ...
}

Server-side validation messages

If a FormField fails to pass validate() the default error message is returned.

'$Name' is required

Use setCustomValidationMessage to provide a custom message.

use SilverStripe\Forms\TextField;

$field = TextField::create(/* .. */);
$field->setCustomValidationMessage('Whoops, looks like you have missed me!');

JavaScript validation

Although there are no built-in JavaScript validation handlers in Silverstripe CMS, the FormField API is flexible enough to provide the information required in order to plug in custom libraries like Parsley.js. Most of these libraries work on HTML data- attributes or special classes added to each input. For Parsley we can structure the form like.

namespace App\PageType;

use PageController;
use SilverStripe\Forms\Form;

class MyFormPageController extends PageController
{
    // ...

    public function getMyForm()
    {
        // ...

        $form = Form::create($this, 'MyForm', $fields, $actions);
        $form->setAttribute('data-parsley-validate', true);

        $field = $fields->dataFieldByName('Name');
        $field->setAttribute('required', true);
        $field->setAttribute('data-parsley-mincheck', '2');

        return $form;
    }
}

Model validation

An alternative (or additional) approach to validation is to place it directly on the database model. Silverstripe CMS provides a DataObject::validate() method to validate data at the model level. See Data Model Validation.

Validation in the CMS

In the CMS, we're not creating the forms for editing CMS records. The Form instance is generated for us so we cannot call setValidator easily. However, a DataObject can provide its own Validator instance/s through the getCMSCompositeValidator() method. The CMS interfaces such as LeftAndMain, ModelAdmin and GridField will respect the provided Validator/s and handle displaying error and success responses to the user.

Again, custom error messages can be provided through the FormField

namespace App\PageType;

use Page;
use SilverStripe\Forms\CompositeValidator;
use SilverStripe\Forms\FieldList;
use SilverStripe\Forms\RequiredFields;
use SilverStripe\Forms\TextField;

class MyPage extends Page
{
    private static $db = [
        'MyRequiredField' => 'Text',
    ];

    public function getCMSFields()
    {
        $this->beforeUpdateCMSFields(function (FieldList $fields) {
            $fields->addFieldToTab(
                'Root.Main',
                TextField::create('MyRequiredField')->setCustomValidationMessage('You missed me.')
            );
        });
        return parent::getCMSFields();
    }

    public function getCMSCompositeValidator(): CompositeValidator
    {
        $validator = parent::getCMSCompositeValidator();
        $validator->addValidator(RequiredFields::create([
            'MyRequiredField',
        ]));
        return $validator;
    }
}

You can also update the CompositeValidator by creating an Extension and implementing the updateCMSCompositeValidator() method.

API documentation

Edit on Github