• Kris Wallsmith
• 5 months ago
• Releases
• 23

The symfony team is happy to announce the immediate availability of symfony 1.3 beta 1! We have made a number of enhancements since 1.3 alpha 2 went out, just two weeks ago, which are described below.

Along with designating the 1.3 branch with beta status, we are now shifting our focus from enhancing the framework to shoring up its stability. This means the API is locked and you should feel free to begin testing your existing projects against the 1.3 codebase (we encourage you to do so!). Instructions for upgrading a symfony 1.2 project can be found in the upgrade tutorial.

Cascading Plugin Schemas

You can now modify schemas defined in Doctrine plugins using the same principle of a configuration cascade used throughout symfony. No need to create a specially named file or designate a particular package, just add the model you want to modify to your schema file and your definition will be merged into the plugin's. As an added benefit, this cascade also allows one plugin to extend the schema from another.

Is your markup valid?

Wait, let us answer that for you. We've added a new method to the functional test framework that will make sure you are sending a well-formed response. You can even ask symfony to validate your response against its document type.

You say builders, I say behaviors

The custom builders that symfony has relied on to extend Propel since the beginning have been ported to Propel 1.4's new native behaviors system. This means you now have full access to the power of Propel behaviors without any interference from symfony's builders.

IDE-Friendly

Generated form and Doctrine model classes are now marked up with type-hinting comments to help your IDE of choice provide more powerful code-completion. Lazy fingers rejoice!

Colorful Windows

If you've installed ANSICON on your Windows box, symfony now colorizes its CLI output for your visual pleasure.

These are just the major enhancements added since 1.3 alpha 2 was released two weeks ago. A complete description of what symfony 1.3 brings can be found in the What's New documentation.

What's Next?

Like I mentioned above, the core team is now focusing its attention on the stability of the 1.3 branch. This means that now is the optimial time for you to upgrade one of your projects and submit any issues you find to Trac. The first Release Candidate will be out in another two weeks, which will be here before you can say "backslash," so please test your code against symfony 1.3 beta 1 sooner than later.

Comments

• 

  #1 lukas said 36 minutes later

  Thanks again team for this release!!!

  I got an error.. generating the forms..

  C:\desarrolloweb\sfprojects\desarrollosur>symfony propel:build-form
  >> propel generating form classes

  Parse error: syntax error, unexpected T_FOREACH, expecting T_FUNCTION in C:\desarrolloweb\sfprojects\desarrollosur\plugins\sfGuardPlugin\lib\model\om\BasesfGuardGroupPermissionPeer.php on line 1227

  What's up ?? tanks in advance Kris.
  

• 

  #2 Matias said about 2 hours later

  Is there a new link for ANSICON? Geocities has this message: GEOCITIES IS CLOSING ON OCTOBER 26, 2009.
  New GeoCities accounts are no longer available. :)

• 

  #3 Kris said about 3 hours later

  @Matias - thanks for the heads up, I've updated the link

• 

  #4 Jonathan Nieto said about 4 hours later

  Excellent work guys!!!,
  I'd like to test it right away, but I think I have to wait until weekend! :D

• 

  #5 kendoctor said about 6 hours later

  great news!
  by the way, ask something for 1.2x
  could i generate fixtrue data by cli from exisiting database data ?
  

• 

  #6 Marijn Huizendveld said about 6 hours later

  1.3 Is shaping up to be a very nice release if you ask me:-)
  And for everybody who would like to incorporate mark-up validation in projects but cannot use 1.3, I wrote a plugin for markup validation a few months ago (http://www.symfony-project.org/plugins/rsfResponseValidatorPlugin) it can easily be incorporated within existing unit tests. The plugin connects to the W3.org validator but can also use a local instance of the W3.org validator.

• 

  #7 M said about 9 hours later

  Hi,

  I have a problem with download from pear channel

  [root@ozzy ~]# pear download symfony/symfony-1.3.0BETA1
  Failed to download symfony/symfony, version "1.3.0BETA1", latest release is version 1.3.0ALPHA2, stability "alpha", use "channel://pear.symfony-project.com/symfony-1.3.0ALPHA2" to install
  Cannot initialize 'symfony/symfony-1.3.0BETA1', invalid or missing package file
  Package "symfony/symfony-1.3.0BETA1" is not valid
  download failed
  

• 

  #8 Stephen Melrose said about 9 hours later

  Lack of auto-complete in the IDE with Doctrine is the one thing that kept me from moving to it.

  I'm certainly going to give it a go now we have this support. Thank you!

• 

  #9 xplo said about 10 hours later

  The beta seems broken with Propel, it was ok with alpha2.

  It cannot build model because of syntax error when adding something like that

  // symfony_behaviors behavior
  foreach (sfMixer::getCallables('BaseTable:doUpdate:post') as $sf_hook)
  {
  call_user_func($sf_hook, 'Table', $values, $con, $ret);
  }

• 

  #10 Fabien said about 10 hours later

  @M: I have fixed the PEAR channel. You can retry by first clearing your local PEAR cache with:

  pear clear-cache

• 

  #11 Stefan said about 10 hours later

  And if you want to contribute to symfony 1.3, feel free to join the symfony BugHuntDay! Check the earlier blog post about this :)

