symfony on SWiK

A week of symfony #88 (1->7 september 2008)

Sun, 07 Sep 2008 14:59:42 -0700

Symfony continued this week adding cool new features for the upcoming 1.2 version. The routing framework will be refactored to allow further customization and complete RESTful architecture. In addition, Propel plugin development showed an immense activity during this week.

Development mailing list

Discussions about how to handle email sends in 1.1 plugin and sf1.1 / sfForm / FCKeditor widget

Development highlights

r11274, r11276: [1.1, 1.2] added a way to set the "value" attribute value of a checkbox
r11277: [1.2] removed getMethodName() usage in core + changed deprecated log to a warning
r11278, r11279: [1.1, 1.2] renamed valueAttributeValue to value_attribute_value (coding standard and api consistency)
r11280, r11281: [1.1, 1.2] fixed sfCacheClearTask: clear all type if not defined app
r11286: [1.2] removed log messages that do not give valuable information
r11287: [1.2] removed log from sfWebRequest
r11293: [1.2] removed the application name as an argument for Propel task in favor of an optional option
r11297, r11298: [1.1, 1.2] fixed parsing of star parameter creating empty param
r11301: [1.2] added confirmation when inserting the SQL statements
r11313: [1.2] First part of the routing refactoring (WIP)
r11319: [1.2] renamed method_name to method in the routing context
r11338: [1.1, 1.2] fixed sfBaseTask so that it notifies the same event as sfTask
r11339: [1.2] fixed Propel Peer classes guessing
r11341: [1.2] allow a task alias to be a fully qualified name (with a namespace)
r11343: [1.2] rename propel:generate-crud to propel:generate-module
r11344: [1.2] added support for PUT and DELETE for the link_to() helper
r11347: [1.2] moved extra parameters from routing to request attributes
r11349: [1.2] fixed default form format name when generating a CRUD module
r11353: [1.2] added support for PUT and DELETE methods to the form_tag() helper
r11354: [1.2] added false as a value that removes the attribute from a widget tag
r11356: [1.2] added sfForm::renderFormTag() method
r11361, r11362: [1.1, 1.2] fixed cloning of widgetformschema fails to clone formatter correctly
Updated dwhittle branch
...and many other changes

Development digest: 107 changesets, 30 defects created, 15 defects closed, 5 enhancements created, 1 enhancement closed, 6 documentation defects created, 8 documentation defects closed and 17 documentation edits.

Book and documentation

Created Symfony YAML MySQL Workbench Plugin page
Updated contributing to Symfony with SVK, Upgrade to 1.2 pages

Wiki

New symfony blogger:
- Obvious Hints (website, feed)

Plugins

New plugins
- sfHtml2TextPlugin: provides an abstraction and autoloading of html2text class
- sfPHPUnitTestPlugin: unit/functional testing replacement for symfony
- sfStatisticsPlugin: an easy-to-use tool for reports (chart and data table) creating based on the Propel Model through Google Chart API
- tbFriendfeedClientPlugin: a FriendFeed client plugin
Updated plugins
- sfPropelPlugin:
  - [migration]: added index size parameter and ->unique() convenience method to column abstraction class, normalized sfPropelIndex::asPropel() signature, added ->getCreateIndexStatement() to DDL builder extensions, reorganized sfPropelBaseTask for better reusability, added sfWidgetFormPropelSelectRadio.class.php, added prove.php test script to run all plugin tests, removed transaction from sqlite drop column statement in favor of PDO::beginTransaction(), added ->create() and ->drop() terminator methods to model abstraction classes, removed DDL builder class from propel.ini to avoid an unnecessary upgrade step, added convenience create/add and drop methods to column and index abstraction classes that accept a string table name parameter, ported recognition of special column names from sfPropelDatabaseSchema to abstraction layer, added sfPropelTable::columns() to facilitate prettier code, added migration class for creating migration log table, added static propel model classes for migration log table, added autoIncrement attribute to fixture statements, rewrote base migration and manager classes to handle namespaces, added sfPropelMigrationSchema class for acting upon a collection of migration classes, updated migration tasks to use new manager and schema classes, moved migrations from project/plugin data to lib directory, removed propel.ini directive to disable migrations, improved DRY in builder and model abstraction layer, added test suite, updated migration log table, model classes and migration, updated execution of a collection of SQL statements to ignore exceptions per Propel's example, addressed MSSQL drop table bug, fixed how migration schema builds its revision range, added confirmation to backward migration of the migration namespace, changed all application arguments to options, added autoload registration for bundled plugin model directory, eliminated use of sfProjectConfiguration::getActive() where possible, eliminated use of sfSimpleAutoload where possible, added some helpful error messages
  - [behavior]: added sfWidgetFormPropelSelectRadio.class.php, removed the application name as an argument for Propel task in favor of an optional option
  - [trunk]: removed the application name as an argument for Propel task in favor of an optional option, added confirmation when inserting the SQL statements, fixed Propel Peer classes guessing, rename propel:generate-crud to propel:generate-module, fixed default form format name when generating a CRUD module, made form class name customizable in the CRUD generator, changed the default list variable name in the generated CRUD module, added sfForm::renderFormTag() method
