symfony Blog Quotes

Simple bash script to update Symfony2

2012-02-09T17:16:00Z

As you noticed there are frequent maintenance releases of Symfony2, the 2.0.10 version is already out. To avoid doings thing manually I use this simple bash script to make the update: (It works with a Symfony2 standard edition). To use it, just launch the script at the root of your project: (be careful as it will delete your vendor directory)

./update_symfony 2.0.10

The bash script:

See you.

Other related posts;

Une semaine symfonique #266 - du 30 janvier au 5 février 2012

2012-02-08T21:34:00Z

Post original: A week of symfony #266 (30 January -> 5 February 2012) )

Cette semaine une montagne de bugs ont été corrigés sur la branche "master" Symfony2 ainsi que de nombres améliorations et re-factorisaions concernant les composants "Formulaire" et "Validation". De plus, le dépôt officiel Symfony2 a atteins la limite symbolique des 1000 "forks".

Mailing liste de développement:

Développement Symfony2, l'essentiel:

Branche 2.0:

a1b6d4c: [DependencyInjection] added a failing testcase for escaped % in array parameters
048fc2f: [Form] fixed broken MoneyType test for JPY
8e13095, a7b48c0: [DependencyInjection] fixed the unescaping of parameters to handle arrays

Branche "Master":

a676598, 57cc531: [Form] added class LazyChoiceList
307f17d: [FrameworkBundle] code factorization in TraceableEventDispatcher
5aa5987: [Form] fixed form children are always validated in group Default
dbd3a1b: [Security] allowed unsetting parentAcl on MutableAclInterface
1678a3d: [Validator] fixed Validator::validateValue() propagates empty validation root instead of the provided value
1dd302c: [Validator] fixed ConstraintViolationList::__toString() to not include dots in the output if the root is empty
f904a9e: [Validator] fixed GraphWalker does not add constraint violation if error message is empty
a103c28: [Validator] the Collection constraint adds 'missing' and 'extra' errors to the individual fields now
de253dd: [Form] added read_only and disabled attributes
fe85bbd: [Validator] simplified ExecutionContext::addViolation() and added ExecutionContext::addViolationAt()
a30a679: [Validator] made ExecutionContext immutable and introduced new class GlobalExecutionContext
9153f0e: [Validator] deprecated ConstraintValidator methods setMessage(), getMessageTemplate() and getMessageParameters()
3c28ab7, [c373d5b|http://github.com/symfony/symfony/commit/c373d5b6568ac93ab1d7496d2254b1b6bd8e44d5): [Routing] no prefix is required to override imported RouteCollections
e9b4c58: [Console] enable process isolantion in shell
7cecb4e: [Form] added support for parent of FormBuilder
2e4ebe4: [Validator] renamed methods addViolationAtRelativePath() and getAbsolutePropertyPath() in ExecutionContext
7837f50: [Form] added FormUtil::singularify()
49d1464: [Form] implemented MergeCollectionListener which calls addXxx() and removeXxx() in your model if found
9b0245b: [Form] made prefix of adder and remover method configurable
9a4e22e: [Form] disallowed infinity in NumberToLocalizedStringTransformer
d208f4e: [Form] made it possible to use models with only either addXxx() or removeXxx()
b393774: [Form] used direct method access in MergeCollectionListener instead of Reflection to avoid problems when using class hierarchies
02f61ad: [Form] renamed choice and collection options 'adder_prefix' and 'remover_prefix' to 'add_method' and 'remove_method' and allowed to specify full method names
8dc40e4, 4847d3a: [FrameworkBundle] added config:dump-reference console command
58939f1, 9757958, 2f8ad93, fa32885: added configuration docs for TwigBundle (reverted)
bd461e2: [Form] forms now don't create empty objects anymore if they are completely empty and not required. The empty data for these forms is null
0753cee: [Form] fixed read_only attribute for expanded fields

Plugins symfony1 mis à jour:

apostrophe:

fixed bug that caused page forms not to work
refactored getEmbedCode() so it doesn't instantiate embed services twice and doesn't crash if the service URL is bogus and the width and height aren't known
don't cache non-200 OK responses, it leads to SEO problems
refactored nonrecursive version of aFiles::rmRf

apostropheBlog:

fix for XSS attack

Ils s'en ont parlé:

Don't miss the Confoo Conference 2012

2012-02-08T13:27:09Z

The Confoo Conference is the most exciting conference I've experienced so far. The venue is awesome and the quality of talks is excellent. This year, the best speakers in the world will join the conference and talk about trendy web technologies topics like PHP, HTML5, JavaScript, Ruby, Python, Java, Scala, NodeJS...

You should not miss it if you are near Montreal. The first two days of the event are dedicated to workshops on monday 27th and tuesday 28th of February. These workshops will cover interesting topics like PHP best practices, HTML 5 and accessibility, security and Symfony. SensioLabs will also be there to provide a Symfony2 advanced workshop. If you want to improve your skills with Symfony2, you will have the chance to be trained by an official SensioLabs trainer: me! The number of seats are limited and my training session is almost full. Don't wait a minute a book your training day at a special fare of $700.00 CAD (+ tax.).

Then, for the last three days, there are more than 160 conference sessions split in 10 tracks about PHP, security, testing, Ruby, Java, Python, HTML5, Scala, NodeJS, mobile and many more trendy topics. With such a wide choice, you will have the chance to discover and learn more about the best tools and techonologies from the best experts in world.

Below is a list of the announced top speakers:

Fabien Potencier (Symfony and Twig lead developer)
Derick Rethans (XDedug lead developer)
Ilia Alshanetsky (PHP core developer)
Andreï Ziemvski (PHP core developer)
Sebastian Bergman (PHPUnit lead developer)
Arne Blankerts (PHPDocx lead developer)
David Zuelke (Agavi framework lead developer)
Joshua Hull (Twitter)
Karl Dubost (Opera software)
...

If you want to know more about the schedule, just look at the Confoo Conference website: http://confoo.ca

Se publica Symfony 2.0.10

2012-02-06T13:25:42Z

El proyecto Symfony acaba de publicar la versión 2.0.10. La principales novedades respecto a la versión anterior son:

Twig se ha actualizado a la versión 1.6 (ver novedades). Esta actualización corrige un problema de Assetic en el entorno de producción.
Doctrine2 se ha actualizado a sus últimas versiones estables.
Se han corregido pequeños errores (ver changelog completo)

Para actualizar tus aplicaciones, modifica primero el valor de los archivos deps y deps.lock por los siguientes:

Y después ejecuta el siguiente comando para descargar los cambios:

$ php bin/vendors install

Por último, si al ejecutar después la aplicación se muestra algún error, vuelve a borrar la cache manualmente:

$ php app/console cache:clear

Fuente: Symfony 2.0.10 released

svn blame: who made the bug?

2012-02-05T16:48:00Z

In bigger projects it happens quite often that an unknown team member has made a modification that caused a lot of trouble. And no one wants to confess... It is quite uncomfortable to analyse distinct revisions and changes of a file to find who caused the problem, as it is time consuming. This is where svn blame is the perfect tool - you execute it upon a chosen target to display revision number, team member and content line by line. You can easily find who is the author of a bug and when he committed it. It's intereting, that despite being very useful, this tool is not very known.

blame me if you can find me quickly!

The usage is very simple:


tducin@workshop:/var/www/admin/config/doctrine$ svn blame schema.yml

and you have the entire file analysed:


   367     dennis connection: master
   362     tducin
   362     tducin options:
   362     tducin   charset: utf8
   362     tducin   collate: utf8_general_ci
   362     tducin
  3755     george Status:
  3755     george   comment: "Statusy"
   491     dennis   actAs:
  1980     dennis     SoftDelete: ~
  1793     harold     Timestampable: ~
  1793     harold     Signable: ~
   492     tducin   columns:
   492     tducin     name:
  3755     george       type: string(64)
   492     tducin       notnull: true
  2628     tducin       comment: "nazwa"
  3755     george     notify_mail:
  3755     george       type: boolean
  3755     george       notnull: true
  3755     george       default: false
  3755     george       comment: "klient ma być powiadamiany mailowo"
  1541     dennis     stock_mode:
  1541     dennis       type: enum
  1541     dennis       values: [ reserved, sent, cancelled ]
  1541     dennis       default: reserved
  2628     dennis       comment: "tryb magazynowy: reserved, sent, cancelled"
  3755     george     force_reminder:
   892     tducin       type: boolean
   878     tducin       notnull: true
  3755     george       comment: "Wymuszenie dodania wpisu w kalendarzu"
  3755     george     block_update:
  3755     george       type: boolean
  3755     george       notnull: true
  3755     george       comment: "Blokada zmiany statusu"
  4078     harold   indexes:
  4078     harold     softdelete_idx:
  4078     harold       fields: [ deleted_at ]

Une semaine symfonique #265 - du 23 au 29 janvier 2012

2012-01-31T13:12:00Z

Post original: A week of symfony #265 (23->29 January 2012)

Cette semaine les collecteurs time, logger et Doctrine ont été améliorés et refactorisés. Pendant ce temps, de nombreux bug ont été corrigés sur le composant Form, particulièrement concernant l'amélioration de l'interface ChoiceListInterface et de ses implémentations.

Mailing liste de développement:

Call for volunteers for Netbeans Sf2 plugin development

Développement Symfony2, l'essentiel:

Branche 2.0:

7f96c8a: [HttpKernel] prevent php script execution in cached ESI pages using HttpCache
c3f0ec7: [DoctrineBundle] made DoctrineBundle fowards compatible with Doctrine 2.2

Branche "Master":

3b260d2: refactored the collector to separate the loggers per connection
e37783f: [DoctrineBridge] refactored the query sanitization in the collector
2a998e0: [FrameworkBundle] handle disabled csrf protection in the PHP templating form helper
3a1699a: handle disabled csrf protection in the Twig FormExtension
87b16e7: [Form] greatly improved ChoiceListInterface and all of its implementations (EntityChoiceList was adapted, the methods getEntities(), getEntitiesByByKeys(), getIdentifier() and getIdentifierValues() were removed/made private. Instead of the first two you can use getChoices() and getChoicesByValues(), for the latter two no replacement exists. ArrayChoiceList was replaced by SimpleChoiceList. PaddedChoiceList, MonthChoiceList and TimezoneChoiceList were removed. Their functionality was merged into DateType, TimeType and TimezoneType)
e1fc5a5: [Form] restricted form names to specific characters to fix generation of HTML IDs and to avoid problems with property paths
f533ef0: [Form] added ChoiceView class for passing choice-related data to the view
43e0db5: [DomCrawler] add support for multivalued form fields
399af27: [Form] implemented checks to assert that values and indices generated in choice lists match their requirements
ed9c348: [Security] Authentication(Success|Failure)Handler can now return null
2dd4bf1, c3f637b: [Form] support for PATCH method in forms
d4300b9, b879397: [WebProfilerBundle] tweak the time view
a52c675: [WebProfilerBundle] improved the logger panel

Plugins symfony1 mis à jour:

dcReloadedFormExtra:

added a uniquenes checker widget that checks the uniqueness of a value using an Ajax callback

sfSyncContent:

created default parameters for sync content to be frontend dev FROM prod@production

apostrophe:

added an app.yml option to return email links in a different format that allows apostrophe.unobfuscateEmailInline to be called outside of the a_js spool
all unlink() and rmdir() calls in the product now invoke aFiles::unlink() and aFiles::rmdir(), providing a capability to override these methods
the aFiles class has been refactored into a BaseaFiles? class and an empty aFiles subclass, allowing convenient overrides
a_button helper now accepts a single array of options as an alternative to the full list of parameters
slideshows are allowed to have the crossfade transition now even if they have no height specified
fixed event bug in menutoggle script and added jQuery 1.7 to the plugin
annotation of multiple media items works again

apostropheBlog:

added a 'first' class to the first pager in the blog index

Ils s'en ont parlé:

symfony range filter

2012-01-29T15:06:00Z

In symfony/doctrine, only the Timestampable behavior provides ranged filters (a combination of from and to values that are queried just like MySQL BETWEEN statement). But how about ranged values for other data types?

I thought it'd be both cool and very useful, so I set off to search the web, but found no solution. Hence, I've made one myself. We will create three new classes and modify two more files to make it work in the basic version.

new widget/validator classes

The first class to be added is the form widget, lib/widget/sfWidgetFormInputRange.class.php:

class sfWidgetFormInputRange extends sfWidgetForm
{
  protected function configure($options = array(), $attributes = array())
{
$this->addRequiredOption('from_value');
$this->addRequiredOption('to_value');
Â 
$this->addOption('template', 'from %from_value% to %to_value%');
}
Â 
/**
   * Renders the widget.
   *
   * @param  string $name        The element name
   * @param  string $value       The value displayed in this widget
   * @param  array  $attributes  An array of HTML attributes to be merged with the default HTML attributes
   * @param  array  $errors      An array of errors for the field
   *
   * @return string An HTML tag string
   *
   * @see sfWidgetForm
   */
public function render($name, $value = null, $attributes = array(), $errors = array())
{
$value = array_merge(array('from' => '', 'to' => ''), is_array($value) ? $value : array());
Â 
return strtr($this->translate($this->getOption('template')), array(
'%from_value%' => $this->getOption('from_value')->render($name.'[from]', $value['from']),
'%to_value%'   => $this->getOption('to_value')->render($name.'[to]', $value['to']),
));
}
Â 
/**
   * Gets the stylesheet paths associated with the widget.
   *
   * @return array An array of stylesheet paths
   */
public function getStylesheets()
{
return array_unique(array_merge(
$this->getOption('from_value')->getStylesheets(),
$this->getOption('to_value')->getStylesheets()));
}
Â 
/**
   * Gets the JavaScript paths associated with the widget.
   *
   * @return array An array of JavaScript paths
   */
public function getJavaScripts()
{
return array_unique(array_merge(
$this->getOption('from_value')->getJavaScripts(),
$this->getOption('to_value')->getJavaScripts()));
}
}

The second one is the form filter widget, lib/widget/sfWidgetFormFilterInputRange.class.php:

Truncated by the Symfony feed aggregator, read more.

Load fixtures with Symfony2

2012-01-28T13:06:00Z

Hi Symfonians !

I am actually spending a lot of time on testing Symfony2. When building an application, one of the first thing you will have to do is to insert initial datas, also called fixtures, so you can use and test your application. There is a documentation on the Symfony website about this subject, it uses the DoctrineFixturesBundle.

It works very well, but I wanted to use YAML files "a la symfony1". So I ended up with this simple solution:

The base Loader class:

First, I create a base Loader class that others entities loaders will extend:

The getModelFixtures() function will load the YAML file corresponding to the current entity, the getModelFile() function will have to be implemented by sub-loaders. The class implements the ContainerAwareInterface so we can access the DIC in the loaders.

The Category loader:

The YAML file:

Both jobs and categories YAML files are almost equal to the Jobeet1 tutorial ones.

The loader class:

The getModelFixtures() function retrieves the fixtures for the Category entity and then you just have to iterate over the array. At each iteration we add a reference to the entity so it can be used in other loaders. (as a foreign key)

The Job loader:

The YAML file:

The loader class:

Same here, but: for each iteration we retrieve the proper category reference we already built in the Category loader (line 30). In Jobeet1 there was a loop directly in the YAML file in order to add lot of job rows, now we can do this loop in our loader: duplicateLastJob(). There is also a special case where we force a value for the expiresAt date field that would be overridden by the Job object life-cycle callbacks otherwise.

You can find the code on github.

See you ! COil

PS: This tutorial was tested with Symfony Standard Edition 2.0.9

Other posts about Symfony2 fixtures:

Load fixtures with Symfony2 and YAML files

2012-01-28T13:06:00Z

The base Loader class:

First, I create a base Loader class that others entities loaders will extend:

The Category loader:

The YAML file:

Both jobs and categories YAML files are almost equal to the Jobeet1 tutorial ones.

The loader class:

The Job loader:

The YAML file:

The loader class:

Same here, but:

For each iteration we retrieve the proper category reference we already built in the Category loader (line 30).
In Jobeet1 there was a loop directly in the YAML file in order to add lot of job rows, now we can do this loop in our loader: duplicateLastJob().
There is also a special case where we force a value for the expiresAt date field that would be overridden by the Job object life-cycle callbacks otherwise.

I think this a good approach as you have the ease of writing YAML without loosing the possibility to handle complex or edge cases with PHP. You can find the code on github.

See you ! COil

PS: This tutorial was tested with Symfony Standard Edition 2.0.9.
PS2: If you have a blog post about fixtures, let me know so I can add it below.

Other posts about fixtures:

sqlite w środowisku developerskim w symfony i symfony2

2012-01-26T18:59:23Z

Sqlite nie koniecznie jest dobrą bazą produkcyjną dla tworzonych aplikacji internetowych. Jednak podczas ich tworzenia powinna nadać się idealnie. Tym bardziej, jeśli nie chcemy naszej maszyny developerskiej obarczać dodatkowymi procesami, czy też pilnować włączania/wyłączania serwerów bazy danych, sqlite nada się idealnie.