What is Symfony?
Get started
Documentation
Community
Services
News

Latest News

Symfony Live San Francisco 2012

by Fabien Potencier – May 22, 2012

What happened last week in Symfony?

This week, Symfony 2.0.14 was released and the new OptionsResolver component was introduced. In addition, the first Symfony Community Survey was published to get a better understanding of the Symfony community.

Upcoming Events

The Symfony Community organizes events all over the world on a regular basis. Here are the next ones.

Germany, Hamburg — Symfony User Group Hamburg

on May 31, 2012, from 18:30 to 21:00

Germany, Berlin — Einführung in Symfony2 @ International PHP Conference

on June 04, 2012, from 14:15 to 15:00

France, Paris — Symfony Live Paris 2012

from June 06, 2012 to June 09, 2012

France, Paris — sfPot Paris

on June 12, 2012, from 19:00 to 23:05
About

Blog

symfony 1.3.7 & 1.4.7
by Kris Wallsmith – September 22, 2010 – 17 comments

The symfony team is happy to announce the immediate availability of symfony versions 1.3.7 and 1.4.7. These releases include a number of bug fixes as well as a Doctrine update and updates to some translations files. Read on for the details.

Doctrine 1.2.3

The bundled version of Doctrine has been updated to the latest release from the Doctrine 1.2 branch. Read more about this release on the Doctrine blog.

Using a Compiled Version of Doctrine

The symfony core is now compatible with a compiled version of the Doctrine library. The Doctrine compiler, which merges many of that library's core classes into one file, can provide a modest boost in performance by decreasing the number of file reads necessary for processing a request.

If you use sfTaskExtraPlugin in your project, you can easily run the Doctrine compiler using the doctrine:compile task.

You can read about the other minor fixes in the changelog.

How to Upgrade

If you've checked out a copy of the tag from Subversion you can switch to the latest version:

// symfony 1.3
$ svn switch http://svn.symfony-project.com/tags/RELEASE_1_3_7

// symfony 1.4
$ svn switch http://svn.symfony-project.com/tags/RELEASE_1_4_7

If you are using the PEAR package you can update using the pear command:

// symfony 1.3
$ pear upgrade symfony/symfony-1.3.7

// symfony 1.4
$ pear upgrade symfony/symfony-1.4.7

Have you upgraded to 1.4?

As I've mentioned in an earlier release announcement and has been documented on the symfony site since its release, version 1.3 is going to reach the end of its support period in November. If you haven't upgraded your 1.3 project to 1.4, now is the time. You can start by running the project:validate task and then ping the community via the symfony-users mailing list or on the IRC #symfony channel with any questions.

Add a Comment

You must be connected to post a comment.

Comments

#1 SlugO said on the 2010/09/22 at 07:11

Is the web debug bar broken in 1.4.7? It can be seen on top but none of its views can be expanded.
#2 kk said on the 2010/09/22 at 07:54

I report debug bar problem in sf1.4.7 (as Slug0).
#3 Ahto said on the 2010/09/22 at 09:09

Same problem here with the debug bar.
#4 Ahto said on the 2010/09/22 at 10:00

I left a message here http://trac.symfony-project.org/ticket/9080
#5 Massimiliano Arione said on the 2010/09/22 at 10:01

I opened a ticket for web debug toolbar broken: http://trac.symfony-project.org/ticket/9083
#6 Kris Wallsmith said on the 2010/09/22 at 11:39

Thanks for the report, guys. I'll release again with this fix soon.
#7 Peter Kokot said on the 2010/09/22 at 12:27

Thanks for the update. I'm just curious though, why none of the translation patches aren't included in the updates yet. Would it be possible to insert patches too or is this intentionally left behind?

http://trac.symfony-project.org/ticket/8985
http://trac.symfony-project.org/ticket/8167
http://trac.symfony-project.org/ticket/8532
http://trac.symfony-project.org/ticket/8885
http://trac.symfony-project.org/ticket/8960

Would be great instead of correcting i18n catalogues all the time with custom translations in application.

Regards.
#8 COil said on the 2010/09/22 at 16:04

Hummm... The multiple doctrine database management does not work any more. (the connection parameter for each table is ignored or not correctly retrieved)

+1 for debug bar
#9 Gimler said on the 2010/09/22 at 20:20

what is with this ticket http://trac.symfony-project.org/ticket/8915
#10 Gimler said on the 2010/09/22 at 20:25

and this ticket german translations for the admin generator http://trac.symfony-project.org/ticket/9088
#11 COil said on the 2010/09/23 at 10:11

http://trac.symfony-project.org/ticket/9092
#12 Fabien said on the 2010/09/23 at 16:48

I should have committed all translation changes mentioned in the comments.
#13 tayhimself said on the 2010/09/23 at 20:17

Who cares about the translation. What about the broken web debug toolbar?
#14 crypti said on the 2010/09/25 at 18:00

Does somebody of you know how to use "Using a Compiled Version of Doctrine"?
#15 Kris said on the 2010/09/25 at 18:24

@crypti the easiest way is to use sfTaskExtraPlugin's doctrine:compile command.
#16 Andi said on the 2010/09/27 at 11:14

" Hummm... The multiple doctrine database management does not work any more "

I have the same Problem with "multiple database connection" after the update to 1.4.8
#17 mattraines said on the 2010/09/29 at 12:48

Does anyone else get a fatal error running "php symfony doctrine:compile"?

PHP Fatal error: Cannot redeclare class Doctrine_Data_Import in /.../symfony/1.4/lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Data/Import.php on line 402

Using latest symfony 1.4 from trunk (1.4.9) and sfTaskExtraPlugin 1.3.3-DEV