- smFaceliftPlugin: converted the included files into classes
- sfDoctrineGuardPlugin: moved signin form to allow override, added translation to signin template
- sfPropelAuditPlugin: created folder for symfony 1.0 releases and restored previous releases (1.0.0 and 1.0.1)
- sfLanguageSwitchPlugin: added trunk and tags directories, added branches directory, moved release 0.0.1 to tags directory, rewritten some parts of source, removed some flags, rewritten documentation, added automatic switch for sf 1.0 and 1.1, updated package.xml, released 0.0.2 version
- sfPropelActAsNestedSetBehaviorPlugin: added boolean type cast to match phpdoc function signatures
- ysfYUIPlugin: added note to README about declaring yui-skin-sam class to body tag to get styling working
- sfExtjsThemePlugin: fixed the problem with local grouping, fixed the problem with double sort statements when grouping, removed obsolete Ext.ux.form.Checkbox folder, added new override to fix Checkbox alignment in IE, added new override to add getValue and setValue to RadioGroup, added new override to BoxComponent so button can extend it, added new Ext.ux.BoxButton so Button extends BoxComponent, uses same button xtype, cleaned up actions.class.php in the generator to remove a lot of commented obsolete code
- sfFormtasticPlugin: fixed bug when calling ->renderHiddenFields() on a form with an error schema

Some new symfony powered websites

Social Group Buy: (english) social shopping service allowed to organize and execute buying groups
LifeJack: ebay-like site for life assurances
ullright: (english) framework and application suite providing helpful tools to support workflows and company-internal administration/organisation in general
Zamanzar: (english) real estate portal with thousands of Indian real estate listings
Animalo.pl: (polish) an online community for Pet Owners

They talked about us

sfshop - Google Code

Sun, 07 Sep 2008 06:01:18 -0700

sfShop is Open Source online shop e-commerce platform. This platform can use anybody for build online shop e-commerce solution. The paltform is available for free under the MIT License and any developer can take part in development.

Call the expert: How to implement a conditional validator?

Fri, 05 Sep 2008 06:07:30 -0700

Jon works on a symfony 1.1 project with a classic login form.

The form is composed of two fields: a username and a password. The validation rules are quite straightforward:

He wants each field to be required
He wants to check the correctness of the password

Here is the first implementation of the login form:

class loginForm extends sfForm
{
  public function configure()
  {
    $this->setWidgets(array(
      'username'  => new sfWidgetFormInput(),
      'password'  => new sfWidgetFormInputPassword(),
    ));
 
    $this->setValidators(array(
      'username' => new sfValidatorString(array('required' => true)),
      'password' => new sfValidatorString(array('required' => true)),
    ));
 
    $this->widgetSchema->setNameFormat('login[%s]');
  }
}

This form enforces the requirements on the username and password fields but does not check the correctness of the password.

The password can only be validated if you also have access to the username value. But as you might know, a validator attached to a field does not have access to the other values of the form.

When a validator relies on another submitted value, you need to create a post validator. A post validator is executed after all other validators and is given the whole array of cleaned up values.

To check the password, we will implement a simple callback validator to ensure that the submitted password is equal to the username. Of course, for his real project, Jon will have to call the model layer to do the actual work.

Here is the modified login form with the added post validator:

class loginForm extends sfForm
{
  public function configure()
  {
    $this->setWidgets(array(
      'username'  => new sfWidgetFormInput(),
      'password'  => new sfWidgetFormInputPassword(),
    ));
 
    $this->setValidators(array(
      'username' => new sfValidatorString(array('required' => true)),
      'password' => new sfValidatorString(array('required' => true)),
    ));
 
    $this->widgetSchema->setNameFormat('login[%s]');
 
    // add a post validator
    $this->validatorSchema->setPostValidator(
      new sfValidatorCallback(array('callback' => array($this, 'checkPassword')))
    );
  }
 
  public function checkPassword($validator, $values)
  {
    if ($values['password'] != $values['username'])
    {
      // password is not correct, throw an error
      throw new sfValidatorError($validator, 'Invalid password');
    }
 
    // password is correct, return the clean values
    return $values;
  }
}

Now, the form works as expected, but Jon does not like one small thing: if you submit a random password without entering a username, you will have two error messages: a required error for the username and a global error for the wrong password.

But wait a minute, if the username is empty, we don't need to validate the password. Let's change the form to only validate the password if there is a username submitted. This is quite simple, as we just need to ensure that $values['username'] is not empty in the post validator callback:

public function checkPassword($validator, $values)
{
  // before validating the password, check that the username is not empty
  if (!empty($values['username']) && $values['password'] != $values['username'])
  {
    throw new sfValidatorError($validator, 'Invalid password');
  }
 
  return $values;
}

