Doctrine2 behavioral extensions

v2.4.23 2016-09-12 05:54 UTC


Version 3.0.0

Build Status Total Downloads Latest Stable Version

Note: Extensions 3.0.x are compatible with ORM and doctrine common libraries from 2.5.x and requires PHP 5.4 or higher. Extensions 2.4.x are compatible with ORM and doctrine common library versions from 2.2.x to 2.5.x

Since the author has stopped working with PHP, looking for maintainers to ensure stability of doctrine extensions.

Latest updates


  • Nested tree now allows root field as association.
  • Sortable supports more than one sortable field per entity, has BC changes.
  • Uploadable supports more than one file per entity, may have implicit BC change if users have used their custom FilenameGeneratorInterface see #1342.


  • From now on, extensions will require php 5.4 or higher.
  • All trait column names will refer to naming strategy and won't be explicitly set by extensions.
  • Tree repositories are now using traits, for easier extensions.

Extensions and Documentation

This package contains extensions for Doctrine2 that hook into the facilities of Doctrine and offer new functionality or tools to use Doctrine2 more efficiently. This package contains mostly used behaviors which can be easily attached to your event system of Doctrine2 and handle the records being flushed in the behavioral way. List of extensions:

  • Tree - this extension automates the tree handling process and adds some tree specific functions on repository. (closure, nestedset or materialized path)
  • Translatable - gives you a very handy solution for translating records into different languages. Easy to setup, easier to use.
  • Sluggable - urlizes your specified fields into single unique slug
  • Timestampable - updates date fields on create, update and even property change.
  • Blameable - updates string or reference fields on create, update and even property change with a string or object (e.g. user).
  • Loggable - helps tracking changes and history of objects, also supports version management.
  • Sortable - makes any document or entity sortable
  • Translator - explicit way to handle translations
  • SoftDeleteable - allows to implicitly remove records
  • Uploadable - provides file upload handling in entity fields
  • References - supports linking Entities in Documents and vice versa
  • ReferenceIntegrity - constrains ODM MongoDB Document references
  • IpTraceable - inherited from Timestampable, sets IP address instead of timestamp

Currently these extensions support Yaml, Annotation and Xml mapping.

Note: Please note, that xml mapping needs to be in a different namespace, the declared namespace for Doctrine extensions is doctrine-extensions.xsd So root node now looks like this:

<doctrine-mapping xmlns="http://doctrine-project.org/schemas/orm/doctrine-extensions.xsd"

XML mapping xsd schemas are also versioned and can be used by version suffix:

ODM MongoDB support

List of extensions which support ODM

  • Translatable
  • Sluggable
  • Timestampable
  • Blameable
  • Loggable
  • Translator
  • Tree (Materialized Path strategy for now)
  • References
  • ReferenceIntegrity

All these extensions can be nested together and mapped in traditional ways - annotations, xml or yaml

Running the tests:

pdo-sqlite extension is necessary. To setup and run tests follow these steps:

  • install dev libraries: composer install
  • run: bin/phpunit -c tests
  • optional - run mongodb service if targeting mongo tests

NOTE: if php7 is used with mongodb install extension and dependencies using composer7.json. This is a temporary hack until the better ODM support is available.

Running the example:

To setup and run example follow these steps:

  • go to the root directory of extensions
  • install dev libraries: composer install
  • edit example/em.php and configure your database on top of the file
  • run: ./example/bin/console or php example/bin/console for console commands
  • run: ./example/bin/console orm:schema-tool:create to create schema
  • run: php example/run.php to run example


NOTE: composer7.json is only used to test extensions with ODM mongodb using php7, same for travis.

Thanks to everyone participating in the development of these great Doctrine2 extensions!

And especially ones who create and maintain new extensions: