Message-ID: <75477737.3726.1485855042140.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3725_1661138091.1485855042139" ------=_Part_3725_1661138091.1485855042139 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This Field Type is used as fallback and for testing purposes.
Name | Internal name | Expected input type |
---|---|---|
Null |
variable |
mixed |
As integration with Legacy Stack requires that all Field Types are also = also handled on 5.x stack side, Null Field Type is provided as a dummy for = legacy Field Types that are not really implemented on 5.x side.
Null Field Type will accept anything provided as a value, but will not s= tore anything to the database, nor will it read any data from the database.=
This Field Type does not have its own fixed internal name. Its identifie= r is instead configured as needed by passing it as an argument to the const= ructor.
Following example shows how Null Field Type is used to configure dummy i=
mplementations for ezcomcomments
and ezpaex
legac=
y datatypes:
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