As Jon is quite fussy, he would rather have the 'Invalid password' error message just above the password field instead of having a global error.

That's quite easy to accomplish by throwing an error bound to the password field instead of throwing a global error:

public function checkPassword($validator, $values)
{
  if (!empty($values['username']) && $values['password'] != $values['username'])
  {
    $error = new sfValidatorError($validator, 'Invalid password');
 
    // throw an error bound to the password field
    throw new sfValidatorErrorSchema($validator, array('password' => $error));
  }
 
  return $values;
}

Jon is now happy with his login form and he is ready to take up the next challenge.

http://www.steercms-project.org/

Thu, 04 Sep 2008 08:58:32 -0700

symfony | Web PHP Framework | Plugins | dgDojoPlugin | 0.1.1

Thu, 04 Sep 2008 05:59:45 -0700

New in symfony 1.2: Toward a RESTful architecture (Part 1)

Wed, 03 Sep 2008 23:54:34 -0700

Yesterday, I have committed the first slew of changes to the routing framework. Thanks to this refactoring, developers have new opportunities to customize the routing and this will allow very cool features in the very near future.

But today, let's dive into the goodness of the symfony 1.2 routing framework.

Routes as first-class objects

Before symfony 1.2, the routing system (via the sfPatternRouting class) stored its routes as an associative array. It works quite well but does not allow for easy customization. To give developers the freedom to easily enhance the routing process, the routes are now stored as an array of sfRoute objects.

This refactoring is totally backward compatible and nothing need to be changed in your routing.yml configuration file.

If you connect your routes with PHP code, you must now pass a sfRoute instance as the second argument to the connect(), preprendRoute(), appendRoute(), and insertRouteBefore() methods:
$routing->connect('foo_bar', new sfRoute('/foo/:bar', array('module' => 'foo', 'action' => 'bar')));
 

Route customization

The sfRoute constructor takes an array of options as its last argument to allow the customization of each route. In the routing.yml configuration file, use to options key to override defaults:

article:
  url:     /article/:id-:slug
  options: { segment_separators: [/, ., -] }

The segment_separators option sets the characters that can separate each segment of the pattern. In the previous example, we explicitly add the - (dash) character as a valid separator to the two default built-in separators (/ and .). This allows a URL like /article/1-my_article_title to match the route with an id variable of 1 and a slug variable of my_article_title.

This option was already available in symfony 1.1, but you were only allowed to change it globally. By adding new separators globally, you could have potentially broken third-party routes (like the ones defined in plugins).

Beside the options already available, there are two new options:

generate_shortest_url: Whether to generate the shortest URL possible
extra_parameters_as_query_string: Whether to generate extra parameters as a query string

These options can be configured globally for the routing or locally for each route. By default, they are set to false in factories.yml to keep backward compatibility with previous symfony versions.

Let's see how to use these options to customize a route:

articles:
  url:     /articles/:page
  param:   { module: article, action: list, page: 1 }
  options: { generate_shortest_url: true }

This route will generate the shortest URL possible. So, if you pass a page of 1, which is the default value for the page variable, the generated URL will be /articles:

echo url_for('@articles?page=1'); // generates /articles
// would have been /articles/1 in symfony 1.1
 
echo url_for('@articles?page=2'); // generates /articles/2

Let's take another example to illustrate extra_parameters_as_query_string usage:

articles:
  url:     /articles
  options: { extra_parameters_as_query_string: true }

This route will accept extra parameters that are not valid variables for the route and add them as a query string:

echo url_for('@articles?page=1'); // generates /articles?page=1
// would not have matched the route in symfony 1.1
 
echo url_for('@articles?page=2'); // generates /articles?page=2

As this option can change the matching route depending on your configuration, enable it with care if you are upgrading an existing project. But as the test browser uses the routing process, you will just have to launch your functional test suite to check if it breaks something.

Routing customization

All the logic from the sfPatternRouting routing class has been moved to the sfRoute object:

When an HTTP request comes in, the routing object asks each route in turn if it matches the URL.
And when you want to generate a URL, the routing object asks each route in turn if it is able to generate a URL for the given parameters.

By embarking all the logic in the route class, it is just a matter of creating a new route class to change the behavior of the parsing or generation process.

If you want to change the default route class used by a route, add a class key to your route configuration like this:

article:
  url:   /article/:id
  param: { module: article, action: index }
  class: myRoute

With this routing configuration, symfony will use the myRoute class for the article route, instead of the built-in sfRoute class. It is now up to you to override the default behaviors.

The sfRoute class is much more modular than the old sfPatternRouting class to allow easier customization of the default behavior. The "compilation" phase has been refactored into smaller methods, the code has been simplified, and it is now based on a "real" tokenizer.

The built-in `sfRequestRoute`

Symfony has another built-in route, sfRequestRoute, which can enforce the HTTP method during the matching process:

article:
  url:          /article/:id
  requirements: { sf_method: get }
  class:        sfRequestRoute

With the previous routing configuration, the article route will only match requests with a GET HTTP method.

