The symfony core team is happy to announce the immediate availability of symfony 1.3 alpha2! This will be the last alpha release for the 1.3 branch, which means we are just a few days away from locking the API.

We've fixed a number of bugs and devoted considerable time to bringing Propel's integration up to speed with Doctrine's. Here are some of the development highlights since we last spoke...

Propel 1.4

Symfony now comes bundled with Propel 1.4. This latest version of the Propel ORM framework includes many exciting features, including build-time behaviors, better run-time introspection, and enhanced logging. Visit Propel's What's New in 1.4 page for more information.

Doctrine Migrations

A few new features have been added to symfony integration with Doctrine database migrations. A new task, doctrine:generate-migrations-diff, generates complete migration classes by comparing your project's old and new schemas. Additionally, --up and --down options have been added to doctrine:migration so you can easily step through your migrations, one at a time. For

A Better ->click()

You are now free to write cleaner and more flexible functional tests. The test browser's ->click() method now accepts any CSS selector, making it easy to target any button or link in a semantic fashion.

Cache More

Previous versions of symfony have disallowed caching of templates accessed with a query string in the address bar. We've changed this now, making it possible to cache any GET request.

Much of the documentation has been updated for symfony 1.3, including the Upgrade and What's New tutorials. We look forward to your feedback!

Published in #Releases

Fabian Lange said on Oct 13, 2009 at 00:12

It is really good to see that we could include Propel 1.4 in our symfony 1.3 roadmap. I think tons of users will appreciate this. But because propel project did not always care about compatibility in the branches in the past, I would like to ask as many propel users of symfony to check this release. We need feedback on propel 1.4 integration as soon as possible.

annis said on Oct 13, 2009 at 01:19

Awesome, thank you very much! I already started to port a symfony 1.2 project over to the first alpha and I've gotta say that it was a pretty smooth upgrade process.

Thanks again for a wonderful framework! Cheers, Daniel

Lukas said on Oct 13, 2009 at 01:51

Hey thanks team!! How to upgrade from alpha1 to alpha2 ?? Thanks in advance!

Kris said on Oct 13, 2009 at 03:24

@Lukas You can run the symfony project:upgrade task, but I don't think any new upgraders have been added since alpha 1.

Yuriy Voziy said on Oct 13, 2009 at 12:13

Mmmmm... migrations.

Stephen Melrose said on Oct 13, 2009 at 13:25

I've submitted an issue for your consideration. I'm not 100% sure it is relevant, but let me know what you think.

http://trac.symfony-project.org/ticket/7336

[MA]Pascal said on Oct 13, 2009 at 13:47

@Stephen did you use 'symfony project:optimize task' during your 1.3 benchmarks ?

Lukas said on Oct 13, 2009 at 15:32

@Kris Thanks for reply.. (I use Propel as ORM). When i run those task i have de follow error in mi cli:

Fatal error: Uncaught exception 'sfCommandException' with message 'The task named "configure:database" in "sfPropelConfigureDatabaseTask" task is already registered by the "sfDoctrineConfigureDatabaseTask" task.' in C:\desarrolloweb\sfprojects\worbit\lib\vendor\symfony\lib\command\sfCommandApplication.class.php:142 Stack trace:

Tom said on Oct 14, 2009 at 10:35

A better ->click() is good news! However: Is the problem with special chars in links solved? E.g. today you cant use click('äüöß')...

kendoctor said on Oct 17, 2009 at 15:45

#10

i'm from china i find symfony quite by chance i'm very excited to use this framework. i've learned it for one month. before, i tried to develop such a framework alike. but when dig symfony, i get lots of ideas and real implementations. now, i've started to organize what i learned to teach my group members. i hope i can use this framework as the main tools&IDE for our teams.