• 

  #12 Raphael said about 11 hours later

  Great, thanks for the fast progress on SF1.3, it's impressive.

  I have a question for clarification on the plugin repository on this site, is it planned to extend it to explicitly identify 1.3-compatible plugins?
  I guess that while the vast majority of SF1.2-compatible plugins would be forward compatible to SF1.3 as they are today already, there are some which aren't, e.g. due to changes on YAML parser.

  Cheers RAPHAEL

• 

  #13 M said about 13 hours later

  @ Fabien

  Thanks!

• 

  #14 Fabian Lange said about 14 hours later

  I just want to ask you to discuss upgrading problems on the developer mailing list. Or if there are clear bugs open a ticket.
  Comments here are likely to be forgotten soon.

• 

  #15 Fabien said about 16 hours later

  @Raphael: I have just added a new 1.3 section to the plugin section.

• 

  #16 Raphael said about 17 hours later

  Wow... great! :-) Merci et salut's RAPHAEL

• 

  #17 FWH said 1 day later

  Any chance of bug #6651 being fixed for symfony 1.3 ? http://trac.symfony-project.org/ticket/6651

  It's been opened for 4 months and there's not been any update.

  Thanks in advance,

  FWH

• 

  #18 Austin said 2 days later

  I get this message when I type in "pear install symfony/symfony-1.3.0BETA1" my command line:
  "symfony/symfony is already installed and is newer than detected released version 1.3.0BETA1"

  I am using symfony 1.3.0ALPHA2 at the moment.
  

• 

  #19 Alex said 5 days later

  Hm.. when i try to download ANSICON, Kaspersky antivirus say that file http://adoxa.110mb.com/ansicon/ansi122.zip/ansicon.exe

  contain a virus HEUR:Trojan.Win32.Invader

  Any body already use ANSICON?

• 

  #20 Jasper Lammertink said 13 days later

  I have the same problem as xplo.
  I get a error when i try to generate form or filter classes.

  Parse error: syntax error, unexpected T_FOREACH, expecting T_FUNCTION in MY_FILE on line MY_LINE

  I couldn't find anything about this so am wondering if this has been looked at already?

• 

  #21 LKS said about 1 month later

  I got an error.. generating the forms..

  >> propel generating form classes

  Parse error: syntax error, unexpected T_FOREACH, expecting T_FUNCTION in D:\xamp
  p\htdocs\prof\lib\model\om\BaseJobeetAffiliatePeer.php on line 566

  i tried in symfony 1.3 and 1.4 how can be possible ? they are a lot of comments about this old bug , you made a new release !!! with the same bug !

• 

  #22 Tom said about 1 month later

  Hi, I've got the some problem like lukas with sfGuard plugin. When I was upgradeing my project from 1.2.8 to 1.3.0 and after typeing "symfony propel:build --all-classes", and starting it, i saw "Parse error: parse error, expecting `T_FUNCTION' in D:\Programy\wamp\www\new\pracus\plugins\sfGuardPlugin\lib\model\om\BasesfGuardUserPeer.php on line 593".

  How can I get fix this error?

• 

  #23 arrow3215 said about 1 month later

  @lukas
  see
  http://trac.symfony-project.org/ticket/7769#comment:1
  and
  http://forum.symfony-project.org/index.php/t/23802/