Your SlideShare is downloading. ×
eZ Publish Summer Camp 2013 - Building custom field types
eZ Publish Summer Camp 2013 - Building custom field types
eZ Publish Summer Camp 2013 - Building custom field types
eZ Publish Summer Camp 2013 - Building custom field types
eZ Publish Summer Camp 2013 - Building custom field types
eZ Publish Summer Camp 2013 - Building custom field types
eZ Publish Summer Camp 2013 - Building custom field types
eZ Publish Summer Camp 2013 - Building custom field types
eZ Publish Summer Camp 2013 - Building custom field types
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

eZ Publish Summer Camp 2013 - Building custom field types

623

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
623
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Building custom field types Edi Modrić ( @emodric ) https://github.com/emodric/EzscIpAddressBundle
  • 2. About me • Edi Modrić • Computer engineering masters degree • Working at Netgen for 6 years • 5 years of eZ Publish development • Certified eZ Publish developer • eZ Tags maintainer • Collaborated with eZ Systems on eZ Publish 5 kernel • @emodric • edi@netgen.hr
  • 3. Agenda • A little bit of theory • Coding a simple field type • Verifying that it works
  • 4. The code $ cd /var/www/ezpublish/src/ $ mkdir Netgen && cd Netgen $ git clone git://github.com/emodric/Ezsc IpAddressBundle.git
  • 5. Datatype + public API = field type • Content class = Content type • Content object = Content • Content class attribute = Field definition • Content object attribute = Field • Object attribute content = Field value • Datatype = Field type
  • 6. Field type components • Main field type implementation • Field type value • Per storage converters
  • 7. Field type storage • Internal storage • Stores data to ezcontentobject_attribute DB table • External storage • Custom database tables • Anything else
  • 8. What about legacy stack? • Legacy datatypes are not going anywhere • No admin interface based on Symfony stack • To actually use your field type, you WILL need legacy datatype
  • 9. Field type vs. datatype • No difference in functionality • Advantages over datatypes • Clear separation of concerns • No POST variables • No SQL • No file uploads • More readable and understandable code

×