Global navigation

   Documentation Center
   eZ Studio & eZ Platform
     User Manual
     Technical Manual
     Glossary
   eZ Publish 4.x / legacy

 
eZ Publish (5.x)

eZ Publish 5.x | For eZ Platform & eZ Studio topics see Technical manual and User manual, for eZ Publish 4.x and Legacy topics see eZ Publish legacy

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • accept as input the URL of a tweet (https://twitter.com/<username>/status/<id>)

  • fetch the tweet using the twitter oEmbed API (https://dev.twitter.com/docs/embedded-tweets)

  • store the tweet’s HTML & author URL in a custom database tableembed contents and url

  • display the tweet's embed when displaying the field from a template

...

FieldTypes, like any other eZ Publish 5 extensions, must be provided as Symfony 2 bundles. This chapter will cover the creation and organization of this bundle
Read more about Creating the bundle and structuring the bundle.

 API

This part will cover the implementation of the eZ Publish API elements required to implement a custom FieldType
Read more about implementing the API.

...

Storing data from any FieldType into the Legacy Storage Engine requires that your custom data is mapped to the data model. This part will cover the implemention of the storage converter for the Tweet FieldType
Read more about Implementing the Legacy Storage Engine Converter.

Templating

Displaying a FieldType's data is done through a twig template.
Read more about implementing the FieldType template.

 Custom storage

Whenever a FieldType must store more than the basic primitives the API supports, custom, external storage must be implemented. This part covers how a FieldType can store custom data anywhere, in particular into custom tables in the legacy database.