Symfony 1.1 - What’s new?

Fabien has returned from the IPC 2007 in Frankfurt and he has published all the slides of his presentation in his new blog.

He promised to commit the last two missing classes (sfForm and sfFormField) by the end of the month.

After that commit, the last missing element for the waited new Framework will be the documentation.

In this article, I will briefly explain all the significant changes of Symfony 1.1 so that you will have fewer doubts deciding between: rewrite part of your old code, simply update your application or use the new Symfony 1.1 only in new developments.

I will really appreciate your comments and your choice about upgrading.

Mauro Casula

• New task framework

The new task framework will be very simple to extend and will be organized in task namespaces.

Task namespaces examples:
> symfony generate:app …
> symfony generate:controller …
> symfony generate:module …
> symfony plugin:install sfGuardPlugin

In addicion, it has been introduced a very usefull task help system:
> symfony help plugin:install

It will be possible to call a task directly from the code:
$task = new sfCacheClearTask($dispatcher);

Event dispacher and dependencies re-organization

Developers worked very hard over the core classes, removing dependencies and singletons and introducing a new event dispatcher system.

New depenedencies

• New Form, Widget, Validator framework

As I wrote in my previous post, the symfony form handling system has been completely rewritten.
The old validation system will be still included in Symfony 1.1; the only thing we have to do about to still use is to set the parameter “compat_10: on” in settings.yml.

The new approach consist of three different sub-systems:

- Widgets ( sfWidget )
- Validators ( sfValidator and sfValidatorSchema )
- Forms ( sfForm )

Each one of these sub-systems are stateless, completely independent from the other classes;
so it will be possible to use this system outside a symfony application.


A widget is an object that can be rendered as an HTML string. It substitutes the use of the helpers.
The base class of all form widgets is called sfWidgetForm: Symfony 1.1 will provide a set of ready to use widgets like sfWidgetFormInput.
The use of a Widget is very simple and similar to the use of a helper:

// create a new input widget
$w = new sfWidgetFormInput();
// render widget
echo $w->render(’first_name’, ‘Fabien’);
// returns the widget as HTML
<input type=”text” name=”first_name” value=”Fabien” id=”first_name” />

In Symfony 1.1 will be introduced the sfWidgetFormSchema class.
A widget schema is simply a group of named widgets.

$w1 = new sfWidgetFormInput();
$w = new sfWidgetFormSchema(array(
‘first_name’ => $w1,
‘last_name’ => $w1,


As in the old releases of Symfony, all validators will extend sfValidator class.
Validator class is stateless and you can aggregate validators to create new extended validators.

The concept of a validator schema is very similar to the concept of widget schema.
A validator schema is a set of named validators.


Fabien define a Form as the glue between a validator schema and a widget schema.

The sfForm class will be the class the user will use when he have to interact with a Web form.

From the model to the view, from the view to the validator and from the validator to the model
sfForm class has all the methods you need for build an html form, to set the apropriate
validation rules of every field and finally for retrieve the data and save it.

I will close this article, writing about the sfFormPropel class.
I think this is simply the best we can expect from a framework.
sfFormPropel class introspects the Propel schema and maps Propel/Creole types to symfony validators and
widgets, intercepting foreign keys and many to many relationships.

Symfony 1.1 will be a little revolution.
Maybe, many developers will use the “compat_10: true” option instead of rewrite the form and validation code of their applications, but for the new projects new features will be the best way.

8 Responses to “Symfony 1.1 - What’s new?”

You can leave a response, or trackback from your own site.

  1. Nov24


    Said this at 2:30pm:

    And what about Doctrine ? Will it be included in 1.1 ?

    A big question about Symfony is always wich ORM choose ;-)

  2. Nov24


    Said this at 7:28pm:

    Rumors say that Doctrine will be the official ORM in Symfony 1.1.

    Propel 1.3 require Php 5.2.x and in actually in beta version.

    The old propel ORM will be available in Symfony 1.1 as Plugin.

    Bye and thanks for visiting

    Mauro Casula.

  3. Nov24


    Said this at 8:23pm:

    This is great - exactly what I was looking for. I’m using symfony from svn, and have been doing my best to get my project base to where compat_10 is set to off. The only major issue at this point is lack of documentation - I simply haven’t been able to figure out what changes need to be made to convert the old helper system to the new. I love the new changes, and I’m looking forward to jumping on all the new documentation as it comes out.

  4. Nov28

    Fabio Cevasco

    Said this at 8:26am:

    Sounds interesting.

  5. Nov28

    Said this at 4:23pm:

    Very Interesting post.

    Do you know when Symfony 1.1 will be released?


  6. Nov28 » Symfony 1.1 - What’s new?

    Said this at 8:50pm:

    […] the website, there’s a look at what’s new in the latest Symfony build, version 1.1, as presented by Fabien Potencier at this […]

  7. Dec20


    Said this at 3:58pm:

    Doctrine will still be a plugin in 1.1.
    Propel & Doctrine will both be plugins for 1.2

    Fabien posted about this on his blog.

  8. Dec20


    Said this at 5:15pm:

    I have read that article…

    I will update my post..


    Mauro Casula.


Leave a Reply


Recent Posts

Popular Categories

No categories


We are a group of programmers with the passion of Object Oriented Programming and PHP5… We hope to help the Symfony comunity to grow, we hope to help Php programmers to switch to MVC world and we wish you can find in this blog all you answers… Welcome to

<<The Administrators>>