If you define several routes with the same url but different method requirements, you can pass sf_method as a parameter when you generate a route:

<?php echo link_to('Great article', '@article?id=1&sf_method=get')) ?>

This is made possible because the routing is now aware of the request context. When the request calls the routing, it passes the following context:

method: The HTTP method
format: The request format
host: The hostname
is_secure: Whether the request was called with HTTPS or not
request_uri: The full request URI
prefix: The prefix to add to each generated route

The sfRequestRoute is the first step towards a RESTful architecture.

What's next?

In the next part, we will see how symfony manages resources by automatically generating RESTful routes based on a simple configuration of routing.yml. We will also learn how to cut the code you have to write in your actions, thanks to the built-in integration of Propel and Doctrine.

Last but not least, I will talk about the new routing framework at symfonyCamp with even more examples and a live demo. So, if you want to learn more about symfony 1.2 and if you are not already registered, you can still join the 60 people who will be there to share their symfony experience.

If you want to follow the progress of symfony 1.2 or if you want to know all the changes we have made for symfony 1.2, you can periodically check the upgrade to symfony 1.2 page where all changes and news features are documented in real-time.

symfony trac

Wed, 03 Sep 2008 02:01:02 -0700

New in symfony 1.2: Small things matter

Tue, 02 Sep 2008 12:55:34 -0700

As for every symfony version, we try to simplify the API and make it more intuitive and powerful. Here are some examples that you will soon enjoy in symfony 1.2.

Application name in CLI tasks

Some Propel tasks take an application name as an argument because they need to connect to the database. This is sometimes counter-intuitive as some other Propel tasks do not require this argument.

As of symfony 1.2, this argument has been removed in favor of an optional "application" option. If you don't provide the "application" option, symfony will take the database configuration from the project databases.yml file, which is the behavior you expect most of the time.

The propel:build-all-load now behaves like any other propel:build-* task:

# symfony 1.2
./symfony propel:build-all-load
 
# symfony 1.1
./symfony propel:build-all-load application_name

You can also load data fixtures or dump your database to YAML with the following commands:

./symfony propel:data-load
./symfony propel:data-dump

Of course you can still provide an application if you need a specific configuration:

./symfony propel:buil-all-load --application=frontend

Native `PUT` and `DELETE` support from the browser

You can now simulate PUT and DELETE requests from a browser by using the POST method and by adding a special sf_method hidden parameter:

<form action="#" method="POST">
  <input type="hidden" name="sf_method" value="PUT" />
 
  <!-- // ... -->
</form>

With such a form, a call to sfRequest::getMethod() will return PUT. Stay tuned for more new features that will enable easy and native RESTful applications in symfony.

Shortcuts in the response

Sometimes, you need to get the stylesheets or the JavaScripts from the current response. But the getStylesheets() and getJavascripts() method returns the internal representation of the information, which is not what you expect.

As of symfony 1.2, these two methods return the information in a ready-to-be-used, de-duplicated, and ordered format:

array(
  'bar.css' => array(),
  'foo.css' => array(),
)

`sfValidatorSchemaCompare` validator

The sfValidatorSchemaCompare constant values have been changed. The following two examples are now equivalent:

// symfony 1.1 and 1.2
$v = new sfValidatorSchemaCompare('left', sfValidatorSchemaCompare::EQUAL, 'right');
 
// symfony 1.2 only
$v = new sfValidatorSchemaCompare('left', '==', 'right');

The new one is much more readable and intuitive.

Symfony-Zone " Developing Symfony with Eclipse

Mon, 01 Sep 2008 16:59:32 -0700

http://download.eclipse.org/tools/pdt

Symfoclipse

Mon, 01 Sep 2008 13:58:53 -0700

SymfonyWithEclipseBasedEditors - symfony - Trac

Mon, 01 Sep 2008 12:59:59 -0700

Best Symfony IDE: Eclipse PDT + Symfoclipse + Clay | Symfony-framework.com

Mon, 01 Sep 2008 12:59:59 -0700

Symfoclipse

Mon, 01 Sep 2008 11:59:36 -0700

Symfoclipse - Symfony Development Tools for Eclipse | Poetry of Programming

Mon, 01 Sep 2008 01:59:32 -0700

SourceForge.net: uml2symfony

Sun, 31 Aug 2008 15:56:06 -0700

ejemplos uml - symfony-es

Sun, 31 Aug 2008 15:56:06 -0700

A week of symfony #87 (25->31 august 2008)

Sun, 31 Aug 2008 14:54:04 -0700

This week, the refactorization of the web debug toolbar was completed, resulting in a much more powerful and flexible tool. In addition, this week started the refactorization of the admin generator, which will include ideas suggested by symfony users. Development activity of the plugins was also remarkable, especially for sfPropelPlugin and DbFinderPlugin.

Development mailing list

Discussions about model-Level validation

Development highlights

