SymfonyWorld Online 2021 Winter Edition December 9 – 10, 2021 100% Online +20 talks and workshops
Caution: You are browsing the legacy symfony 1.x part of this website.

Doctrine Admin Generators


Real World Example

In this article I will start from the beginning with a brand new symfony 1.2 project so you can get going with Doctrine. We will use a schema for your typical, run-of-the-mill content management system. The schema consists of articles, authors and categories where the articles are internationalized.

Start your Project

First you need to initialize a brand new symfony 1.2 project and initialize a backend application. Make sure you are using the latest code from svn as beta1 did not include this Doctrine functionality.

Generate your project

$ mkdir cms
$ cd cms
$ symfony generate:project cms

Configure your database

Open config/databases.yml and replace the contents with a configuration for Doctrine like the following:

    class: sfDoctrineDatabase
      dsn:      mysql:host=localhost;dbname=dbname
      username: root
      password: secret

Generate backend application

$ symfony generate:app backend

Everybody get your Doctrine on

Now we need to enable Doctrine and disable Propel :) Edit your config/ProjectConfiguration.class.php and add the following code to your setup() function.

public function setup()

Now that Doctrine is enabled we can list the available Doctrine tasks:

$ ./symfony list doctrine

Available tasks for the "doctrine" namespace:
  :build-all                   Generates Doctrine model, SQL and initializes the database (doctrine-build-all)
  :build-all-load              Generates Doctrine model, SQL, initializes database, and load data (doctrine-build-all-load)
  :build-all-reload            Generates Doctrine model, SQL, initializes database, and load data (doctrine-build-all-reload)
  :build-all-reload-test-all   Generates Doctrine model, SQL, initializes database, load data and run all test suites (doctrine-build-all-reload-test-all)
  :build-db                    Creates database for current model (doctrine-build-db)
  :build-filters               Creates filter form classes for the current model
  :build-forms                 Creates form classes for the current model (doctrine-build-forms)
  :build-model                 Creates classes for the current model (doctrine-build-model)
  :build-schema                Creates a schema from an existing database (doctrine-build-schema)
  :build-sql                   Creates SQL for the current model (doctrine-build-sql)
  :data-dump                   Dumps data to the fixtures directory (doctrine-dump-data)
  :data-load                   Loads data from fixtures directory (doctrine-load-data)
  :dql                         Execute a DQL query and view the results (doctrine-dql)
  :drop-db                     Drops database for current model (doctrine-drop-db)
  :generate-admin              Generates a Doctrine admin module
  :generate-migration          Generate migration class (doctrine-generate-migration)
  :generate-migrations-db      Generate migration classes from existing database connections (doctrine-generate-migrations-db, doctrine-gen-migrations-from-db)
  :generate-migrations-models  Generate migration classes from an existing set of models (doctrine-generate-migrations-models, doctrine-gen-migrations-from-models)
  :generate-module             Generates a Doctrine module (doctrine-generate-crud, doctrine:generate-crud)
  :generate-module-for-route   Generates a Doctrine module for a route definition
  :insert-sql                  Inserts SQL for current model (doctrine-insert-sql)
  :migrate                     Migrates database to current/specified version (doctrine-migrate)
  :rebuild-db                  Creates database for current model (doctrine-rebuild-db)

The Schema

Now the fun begins. We have Doctrine enabled so the first thing we need to is define our schema for the CMS in config/doctrine/schema.yml.

      fields: [title, content]
    author_id: integer
      type: enum
      values: [Draft, Published]
      notnull: true
      type: string(255)
      notnull: true
      type: clob
      notnull: true
    is_on_homepage: boolean
    published_at: timestamp
      foreignAlias: Articles
      class: Category
      refClass: ArticleCategory
      foreignAlias: Articles
      type: string(255)
      notnull: true
      type: string(255)
      notnull: true
    about: string(1000)
    article_id: integer
    category_id: integer
      foreignAlias: ArticleCategories
      foreignAlias: ArticleCategories

Data Fixtures

We have our schema, now we need some data to test against so copy the following YAML in to data/fixtures/data.yml

    Author: jwage
    status: Published
    is_on_homepage: true
    published_at: '<?php echo date("Y-m-d h:i:s"); ?>'
    Categories: [article, ontheedge]
        title: symfony 1.2 and Doctrine
        content: Article about the new Doctrine integration in symfony 1.2
        title: symfony 1.2 et doctrine
        content: Article sur l'intégration de Doctrine dans symfony 1.2
    name: Jonathan H. Wage
    about: Jonathan is the lead developer of the Doctrine project and is also a core contributor to the symfony project.
    name: Article
    name: Tutorial
    name: Living on the edge

Building and Testing

Now that we have our schema and data fixtures we have everything we need to initialize our database, models, forms, data, etc. This can all be done with the extremely simply command below:

   $ ./symfony doctrine:build-all-reload --no-confirmation
>> doctrine  dropping databases
>> doctrine  creating databases
>> doctrine  generating model classes
>> doctrine  generating sql for models
>> doctrine  generating form classes
>> doctrine  generating filter form classes
>> doctrine  created tables successfully
>> doctrine  loading data fixtures from "/Us...ymfony12doctrine/data/fixtures"

That was too easy, when is this gonna get hard? Now lets do some inspecting with DQL to see that the data was loaded properly.

