Message-ID: <1076588333.3880.1485855754335.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3879_1969003613.1485855754335" ------=_Part_3879_1969003613.1485855754335 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html The Null FieldType

The Null FieldType

This field type is used for fallback and testing purposes.

Name Internal name Expected input type
Null variable mixed

Description

As integration with Legacy Stack requires that all FieldTypes are also a= lso handled on 5.x stack side, Null FieldType is provided as a dummy for le= gacy FieldTypes that are not really implemented on 5.x side.

Null FieldType will accept anything provided as a value, but will not st= ore anything to the database, nor will it read any data from the database.<= /p>

This FieldType does not have its own fixed internal name. Its identifier= is instead configured as is needed by passing it as an argument to the con= structor.

Following example shows how Null FieldType is used to configure dummy im= plementations for ezcomcomments and ezpaex legacy= datatypes:

Null Fieldtype example configuration
=20
parameters:
    ezpublish.fieldType.eznull.class: eZ\Publish\Core\FieldType\Null\Type

services:
    ezpublish.fieldType.ezcomcomments:
        class: %ezpublish.fieldType.eznull.class%
        parent: ezpublish.fieldType
        arguments: [ "ezcomcomments" ]
        tags:
            - {name: ezpublish.fieldType, alias: ezcomcomments}
    ezpublish.fieldType.ezpaex:
        class: %ezpublish.fieldType.eznull.class%
        parent: ezpublish.fieldType
        arguments: [ "ezpaex" ]
        tags:
            - {name: ezpublish.fieldType, alias: ezpaex}
=20
------=_Part_3879_1969003613.1485855754335--