r11089: [1.2] added a sfWebResponse::ALL constant to be able to retrieve all javascripts and stylesheets without the position
r11096: [1.1, 1.2] fixed default propel.ini file in the sandbox
r11098: [1.2] fixed the behavior of the removeJavascript() and removeStylesheet() methods
r11102: [1.2] changed the default position to sfWebResponse::ALL for the getStylesheets() and getJavascripts() methods
r11116: [1.2] refactored browser and functional test classes
r11121: [1.2] moved web debug toolbar from to for better readability of the source
r11129: [1.1, 1.2] fixed sfWidgetFormPropelSelect rendering in a view has different behaviours depending on how it is called
r11153, r11155: [1.1, 1.2] fixed sfWidgetFormSchema does not apply id_format to hidden fields
r11164: [1.2] changed the sfWebDebugPanel method names
r11166, r11167: [1.1, 1.2] fixed sfWebRequest::getRequestFormat does not handle latest webkit
r11173: [1.2] removed creole dependencies
r11202: [1.2] added the possibility to pass an array to url_for() and link_to() with the route name
r11205: [1.2] moved Propel web debug panel to the Propel plugin
r11254: [1.2] added support for PUT and DELETE methods from a browser
Updated dwhittle branch
...and many other changes

Development digest: 173 changesets, 26 defects created, 16 defects closed, 7 enhancements created, 4 enhancements closed, 7 documentation defects created, 12 documentation defects closed and 72 documentation edits.

Book and documentation

Created How to customize the Web Debug Toolbar cookbook tutorial
Created Admin Generator 1.2 Sprint Notes page
Updated Reserved words, Symfony 1.2 Admin Generator Development, applying custom joins using a helper class pages
Updated My First Project tutorial for symfony 1.1

Wiki

New Job Postings:
- PHP Application Developer @ Current - full-time based in SOMA, San Francisco, CA - Contact: ctower [at] currentmedia [dot] com
New developers for hire:
- Sierra Bravo: founded in 2003 and the largest independent web development firm in Minnesota, with more than 50 programmers on staff. Sierra Bravo creates practical, business-minded web solutions, including social media and Web 2.0 applications, e-commerce, content management systems, and customer relationship management tools.
New symfony blogger:
- symfonylab.blogspot (website, feed)

Plugins

New plugins
- sfVideoGalleryPlugin: dynamic video gallery plugin. The video gallery can be attached with any object of the database. So it is quite flexible in nature to adopt and contain the video files with any existing object. It also include ffmpeg converter so that the user can upload videos in any format which will be automatically converted into flv format.
- Upcoming plugins: sfMilkboxPlugin, trShopPlugin
Updated plugins
- sfPropelPlugin: added Propel model classes for migration log, added propel.ini directive to disable migrations, [1.3] restored sfMixer-style behaviors, connect phing build events to sfEventDispatcher, [migration branch] ported phing to symfony events, exposed build properties to propel tasks, modified base propel task to include schema files from bundled plugins, implemented propel.disableMigrations build property, fixes for sfFormPropel + sfWidgetFormPropelSelect, [1.2] removed the migration stuff, [migration] sketched out API for expansion of migration tasks to support namespaces, added beginnings of fluid interface for database-agnostic migrations, moved FK logic into column class, added single-column index method to column class, added phpdoc comments, added sfPropelTable::asCreateTableSql(), migration model ->unwrap() methods now clone the internal object, moved creation of Propel object from constructor to terminators, removed magic layer in favor of an explicit API, extended Propel's DDL builder classes, added drop table support to abstraction layer, added drop index support to abstraction layer, added support for create and drop column to abstraction layer
- sfMinifyPlugin: added 1.1 branch, updated README
- sfFormExtraPlugin: added CHANGELOG, updated README, updated package.xml
- sfPhpExcelPlugin: upgraded to PHPExcel 1.6.3
- sfExtjsThemePlugin: re-implemented row expander, changed Ext.ux.grid.CheckColumn to trigger the fire grid afteredit event, added editable check to Ext.ux.grid.CheckColumn? so it can be turned off (default is on), added check for expand_column.fields so it will be automatically added to the datastore, fixed a bug with partial generation not setting the file editable, implemented credentials for editing gridpanels, moved some things from the partial into the generator for the list/grid plugin config, improved configurability of grid.columns.editable, started fixing grouping
- DbFinderPlugin: implemented sfDoctrine::withColumn(), partially implemented getColumn() getter (currently limited by Doctrine capabilities), implemented sfDoctrine::groupBy() and sfDoctrine::groupByClass(), [BC Break] withColumn() now accepts normal CamelCase syntax for calculated columns (count(Comment.Id) instead of count(comment.ID)), implemented sfDoctrineFinder::set(), sfDoctrineFinder::paginate() and sfDoctrineFinderPager, reorganized files into adapter folders, implemented sfDoctrineFinder::withI18n() which completes Doctrine adapter, released 0.9 version
- sfAmfPlugin: added Doctrine support, added PropelAdapter.php, fixed bugs in package.xml, adding annotation support for @AmfIgnore and @AmfClassMapping, added the AmfReturnType annotation
- sfFirePHPLoggerPlugin: updated readme
- sfMediaLibraryPlugin: made the plugin compatible with both 1.0 and 1.1
- sfFormtasticPlugin: fixed sfFormtasticBase::setIdFormat(), cleaned up render methods for better DRY
- sfMogileFSPlugin: updated package.xml, made listKeys() arguments optional
- sfPropelPollsPlugin: fixed package.xml
- sfSimpleBlogPlugin: changed calls to DbFinder::withColumn() to be compatible with DbFinder change, released 0.9.1 beta version
- sfDoctrinePlugin: updated Doctrine to 1.0.0-RC2 tag

