Form validator and form builder addon for Cockpit CMS
Switch branches/tags
Nothing to show
Clone or download
Latest commit f89d5ee Nov 22, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
FormValidation bump version to 0.2.2 Nov 21, 2018
.gitattributes :neckbeard: Added .gitattributes & .gitignore files Jul 28, 2018
.gitignore :neckbeard: Added .gitattributes & .gitignore files Jul 28, 2018
LICENSE added license Oct 22, 2018 updated changelog Nov 16, 2018

Form Validation Addon for Cockpit

A form validator and form builder for Cockpit

Work in progress! Feel free to contribute with code, bug reports or feature requests.


Add files to addons/FormValidation.


  • Cockpit version >= 0.7.2
  • PECL intl extension (for punycode conversion of urls and mail adresses)


Form builder

I used the cp-fieldsmanager, where all field types are available. In my tests I only used these types:

  • text
  • textarea
  • boolean

It's meant for strings and I don't know (yet), what happens if it should validate arrays.

In the frontend it's possible to reuse some form options like "info", "label", "group", "lst", "width".


Form Validator

  • checks for required fields
  • checks for content types
  • sends response if validation fails

The idea is to add multiple checks on each field to trick spambots without using a captcha.

some templating

  • custom mail subject
  • field for reply to

see screenshots below

How to use

Create a field and click on "Validate" tab. Click on "Validate form data" to activate the validator.

When the validator is active, it checks, if required fields are present. If you want to allow sending fields, that aren't present in the form builder, you have to click "Allow extra fields".

To activate more validations, click on "Validate" for each field and add some json.

mail field

Create a text field.

  "type": {
    "mail": true,
    "url": false


Create a boolean field and name it "confirm". Spambots will love it :-D

  "honeypot": {
    "fieldname": "confirm",
    "expected_value": "0",
    "response": "Hello spambot. A human wouldn't fill this field."

If "response": "404", sender gets a 404 Path not found instead of a json response.



  • if form validation is active
    • key names must be alphanumeric (a-zA-Z0-9) or '-' or '_'
    • check, if required fields are present
    • sending data with unknown field names is not allowed
  • if field validation is active
    • no defaults, only specified validations


  • Validating to type:{"phone":false} could lead to false positives. The regex is meant to allow inputs like "0123 45678" or "+49 123-456-78", but "123" returns true, too.
  • honeypot: the field name must match the option honeypot.fieldname


Add a lang file in path/to/cockpit/config/formvalidation/i18n/de.php

Sample for German translation:


return [
    'is required' => 'ist ein Pflichtfeld',
    'does not exist' => 'existiert nicht',
    'Hello spambot' => 'Hallo Spambot',
    'must be mail' => 'Bitte geben Sie eine gültige E-Mail-Adresse ein.',
    'must be phone' => 'Bitte geben Sie eine Telefonnummer ein.',
    'must be url' => 'muss eine Url sein',
    'must not be mail' => 'In diesem Feld darf keine E-Mail-Adresse stehen (um Spambots zu verwirren).',
    'must not be phone' => 'In diesem Feld darf keine Telefonnummer stehen (um Spambots zu verwirren).',
    'must not be url' => 'In diesem Feld darf keine Url stehen (um Spambots zu verwirren).'

To do

  • allow mail addresses with special chars (punycode) - they are valid, but filter_var($to, FILTER_VALIDATE_EMAIL) returns false
    • --> overwrite original submit function again or
    • --> change the mail validation in cockpit core --> now in core
  • i18n of error responses
  • friendly error responses --> use i18n
  • add a view to include via PHP frontend


  • required (!empty)
  • honeypot (humans wouldn't fill this field)
  • type (mail, phone, url)
  • !type (inverse type)
  • equals (= string) (for simple captchas or something like "Are you really sure? Type 'Yes'")
  • contains
    • code
    • url(s)
    • string


  • mail
  • phone
  • url
  • number
  • bool
  • ascii
  • date --> must be i18n specific
  • ...

Form Mail Template Example

Create a custom mail template in config/forms/emails/formname.php to use the settings "email_text_before" and "email_text_after".


// map field labels to data names
$out = cockpit('formvalidation')->nameToLabel($data, $frm);

// templating in email_text_after and email_text_before
$email_text_before = isset($frm['email_text_before']) && !empty($frm['email_text_before']) ? cockpit('formvalidation')->map($frm['email_text_before'], $data) : false;

$email_text_after = isset($frm['email_text_after']) && !empty($frm['email_text_after']) ? cockpit('formvalidation')->map($frm['email_text_after'], $data) : false;

<html><head><meta charset="utf-8" /></head><body>
<?php if ($email_text_before): ?>
<p>{{ $email_text_before }}</p>
<?php endif; ?>
<?php foreach ($out as $field => $val): ?>
<p><strong>{{ $field }}:</strong><br />
{{ $val }}</p>
<?php endforeach;?>
<?php if ($email_text_after): ?>
<p>{{ $email_text_after }}</p>
<?php endif; ?>



  • improved Admin.php overwrite
  • added version numbers and git tags
  • fixed empty forms index page in upcoming Cockpit v0.8.4 original changed


  • added i18n
  • now throws response as an Exception if using Cockpit as a library


  • moved addon to subfolder
  • disabled experimental custom #config path
  • added warning if global mailer settings aren't defined
  • added custom mailer settings to define individual mailers per form