symfony 1.3 beta 2

The core team is happy to announce the immediate availability of symfony 1.3.0 beta 2. It is available for installation over PEAR or by checkout directly from the Subversion repository. Visit the installation page for all the details.

This is the final beta release of the 1.3 branch, so there aren't too many exciting new features to announce. Our focus has been on improving the stability of the existing code base since the API was locked with the beta 1 release. More information about what's new in symfony 1.3 can be found in the what's new and upgrade tutorials.

Propel 1.4 stable

Integration with Propel 1.4, whose first stable version was just released, has been cleaned up and is now more stable and easier to customize. As Fabian mentioned earlier, the new Propel 1.4 detailed query logging mechanism is now easily configured using symfony's database configuration file.

Response Validation

The response tester, which received a new method for testing the validity of a response in the 1.3 beta 1 release, now supports XSD- and RelaxNG-based validation as well as DTD. What's more, standard DTD definitions are now bundled with symfony, eliminating the cost of external requests when running these validations.

Minor bugs were fixed in the newly-enhanced pager objects, the Propel upgrade task, and the generation of form classes based on Doctrine inheritance models.

What's Next?

We plan to have two release candidate releases before releasing the first stable version of symfony 1.3 at the end of the month. The schedule, subject to change, is as follows:

  • 16 November: 1.3.0 RC1
  • 23 November: 1.3.0 RC2
  • 30 November: 1.3.0 stable

Yep, that's one release a week for the rest of the month. If you haven't done so already, please take a moment to test upgrading an existing symfony 1.2 application to 1.3. The upgrade should go smoothly at this point, but please post any issues you may encounter to Trac. Thank you for helping make this coming release the best it can be!

Comments

Hi,

Pear channel is not updated
[root@ozzy ~]# pear clear-cache
reading directory /var/cache/php-pear
4 cache entries cleared
[root@ozzy ~]# pear upgrade symfony/symfony-1.3.0BETA2
Nothing to upgrade

I'm developing my first big symfony project with 1.3-alpha, beta and I don't have any problems so far :)

I think I really like this framework :)

Regards,
Michal
What about sf 1.4?

We know it's sf 1.3 without the deprecated stuff, but will they be released together or we'll have to wait after november 30th for the cleaning up process? I'm about to start a new important project, and I would like to use 1.4 from the start (of course knowing that 1.3 will be the same, but you know... :) ).
@lloyd27,
I think we will do it like that: release 1.3. clean up trac and documentation a bit, and then start removing the deprecated stuff. So I guess mid december?
@M: PEAR channel has been fixed now.
@fabien

By trying to install symfony over pear using the command

# pear install -f symfony/symfony-beta

it will install the symfony beta1!

The installation by using the command

# pear install -f symfony/symfony-1.3.0BETA2

it will install the symfony-1.3.0ALPHA2.tar!
@fabien

Thanks, it works fine now.

Now I need to figure out why my fixtures are not compatible with yaml 1.2.
I narrowed the problem with yaml upgrade to this code
<?php for($i = 1; $i <= 9; $i++): ?>
test<?php echo $i ?>:
[snip]
<?php endfor; ?>

What's wrong with it?
It's beautiful. I made the switch from 1.0 to 1.3 last month in preparation for 1.4, and I've been overwhelmed at how much better everything's gotten. The diff-based database migrations are a dream come true!

The only issue I've encountered (and it *might* be my code, somehow) is that when I did the upgrade from 1.2 to 1.3beta1, my pageloads got a lot slower. e.g. 360ms up from 46ms on a fully cached, optimized page. It's still pretty fast, but that seems like a heck of a speedbump.
Well whatever was causing the speedbump seems to be gone now. Back down to about 55ms per request. Ignore me! :)
This looks like a symfony bug to me. Would you please have a look at this exceptions?

exception 'InvalidArgumentException' with message 'Unable to parse line 11 ( test:).' in /usr/share/pear/symfony/yaml/sfYamlParser.php:243
Stack trace:
#0 /usr/share/pear/symfony/yaml/sfYaml.php(96): sfYamlParser->parse('sfGuardUser:? ...')
#1 /usr/share/pear/symfony/task/project/upgrade1.3/sfYamlUpgrade.class.php(44): sfYaml::load('sfGuardUser:? ...')
#2 /usr/share/pear/symfony/task/project/sfUpgradeTo13Task.class.php(52): sfYamlUpgrade->upgrade()
#3 /usr/share/pear/symfony/task/sfBaseTask.class.php(67): sfUpgradeTo13Task->execute(Array, Array)
#4 /usr/share/pear/symfony/task/sfTask.class.php(97): sfBaseTask->doRun(Object(sfCommandManager), NULL)
#5 /usr/share/pear/symfony/command/sfSymfonyCommandApplication.class.php(76): sfTask->runFromCLI(Object(sfCommandManager), NULL)
#6 /usr/share/pear/symfony/command/cli.php(20): sfSymfonyCommandApplication->run()
#7 /usr/bin/symfony(37): include('/usr/share/pear...')
#8 {main}exception 'InvalidArgumentException' with message 'Unable to parse string: Unable to parse line 11 ( test:).' in /usr/share/pear/symfony/yaml/sfYaml.php:101
Stack trace:
#0 /usr/share/pear/symfony/task/project/upgrade1.3/sfYamlUpgrade.class.php(44): sfYaml::load('sfGuardUser:? ...')
#1 /usr/share/pear/symfony/task/project/sfUpgradeTo13Task.class.php(52): sfYamlUpgrade->upgrade()
#2 /usr/share/pear/symfony/task/sfBaseTask.class.php(67): sfUpgradeTo13Task->execute(Array, Array)
#3 /usr/share/pear/symfony/task/sfTask.class.php(97): sfBaseTask->doRun(Object(sfCommandManager), NULL)
#4 /usr/share/pear/symfony/command/sfSymfonyCommandApplication.class.php(76): sfTask->runFromCLI(Object(sfCommandManager), NULL)
#5 /usr/share/pear/symfony/command/cli.php(20): sfSymfonyCommandApplication->run()
#6 /usr/bin/symfony(37): include('/usr/share/pear...')
#7 {main}>> yaml Unable to upgrade SF_ROOT_DIR/data/fixtures/100_profiles.yml

Regards,
Michal8
as usual, discussion about bugs are better placed on the mailing list. If you found a bug reporting it on trac would be preferred
Ok, I filled a bug report in a track and send email to symfony-dev.

Regards,
Michal
Alright! The final release is on my birthday! Nice present. :-D

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.