Some new symfony powered websites

Car Hire Florida: (english) offering competitive car hire to UK holidaymakers staying in Florida, USA.
Volume One: (english) web version of popular local magazine
Kuidas.ee: (estonian) how to do stuff instructions. Do It yourself

They talked about us

symfony | Web PHP Framework

Sat, 30 Aug 2008 16:56:59 -0700

symfony | Web PHP Framework

Fri, 29 Aug 2008 05:57:05 -0700

Framework do php para desenvolvimento com ajax simples e rápido

HowToInstallPearOnWindowsWithWamp - symfony - Trac

Thu, 28 Aug 2008 18:06:54 -0700

Propel 1.3, Doctrine 1.0, and symfony 1.2

Thu, 28 Aug 2008 18:01:35 -0700

After more that two years of development, the Propel team has released Propel 1.3 yesterday. This is a great achievement as Propel 1.3 sports a lot a new exciting features. Here are some major features available in this version:

PDO: Propel 1.3 uses PDO to connect to the database which means that everything will be much faster than before.
Object Instance Pooling: For a given primary key, only one object instance will ever exist even with several calls to retrieveByPK() or doSelect*() (it's not an Identity Map because the database request is still needed).
Date Handling: The support has been improved by using the PHP 5.2 built-in DateTime class, which also means that Propel 1.3 supports pre/post Epoch dates natively.
Default Values: You can now use expressions (like CURRENT_TIMESTAMP) for default values in your database schema.
and also native support for One-to-One Relationships, Master-Slave connections, Identifier Quoting, Nested Sets, and much more...

Propel 1.3 and symfony 1.2

This is also a great news for symfony as Propel 1.3 will be the default version of Propel bundled with symfony 1.2. Dustin has already upgraded symfony 1.2 to use Propel 1.3. If you can't switch to Propel 1.3 for whatever reason, you will still be able to use Propel 1.2 by installing the sfPropelPlugin.

Dustin will update the UPGRADE_TO_1_2 file in the coming days to highlight the changes you need to do to upgrade to Propel 1.3, but you can start today by reading the excellent upgrade page on the Propel wiki.

As symfony 1.2 is now in active development, the 1.2 branch may be a bit unstable over the next few weeks.

Doctrine 1.0 and symfony 1.2

As announced in the symfony 1.2 roadmap, Doctrine 1.0 will be officially supported and the sfDoctrinePlugin will be bundled with symfony 1.2. Doctrine 1.0 beta1 has been released two weeks ago and the Doctrine team will release Doctrine 1.0 final on September 1st.

I have another great news for the Doctrine community and the symfony community. Jonathan Wage, the lead developer of Doctrine, will start working full-time for Sensio Labs on September 1st. He will spend most of his time working on Doctrine and helping us with the official integration of Doctrine with sfDoctrinePlugin.

A week of symfony #86 (18->24 august 2008)

Thu, 28 Aug 2008 18:01:35 -0700

Symfony 1.2 is due to release in few weeks and therefore its development is accelerating. This week, Propel 1.3 was added as the default Propel version and the web debug toolbar was refactorized. In addition, development of symfony framework achieved 11000th changeset milestone.

Development mailing list

Discussions about symfony logs, required fields and sfForm and rewritten sfPropelPlugin 1.3 behaviors

Development highlights

r10947: [1.0, 1.1, 1.2] fixed sfDomCssSelector attribute regex
r10948: [1.0, 1.1, 1.2] fixed 0000-00-00 dates in mysqli creole driver
r10950: [1.0, 1.1, 1.2] fixed sfBrowser parseArgumentAsArray function discards array indices == 0
r10952: [1.1, 1.2] fixed STDOUT only exists with php-cli
r10964: [1.0, 1.1, 1.2] fixed sfFileLogger file closing
r10970: [1.1, 1.2] fixed default value returned by sfNoCache::get() method
r10971: [1.2] tweaked routing log messages
r10972: [1.2] fixed URL with hyphen is not camelised when converted to action name
r10974: [1.2] tweaked some log messages
r10975: [1.2] upgraded sfPropelPlugin to Propel 1.3
r10976: [1.2] updated skeleton files for pdo dsn syntax
r10977: [1.2] updated ObjectHelper to be compatable with Propel 1.3
r10978: [1.2] updated propel.ini to use 1.1 date/time syntax
r10982: [1.2] added sfFormField::getName()
r10985, r10986: [1.1, 1.2] fixed sfWidget::setXhtml(false)
r10993: [1.2] tweaked test bootstrap cleanup
r11003: [1.1, 1.2] fixed sfValidatorSchemaFilter not throwing an error bound to the filtered field
r11005: [1.2] implemented task for configuring core plugins
r11007: [1.2] renamed sourceDirectory to plugin_dir so that it is aligned with the original plugin_dir
r11019: [1.2] added the possibility for sfBrowser to click on a link or button when several links or buttons exist with the same name
r11020, r11021: [1.0, 1.1, 1.2] fixed sfBrowser doesn't send checked checkedboxes without value attributes correctly
r11034: [1.2] changed exception title to be more explicit + added rounded corner under all browsers that support the feature
r11036: [1.2] added a new sfVarLogger class
r11038: [1.2] simplified sfWebDebug by adding the logger as an argument to the constructor
r11041: [1.2] refactored the web debug toolbar to ease its customization
r11044: [1.2] moved cache debug decoration to the sfViewCacheManager class
r11045: [1.2] refactored the web debug toolbar (WIP)
r11059: [1.2] added sfWebResponse::getCharset() method
r11075: [1.2] removed sf_timer_start constant to compute total time in the web debug toolbar
r11076: [1.2] added a new debug.web.filter_logs event to allow the filtering of logs to be displayed in the web debug toolbar
r11083: [1.2] modified sfWebDebugPanelTimer to listen to the debug.web.load_panels event to remove timers from the logs panel
Updated dwhittle branch
...and many other changes

Development digest: 169 changesets, 25 defects created, 16 defects closed, 7 enhancements created, 3 enhancements closed, 2 documentation defects created, 5 documentation defects closed and 28 documentation edits.

Book and documentation

Created How to Add Custom Filter Criteria to the Admin Generator page
Updated symfony 1.2 admin generator page
Added chapter 8 to the forms book
Updated My First Project tutorial for symfony 1.1

Wiki

New Job Postings:
- Symfony + PHP/XHTML Developer @ Amplify - Job specification - Contact: jobs [at] amplify [dot] com [dot] au
New symfony blogger:
- Franziskus Domig (website, feed)

Plugins

New plugins
- sfExtendedFileValidatorPlugin: extends sfFileValidator to add verification of the height and width of an image sent by a form.
- sfAmfPlugin: allows you to handle AMF requests from Flex frontends
- sfW3studioCmsPlugin: ajax CMS based on symfony
- sfSyntaxHighlighterPlugin: adds automatically the JavaScript code needed to use the SyntaxHighlighter Javascript library
- Upcoming plugins: sfMooToolsPlugin
Updated plugins
- sfPropelAuditPlugin: changes to make plugin compatible with Symfony 1.1
- sfDtAjaxPlugin: added option auto_submit and after_update_element, clear value element when element is cleared, added value_element_value option, added support for onsubmit event when auto_submit option is on
- sfSearchPlugin: repository re-organization to consolidate all search plugins, updated READMEs, [lucene] fixed xfLuceneEngine->empty() method, [lucene] added missing file to test suite, [propel] added hacking notice for Propel 1.3, added check for xfIndex in ->checkIndexExists() task method
- sfLucenePlugin: repository re-organization to consolidate all search plugins, updating package.xml for sfLucene 0.1.7-beta
- sfExtjsThemePlugin: notecolumn changes, added support for local combos in the filter
- ysfDimensionsPlugin: added example for subscribing to user.change_culture event
- sfDoctrineGuardPlugin: fixed wrong column in PluginsfGuardUserTable, fixed misplaced parameter to call call_user_func_array, fixed invalid XHTML code of signin form, removing remaining incorrect foreignType definitions
- sfSwiftPlugin: updated README file
- sfJobQueuePlugin: added sfqueue-first-eligible-job task, no sf logging for sfJobQueue tasks
- ysfYUIPlugin: updated docs, small change to value checking in checkbox widget
- ckWebServicePlugin: updated README to reflect last changes, updated package.xml for new releases, released 1.5.0 and 2.1.0 versions
- sfPropelPlugin: changed svn:externals to use propel 1.3.0 tag, added 1.2 branch (was sfPropelPlugin from symfony 1.1 branch), rewrote behaviors system to utilize sfEventDispatcher maintaining BC with sfMixer-style behaviors, removed sfMixer, connect phing build events to sfEventDispatcher
- sfMogileFSPlugin: released 1.0 version
- sfFeed2Plugin: fixed typo, fixed encoding inside CDATA sections
- sfWebBrowserPlugin: added PUT file support to sfSocketsAdapter
- sfPropelPollsPlugin: added CHANGELOG, fixed package.xml, renamed LICENCE file to LICENSE, added changelog to package.xml file to comply to strict mode
- DbFinderPlugin: implemented sfDoctrineFinder::join(), implemented sfDoctrineFinder::with()
- sfHighlightPlugin: removed test dependency on sfSearch
- sfFormExtraPlugin: added sfValidatorSchemaTimeInterval, a validator to validate the interval between two given dates, and according unit tests
- sfMinifyPlugin: modified svn structure, updates for symfony 1.1, updated README
- sfThumbnailPlugin: added a new method to sfImagemagickAdapter for dealing with custom crop proportions, released 1.5.3 version

They talked about us

symfony Events

Thu, 28 Aug 2008 18:01:35 -0700

The end of the year will be very interesting for the symfony project with a lot of opportunities to meet the community and to learn symfony.

Conferences

I try to attend as much PHP conferences as I can to spread the word about symfony. If you want to meet me and share your experience with symfony, please come to one of the conferences I will speak at in the coming weeks:

23 September (France / Paris - French): Présentation symfony
24-25 September (France / Paris - French): Paris Capitale du Libre
09 Octobre (France / Montpellier - French): symfony presentation
27-31 October (Germany / Mainz - English): International PHP Conference
08-09 December (France / Paris - French): Forum PHP

Trainings

Sensio Labs has been successfully delivering symfony trainings since June 2007 and during that time, we trained more than 300 people all over the world (France, Germany, Italy, USA, Canada, India, Ukraine, Romania, England, Netherlands, ...).

The symfony workshops have proven to be very popular. Today, I am pretty excited to announce two major steps for our workshops. Firstly, the new symfony 1.1 workshops are now available in French and English. Secondly, thanks to the new Sensio Labs offices in the US and in Canada, you can be trained by Sensio Labs in these two countries as well:

symfony 1.0 trainings by Sensio Labs:
- 17-19 September (France / Paris) in French
- 24-26 September (France / Paris) in English
symfony 1.1 trainings by Sensio Labs. Join us for the first symfony 1.1 trainings:
- 22-24 October (France / Paris) in French
- 29-31 October (Canada / Montreal) in English
- 29-31 October (USA / Atlanta) in English
- 19-21 November (France / Paris) in French

The registration for the workshops in the US and Canada are not opened yet, but if you want to be notified when the registration opens, send me an email to fabien.potencier at sensio.com.

You will find even more training dates on the Sensio Labs website. And if you want to organize your very own workshop for your company, please contact us.

The Camp

I have already talked about symfony Camp in this blog but the event is approaching very fast. The registrations are growing day by day, and Lambert, from DOP, told me today that they have two places left for the symfony 1.1 training that will take place on September 11th, just before the camp.

The other two days are packed with great sessions from great speakers! Don't miss this unique opportunity to meet the community.

Which version of symfony for your next project?

Thu, 28 Aug 2008 18:01:35 -0700

With three major symfony versions, newcomers have sometimes a hard time figuring out which version to use for their next project.

To help them choose the right version, I have just updated the symfony project website with a brand new installation page. I also hope IT managers will love the great matrix I have made for them:

The upgrade instructions have also been put online with links available from the main installation page and from each symfony version installation page:

Instructions to upgrade to symfony 1.1
Instructions to upgrade to symfony 1.2

If you are curious and want to know what has already changed in the upcoming symfony 1.2 version, you can read the upgrade page for symfony 1.2. This page is updated in real time whenever a new feature is added to this version.

symfony on SWiK

A week of symfony #88 (1->7 september 2008)

sfshop - Google Code

Call the expert: How to implement a conditional validator?

http://www.steercms-project.org/

symfony | Web PHP Framework | Plugins | dgDojoPlugin | 0.1.1

New in symfony 1.2: Toward a RESTful architecture (Part 1)

Routes as first-class objects

Route customization

Routing customization

The built-in sfRequestRoute

What's next?

symfony trac

New in symfony 1.2: Small things matter

Application name in CLI tasks

Native PUT and DELETE support from the browser

Shortcuts in the response

sfValidatorSchemaCompare validator

Symfony-Zone " Developing Symfony with Eclipse

Symfoclipse

SymfonyWithEclipseBasedEditors - symfony - Trac

Best Symfony IDE: Eclipse PDT + Symfoclipse + Clay | Symfony-framework.com

Symfoclipse

Symfoclipse - Symfony Development Tools for Eclipse | Poetry of Programming

SourceForge.net: uml2symfony

ejemplos uml - symfony-es

A week of symfony #87 (25->31 august 2008)

symfony | Web PHP Framework

symfony | Web PHP Framework

HowToInstallPearOnWindowsWithWamp - symfony - Trac

Propel 1.3, Doctrine 1.0, and symfony 1.2

Propel 1.3 and symfony 1.2

Doctrine 1.0 and symfony 1.2

A week of symfony #86 (18->24 august 2008)

symfony Events

Conferences

Trainings

The Camp

Which version of symfony for your next project?

The built-in `sfRequestRoute`

Native `PUT` and `DELETE` support from the browser

`sfValidatorSchemaCompare` validator