Skip to the content
Documentation

The RichText FieldType

No ratings yet

This format is used by eZ P

 

This FieldType is not officially supported yet, it will be as of first stable eZ Platform release.

This FieldType validates and stores structured richtext, and exposes it in several formats.

Name Internal name Expected input
RichText
ezrichtext
mixed

Input expectations

Type Description Example
string
XML document in one of the FieldType's input formats as a string. See the example below.
DOMDocument

XML document in one of the FieldType's input formats as a

DOMDocument object.

See the example below.
eZ\Publish\Core\FieldType\RichText\Value
An instance of the FieldType's  Value  object. See the example below.

Input formats

FieldType works with XML and also expects an XML value as input, wether as a string,  DOMDocument object or FieldType's  Value  object. When the value is given as a string or a DOMDocument  object, it will be checked for conformance to the one of the supported input formats, then dispatched to the appropriate converter, to be converted to the FieldType's internal format. No conversion will be performed if providing the value in FieldType's internal format, or when providing the value as FieldType's  Value  object. In the latter case it will be expected that Value  object holds the value in FieldType's internal format.

Currently supported input formats are described in the table below:

Name Description
Exponential Docbook variant FieldType's internal format
XHTML5 editing format Typically used with in-browser HTML editor
Legacy eZXML format Compatibility with legacy eZXML format, used by XmlText FieldType  

Example of the FieldType's internal format

Example of the FieldType's XHTML5 edit format

This format is used by eZ Platform Online Editor and will change with its needs as we continue to evolve this part of the UI.

For more information about internal format and input formats, see FieldType's conversion test fixtures on GitHub.

For example, ezxml does not use explicit level attributes for <header> elements, instead <header> element levels are indicated through the level of nesting inside <section> elements.

Example of using XML document in internal format as a string

Value object API

eZ\Publish\Core\FieldType\RichText\Value  offers following properties:

Property Type Description
xml
DOMDocument
Internal format value as an instance of  DOMDocument.

REST API specifics

Creating or updating Content

When creating RichText content with the REST API, it is possible to provide data as a string, using the "xml" fieldValue key:

When the value given over REST API is transformed into a FieldType's  Value  object, it will be treated as a string. This means you can use any supported input format for input over REST API.

Contributors

Comments (2 historical)

Written by readers of the earlier documentation sites, kept as they were.

  1. Comment by Eirik Alfstad Johansen, 2015-12-09 15:02

    Eirik Alfstad Johansen ·

    Now that we're approaching the release of eZ Platform, this page is perhaps due for an update?

  2. Comment by André Rømcke, 2015-12-09 15:27

    André Rømcke ·

    Ideally this should have been on github so you could have contributed to it, but yes in time it will 

    Smile

Comments

Add a comment

Comments are read by a moderator before they appear.