$ ./symfony doctrine:dql "FROM Article a, a.Author a2, a.Translation t"
>> doctrine  executing dql query
DQL: FROM Article a, a.Author a2, a.Translation t
found 1 results
  id: '1'
  author_id: '1'
  status: Published
  is_on_homepage: true
  published_at: '2008-11-06 04:37:11'
  created_at: '2008-11-06 16:37:11'
  updated_at: '2008-11-06 16:37:11'
    id: '1'
    name: 'Jonathan H. Wage'
    about: 'Jonathan is the lead developer of the Doctrine project and is also a core contributor to the symfony project.'
      id: '1'
      title: 'symfony 1.2 and Doctrine'
      content: 'Article about the new Doctrine integration in symfony 1.2'
      lang: en
      id: '1'
      title: 'symfony 1.2 et doctrine'
      content: 'Article sur l''intégration de Doctrine dans symfony 1.2'
      lang: fr

That may be your first taste of the Doctrine Query Language, also known as DQL. Looks a lot like SQL huh? Close your mouth, you're drooling.

For those of you who don't wanna write raw DQL strings, don't worry we have a fully featured Doctrine_Query object for building your queries.

$q = Doctrine_Query::create()
  ->from('Article a, a.Author a2, a.Translation t');
$articles = $q->execute();

Admin Generators

Now that we have everything built, we can start generating some magic with symfony. Lets start first by defining the route collections for managing our articles, authors and categories. Open apps/backend/config/routing.yml in your editor and paste the following routes inside.

  class:                    sfDoctrineRouteCollection
    model:                  Article
    module:                 articles
    prefix_path:            articles
    with_wildcard_routes:   true
  class:                    sfDoctrineRouteCollection
    model:                  Category
    module:                 categories
    prefix_path:            categories
    with_wildcard_routes:   true
  class:                    sfDoctrineRouteCollection
    model:                  Author
    module:                 authors
    prefix_path:            authors
    with_wildcard_routes:   true

These routes will allow us to generate an admin generator module for managing the data through each of the Doctrine models. Run the following commands to generate the three modules.

$ ./symfony doctrine:generate-admin backend articles
$ ./symfony doctrine:generate-admin backend categories
$ ./symfony doctrine:generate-admin backend authors

Now when you access the categories module from the backend you should see the following.

New Admin Generators

Now you may want to slightly customize the articles admin generators to display only a certain set of fields in the list and filters form. You can do so by editing the generator.yml located in apps/backend/modules/articles/config/generator.yml.

    display:  [title, published_at, is_on_homepage, status]
    class:    ArticleFormFilter
    display:  [author_id, status, is_on_homepage, published_at, categories_list]

You can customize the other modules as well in the same way.

Now if you change the url to have ?sf_culture=fr in your url the title will show the french version. You should see the following in your browser when you pull up the articles module.

New Admin Generators

Editing Translations

Now how do we go about editing those translations? If you remember this with the old admin generators, it was pretty much impossible. Now, it is a matter of adding one line of code to our ArticleForm. All we need to do is embed the ArticleTranslation form. This can be done by editing lib/form/doctrine/ArticleForm.class.php and adding the following code to configure()

public function configure()
  $this->embedI18n(array('en', 'fr'));

Now when you edit an article you will see you have the ability to edit translations directly inside of the article.

New Admin Generators I18n

Now that is pretty cool but what if you want to edit the Author directly inside of the Article as well and have it create a new Author if it doesn't exist and use the existing Author record if that name does exist. This is simple as well.

Edit/Add Author

In order to add the above described functionality we need to add a little bit of code in three difference places. First you need to embed the Author form in to the Article form by editing lib/form/doctrine/ArticleForm.class.php and add the following code.

public function configure()
  $authorForm = new AuthorForm($this->getObject()->getAuthor());
  $this->embedForm('Author', $authorForm);
  $this->embedI18n(array('en', 'fr'));


Optionally Optimize Queries

Now we can modify the articles actions class to join in the Author and Translation information so that the data is joined on the main query and not lazily loaded by Doctrine invoking additional queries to the database. This step is optional. Open apps/backend/modules/articles/actions/actions.class.php and override the executeEdit() function.

public function executeEdit(sfWebRequest $request)
  $this->article = Doctrine_Query::create()
    ->from('Article a')
    ->leftJoin('a.Author a2')
    ->leftJoin('a.Translation t')
    ->where(' = ?', $request->getParameter('id'))
  $this->form = $this->configuration->getForm($this->article);

Now when you view the form for editing and creating an Article you will see the embedded form for the Author with the existing information populated.

New Admin Generators Embedded Author

Now the last step is to tell Doctrine to look for existing Author objects when setting the name so that duplicate Author names are not created. Edit lib/model/doctrine/Author.class.php and override the name mutator by adding the following code.

public function setName($name)
  $name = trim($name);
  $found = Doctrine_Query::create()
    ->from('Author a')
    ->where(' = ?', $name)
    ->fetchOne(array(), Doctrine::HYDRATE_ARRAY);
  if ($found)
  } else {
    $this->_set('name', $name);

The above code will check if an Author with the passed name already exists, if it does it will assign the identifier of the found record otherwise it does what it normally would do, set the name to the object.


The _set() and _get() methods must be used to avoid a infinite loop when overriding accessors and mutators.