Download and Install

Changelog

You are currently browsing
the website for symfony 1

Visit the Symfony2 website


Install symfony 1.2

About this Release

symfony training
Be trained by symfony experts
Aug 20: London (Getting Started with Symfony2 - English)
Aug 20: London (Web Development with Symfony2 - English)
Aug 21: Köln (Getting Started with Symfony2 - Deutsch)
Aug 21: Köln (Web Development with Symfony2 - Deutsch)
Aug 22: London (Mastering Symfony2 - English)
and more...
This page refers to the 1.2 symfony release. You can switch to:

See the UPGRADE_TO_1_1 for upgrading 1.0 projects first to 1.1. See the UPGRADE_TO_1_2 file for more information about upgrading your projects from 1.1 to 1.2.

All the new features are documented in the What's new? tutorial (http://www.symfony-project.org/tutorial/1_2/en/whats-new)

02/25/10: Version 1.2.12

The 1.2.12 release is security release. Please read http://www.symfony-project.org/blog/2010/02/25/security-release-1-2-12-1-3-3-and-1-4-3 for more information.

02/13/10: Version 1.2.11

12/01/09: Version 1.2.10

09/27/09: Version 1.2.9

07/13/09: Version 1.2.8

This release rolls back the security fix from 1.2.6/1.2.7:

"These changes have been done to plug a security hole in the symfonyadmin generator (more information on the symfony blog: http://www.symfony-project.org/blog/2009/04/27/symfony-1-2-6-security-fix).But a lot of people complained because it causes more harm than good. The fix disables for instance the possibility to have custom partials. Moreover, the problem also exists in a normal form if you don't use the "echo $form" construct and if you forget to display some non-required fields in the template. After some discussion with the core team members, it appears that there is no way to "fix" the problem for the developer. We thought that we would be able to provide something, but the reality is that we cannot. Is it a problem? We think it is not a big problem as the circumstances under which there can be an exploit are extremely rare or even inexistent as if you are vulnerable, it also means that your database data will be corrupted in some way (read the next section for more information). As a matter of fact, all frameworks around are vulnerable and have the exact same problem. We already provide more advanced security features for the form framework than anyother framework around, but we cannot go any further. Security is also a developer matter, and too much magic is sometimes a bad thing. Here is the exact circumstances under which you might be vulnerable: A field is vulnerable only if you forget to display its widget inthe template and only if it has a non-required validator. Then, an attacker could potentially inject a valid value for this field, and it will be saved with the rest of the object. But two things greatly mitigate the issue: first, if you forget to display a field, each time you save the form, its value will be lost. So, most of the time, you will be aware of the problem because the data in the database will be corrupted. Second, the attacker need to know the exact field name, which is not easy as no information is contained in the HTML."

Doctrine Plugin:

Propel Plugin:

05/02/09: Version 1.2.7

Contains the security fix from 1.2.6. Please read http://www.symfony-project.org/blog/2009/04/27/symfony-1-2-6-security-fix for more information.

Doctrine Plugin:

Propel Plugin:

04/27/09: Version 1.2.6

The 1.2.6 release is security release. Please read http://www.symfony-project.org/blog/2009/04/27/symfony-1-2-6-security-fix for more information.

03/28/09: Version 1.2.5

Doctrine Plugin:

Propel Plugin:

02/04/09: Version 1.2.4

Doctrine Plugin:

Propel Plugin:

01/31/09: Version 1.2.3

Doctrine Plugin:

Propel Plugin:

01/08/09: Version 1.2.2

Doctrine Plugin

12/11/08: Version 1.2.1

Doctrine Plugin

Propel Plugin

12/01/08: Version 1.2.0

Doctrine Plugin

Propel Plugin

11/26/08: Version 1.2.0 RC2

11/22/08: Version 1.2.0 RC1

Doctrine Plugin

Propel Plugin

11/10/08: Version 1.2.0 beta2

Doctrine Plugin

Propel Plugin

Version 1.2.0 beta1

Questions & Feedback

If you find a typo or an error, please register and open a ticket.

If you need support or have a technical question, please post to the official user mailing-list.