Cyrille Giquello

Cette page est en lecture seule. Vous pouvez afficher le texte source, mais ne pourrez pas le modifier. Contactez votre administrateur si vous pensez qu'il s'agit d'une erreur.
====== Symfony ======

[[https://symfony.com/]] [[wpfr>Symfony]]

! NEW ! [[/informatique/php/Symfony3]]

! NEW ! [[/informatique/php/Symfony2]]

{{:informatique:php:symfony_logo.gif?160|Symfony logo}}

  * [[http://pixeljets.com/blog/drupal-7-vs-symfony-2-overview-after-1-year-symfony-development|Drupal 7 vs Symfony 2: overview after 1 year of Symfony development]]

[[:informatique:php:Symfony:Etude perso|Etude perso]]

[[/informatique/php/Symfony/Gestion de la langue de l'utilisateur]]

===== Documentation =====

**Accès rapide:**
  * [[http://www.symfony-project.org/reference/1_4/en/16-Tasks|Symfony Reference Book v1.4]]
    * [[http://www.symfony-project.org/reference/1_4/en/16-Tasks|Tasks]] (chap 16)
  * [[http://www.doctrine-project.org/projects/orm/1.2/docs/en|Doctrine ORM v1.2]]
    * [[http://www.doctrine-project.org/projects/orm/1.2/docs/manual/en|Manual - Table of Contents]]

Les livres Sensio Labs (buy or read online for free)
  * [[http://books.sensiolabs.com/book/filter|Tous les livres]] en anglais.
  * [[http://www.symfony-project.org/more-with-symfony/1_4/fr/|Plus loin avec Symfony 1.3 & 1.4]] en français.

**symfony-project.org**\\
  * Le site du projet Symfony: http://www.symfony-project.org
  * code snippets published by others: http://snippets.symfony-project.org
  * Forum: http://forum.symfony-project.org/index.php/i/
  * user mailing-list: http://groups.google.com/group/symfony-users
  * Wiki: http://trac.symfony-project.org/wiki
  * List of plugins: http://www.symfony-project.org/plugins/
  * Developers mailing-list: http://groups.google.com/group/symfony-devs/topics

**Symfonians**\\
Ce site propose de mettre en relation des développeurs, des entreprises, des projets et des offres d'emploi en relation avec le framework Symfony. Et notamment une [[http://symfonians.net/applications|liste d'applications]].\\
http://fr.symfonians.net/

**feeds.feedburner.com**
  * Offical blog feed: http://feeds.feedburner.com/symfony/blog
  * Symfony planet feed: http://feeds.feedburner.com/symfony/planet

**Symfony IRC**\\
irc://irc.freenode.net/symfony

**Blog des développeurs**
  * http://mirmodynamics.com ([[http://mirmodynamics.com/tag/symfony|tag Symfony]])

**Developpez.com**
  * [[http://php.developpez.com/cours/?page=frameworks#symfony|Cours et tutos]]
  * [[http://www.developpez.net/forums/f663/php/bibliotheques-frameworks/symfony/|Forum Symfony]]
  * [[http://c-maneu.developpez.com/tutorial/web/php/symfony/intro/|Commencer à développer avec le framework symfony]] le 02/08/2007 par Christopher MANEU

[[http://webmozarts.com/2009/06/30/easy-unit-testing/|Easy Unit Testing]] with Lime, the Test tool inside Symfony.

[[/informatique/php/comparaison_zend_framework_symfony|Comparaison Zend_Framework et Symfony]]

[[http://www.clever-age.com/veille/blog/industrialisation-de-projets-multi-sites.html|industrialisation de projets multi-sites]]

The **sandbox** is a pre-packaged symfony project. It is made for people who want to play with the framework. 

[[http://snippets.prendreuncafe.com/snippets/tagged/symfony/order_by/date|Snippets tagged "symfony"]] sur prendreuncafe.com.

===== Plugins =====

  * List of plugins: http://www.symfony-project.org/plugins/

Quelques plugins qui ont attirés mon attention :

==== Security ====

[[http://www.symfony-project.org/plugins/sfDoctrineGuardPlugin|sfDoctrineGuardPlugin]] is a symfony plugin that provides authentication and authorization features above the standard security feature of symfony.\\
It gives you the model (user, group and permission objects) and the modules (backend and frontend) to secure your symfony application in a minute in a configurable plugin.

[[http://www.symfony-project.org/plugins/sfDoctrineUserPlugin|sfDoctrineUserPlugin]] provides a starting point for anyone needing a quick full user in any application. It creates a user which has a sfGuardUser. This user then has the following properties: sfGuardUser (Multiple Groups, Multiple permissions, username, password), sfUserUser ( Multiple Email Addresses, Multiple Addresses, Multiple Phone Numbers...)

==== Forms & Widgets ====

[[http://www.symfony-project.org/plugins/sfExtraWidgetsPlugin|sfExtraWidgetsPlugin]], is a complement of the symfony widgets. All widgets use the prototype javascript framework.

[[http://www.symfony-project.org/plugins/sfWidgetFormInputSWFUploadPlugin|SWFUpload]] is a small JavaScript/Flash library to get the best of both worlds. It features the great upload capabilities of Flash and the accessibility and ease of HTML/CSS.

[[http://www.symfony-project.org/plugins/sfViewableFormPlugin|sfViewableFormPlugin]] Enhance you forms with forms.yml.

==== Routing & Co. ====

[[http://www.symfony-project.org/plugins/sfDomainRoutePlugin|sfDomainRoutePlugin]]: Pass and retrieve parameters in the subdomain, Limit routes to certain domains or subdomains, Generate urls across subdomains.

[[http://www.symfony-project.org/plugins/sfOfflineFilterPlugin|sfOfflineFilterPlugin]] Ce plugin, vous permet de mettre hors ligne votre site, tout en continuant à le visiter si vous êtes connecté.

[[http://www.symfony-project.org/plugins/sfSimplePagePlugin|sfSimplePagePlugin]] allows you to manage like static pages with symfony. These page is rendered by symfony, so you can use view system of partial, component, helper...

==== Performance ====

[[http://www.symfony-project.org/plugins/sfCombinePlugin|sfCombinePlugin]] combines multiple JavaScript and CSS files into one JavaScript and one CSS file at runtime, in order to minimize the number of HTTP requests required to render a given page.

[[http://www.symfony-project.org/plugins/sfSuperCachePlugin|sfSuperCachePlugin]] writes your page cache somewhere under your root directory to allow your web server to serve them as fast as possible.

==== Dev tools ====

[[http://www.symfony-project.org/plugins/sfTaskExtraPlugin|sfTaskExtraPlugin]] Adds tasks to your symfony command line to help streamline your workflow.

[[http://www.symfony-project.org/plugins/sfPhpunitPlugin|sfPhpunitPlugin]] creates stub classes for PHPUnit of classes in lib/model. 

[[http://www.symfony-project.org/plugins/sfBugsPlugin|sfBugsPlugin]] allows you to easily send bugs from the Web Debug Toolbar for modules and actions. It's useful for testers to mark bugs for specific sections.

[[http://www.symfony-project.org/plugins/sfDoctrineGraphvizPlugin|sfDoctrineGraphvizPlugin]] Adds a doctrine task that output database MCD and MLD schema using graphviz.

[[http://www.symfony-project.org/plugins/sfApplicationMapPlugin|sfApplicationMapPlugin]] provides tasks to generate application-module-action structure images for your entire project using Graphviz. Useful at the designing stage of projects. Very useful to create brief overlook of a project.

[[http://www.symfony-project.org/plugins/mgI18nPlugin|mgI18nPlugin]] add a new transtalation panel into the debug web panel. The translation panel displays all source messages used in the current page, and a form to edit the target messages.

==== Autres ====

[[#ckwebserviceplugin|ckWebWervicePlugin]]: Server SOAP pour Symfony.

[[http://www.symfony-project.org/plugins/apostrophePlugin|apostrophePlugin]]: [[http://www.apostrophenow.com/|Apostrophe]] is a content management system. Apostrophe is open source, and built upon the great work of other open source projects. That's why our apostrophePlugin is a plugin for the Symfony web application framework.

The philosophy of Apostrophe is that editing should be done "in context" as much as possible, keeping confusing modal interfaces to a minimum and always emphasizing good design principles and an intuitive user experience. When we are forced to choose between ease of use and a rarely used feature, we choose ease of use, or make it possible to discover that feature when you truly need it.

[[http://www.sympalphp.org|Sympal]] is an extension for Symfony that is specifically designed for building content based websites/applications.

[[http://www.symfony-project.org/plugins/i18nTranslatePlugin|i18nTranslatePlugin]] The i18nTranslatePlugin attempts to translate your words and sentences using Google Language Api.

[[http://www.symfony-project.org/plugins/sfEleAdminEmailPlugin|sfEleAdminEmailPlugin]] The sfEleAdminEmailPlugin is a symfony plugin that provides a simple tool for email template administration and also an extension for SwiftMailer message class that allow the sending of formated templates.

[[http://www.symfony-project.org/plugins/sfWorkerPlugin|sfWorkerPlugin]] manage workers from symfony requests. Here workers means external process which may be longer than a single http request. Like you spawn a process external to symfony which will goes on running after the http request which created it.

[[http://www.symfony-project.org/plugins/sfEzcWorkflowPlugin|sfEzcWorkflowPlugin]] is a symfony plugin which allows you to create workflow-driven applications on symfony projects. Workflow definition and execution are handled by ezcWorkflow, therefore you need to install ezComponents first. This plugin provides an interface for admin workflows and executions (create, instantiate, resume and cancel an ezcWorkflow). Also, an input node which links the workflow execution with symfony actions is provided.


===== Divers =====

[[http://www.glagla.org/weblog/2009/09/08/faire-des-liens-entre-applications-dans-un-projet-symfony-revue-des-trois-methodes-proposees/|Faire des liens entre applications dans un projet symfony, revue des trois méthodes proposées]]

==== Flash ====

AMF Server with [[http://www.symfony-project.org/plugins/sfAmfPlugin|sfAmfPlugin]]. Plugin to handle AMF requests from Flex frontends. The plugin is currently based on the SabreAMF library. It makes the development and integration of Services easy.



==== About Timestamp ====

In the method Doctrine_Template_Listener_Timestampable::getTimestamp() there is:
  * type "date" = date($options['format'], time())
  * type "timestamp" = the same as type "date"
  * else = time() (an Unix timestamp) 
Why it isn't like :
  * type "date" = date($options['format'], time())
  * type "timestamp" = time() (an Unix timestamp)
Ma question sur le forum: [[http://forum.symfony-project.org/index.php/t/28456/|A "philosophic" question about timestamp in class Doctrine_Template_Listener_Timestampable]]

==== Suggable behavior ====

> **Q:** Quand l'option canUpdate de Sluggable est à FALSE, je peux le mettre à jour sans générer d'erreur ... Ce n'est pas normal ?! (la question sur [[http://groups.google.com/group/symfony-users/browse_thread/thread/58a3df8ade84d6af|symfony-users]])
>> **R:** C'est normal, l'option "canUpdate" concerne la mise à jour ou non du "slug" quand l'un des "fields" est modifié. Cette option n'empêche en rien la modification manuelle (via un Form).

Si l'on souhaite modifier le Form d'Admin généré :
<code php>
class MyModelForm extends BaseMyModelForm
{
 public function configure()
 {
  // remove it
  //unset( $this->widgetSchema['slug'] );
  // or make it readonly
  $this->widgetSchema['slug']->setAttribute('readonly', true);
 }
}
</code>

==== Timestampable behavior and generated admin form ====

Depuis la version 1.4, lorsque l'on génère les interfaces d'administration (symfony doctrine:generate-admin) pour un modèle avec le behavior Timestampable (actAs: Timestampable: ~), les champs "created_at" et "updated_at" sont générés dans le Form, ce qui est bien embêtant...

Du coup pour les supprimés, il faut modifier la définition du formulaire dans la classe qui étend le formulaire de base pour le modèle.

La classe "MaClasse" à modifier se trouve dans
  lib/form/doctrine/maClasseForm.Class.php
supprimer les validators et les widgets:
<code php>public function configure()
{
  //Following code will remove Required validators from these fields.
  unset($this->validatorSchema['created_at']);
  unset($this->validatorSchema['updated_at']);

  //following code will remove fields from form
  unset($this->widgetSchema['created_at']);
  unset($this->widgetSchema['updated_at']);
}</code>

====Action's properties declaration====

If a property is created in an action, all things work:
<code php>
  public function executeIndex(sfWebRequest $request)
  {
    $this->jobeet_jobs = Doctrine::getTable('JobeetJob')->createQuery('a')->execute();
  }
</code>
But if I add a property's declaration, it does not work any more :
<code php>
class jobActions extends sfActions
{
  public $jobeet_jobs = null;
	
  public function executeIndex(sfWebRequest $request)
  {
    $this->jobeet_jobs = Doctrine::getTable('JobeetJob')->createQuery('a')->execute();
  }
</code>
An execption is throwed :
  Notice: Undefined variable: jobeet_jobs in D:\dev.www\Symfony\Jobeet\apps\frontend\modules\job\templates\indexSuccess.php

What's the reason of that ???

**Answer:**
>> http://forum.symfony-project.org/index.php?t=rview&goto=100435#msg_100435
>> This is deliberate.
>> Declared action attributes are regarded as private to the template i.e. they're expected to be used just for the action itself.
>> If they are undeclared, they are made available to the template by symfony.

==== Surcharge des plugins ====

Les plugins symfony ont la particularité de pouvoir être surchargés dans chaque application avec une granularité relativement fine. Par exemple, il est facile de ne surcharger qu’une action, qu’un template ou qu’un partiel.

Pour permettre la surcharge la plus souple possible, ce découpage des classes doit être généralisé au sein des plugins (actions, components, model, utilitaires,... ). Il s’agit de la méthode utilisée pour les plugins publics développés pour symfony, et du code généré par Propel ou Doctrine. Pour simplifier la création de modules dans les plugins suivant cette convention, on peut gagner du temps en utilisant **le plugin [[http://www.symfony-project.org/plugins/sfTaskExtraPlugin|sfTaskExtraPlugin]] et la tâche generate:plugin-module**, qui pré-générera les classes d’actions.

Lire la suite: [[http://www.clever-age.com/veille/blog/industrialisation-de-projets-multi-sites.html|industrialisation de projets multi-sites/Capitalisation du code]]

==== Log and Logging ====

How to write to log:
<code php>
 // in an action
 $this->logMessage($message, $level);
 // in a template
 <?php use_helper('Debug') ?>
 <?php echo log_message($message, $level) ?>
 // anywhere in your application
 sfContext::getInstance()->getLogger()->info($message);
 sfContext::getInstance()->getLogger()->err($message);
</code>

**__To Check__**: if you turn off the logging and change the logging level to 'err', then getInstance()->getLogger()->debug() will fail with an error.

==== Form and Widget ====

[[http://www.journaweb.info/2009/11/uploader-proprement-des-images-avec-symfony/|Uploader proprement des images avec Symfony]]

=== order fields in form ===

<code php>
 // sfWidgetFormSchema::setPositions(array $positions)
 // ATTENTION: Positions array must include all fields
 $this->getWidgetSchema()->setPositions( array('name','email') );

 // sfWidgetFormSchema::moveField($field, $action, $pivot = null)
 $this->getWidgetSchema()->moveField('name', sfWidgetFormSchema::FIRST );
 $this->getWidgetSchema()->moveField('email', sfWidgetFormSchema::AFTER, 'name' );
</code>

=== Custom Widget ===

[[http://nibsirahsieu.wordpress.com/2009/12/09/combining-input-and-choice-widget-in-symfony/|Combining input and choice widget]] (class myWidgetFormInputTextAndChoice extends sfWidgetForm)

=== Dynamically add fields ===

Got it!
  * [[/informatique/php/symfony/Dynamically add fields|My work]]
  * Dynamic input using javascript and symfony embedded forms http://nibsirahsieu.wordpress.com/2009/11/07/dynamic-input-using-javascript-and-symfony-embedded-forms/
  * Using embedFormForEach in Symfony http://blog.barros.ws/2008/12/01/using-embedformforeach-in-symfon/

Poor:
  * http://groups.google.com/group/symfony-users/browse_thread/thread/572fc3b97316cae6/576f21715c35b73c?lnk=gst&q=Validating+Forms+with+Dynamic+Fields#576f21715c35b73c
  * http://groups.google.com/group/symfony-users/browse_thread/thread/4c4641688ba1ea45/8ae79d44cce598fb?show_docid=8ae79d44cce598fb

===== SOAP =====

==== Symfony en serveur SOAP ====

**[[http://www.symfony-project.org/plugins/ckWebServicePlugin|ckWebServicePlugin]]**\\
The ckWebServicePlugin allows you to build a webservice api for your symfony applications. It comes with a powerful and easy to use wsdl generator, which creates WS-I compliant wsdl files for a maximum of interopability with PHP, .NET and Java clients. \\
Articles:
  * [[http://forum.symfony-project.org/index.php/t/13414/|ckWebServicePlugin - Setup]] in a forum's thread.
  * [[http://blog.barros.ws/2008/11/16/soap-webservice-in-symfony/|With the ckWebService plugin]] November 16th, 2008 by Carlos Barros.

Plus vieux :
[[http://snippets.symfony-project.org/snippet/135|Soap server]] by Fuad Arafa on 2007-01-18

==== ckWebServicePlugin ====

Talking about the plugin on the [[http://forum.symfony-project.org/index.php/f/12/|Symfony forum]]

J'ai essayé ce plugin en l'installant sur une sandbox_1.2 et il y a quelques précisions à apporter au README :

Mettre en commentaire le web_debug dans filters.yml. C'est un problème cette modif de config est pour toute l'application au lieu d'être propre à l'environnement.

Il faut mettre le block "soap_parameter" entre "security" et "cache", si on le met à la fin du fichier ça ne fonctionne pas : le filtre ckSoapParameterFilter n'est pas inscrit dans la chaîne.

    soap_options:
      encoding: utf-8
      soap_version: <?php echoln(SOAP_1_2); ?>

in app/config/php/yml :
  set:
    soap.wsdl_cache_enabled: 0

Problème de sérialisation des objets Propel. \\
Le Problème et la solution : http://forum.symfony-project.org/index.php/m/81012/#msg_81012

===== Data Access =====

Symfony est livrée avec les ORMs Propel et Doctrine. La v1.2 semble préconiser Doctrine.

[[http://redotheweb.com/2008/07/08/comparing-propel-doctrine-and-sfpropelfinder/|Des exemples de requêtes en Propel et Doctrine]]

==== Multi databases ====

[[http://groups.google.com/group/symfony-users/browse_thread/thread/57a32bad21f4075d/baec21d4957b1fa9?lnk=gst&q=multiple+dsn#baec21d4957b1fa9|Multiple Databases doctrine on sf1.2]]

[[http://groups.google.com/group/symfony-users/browse_thread/thread/8e52fb5f7f7ab471/2dfee5fc77622529?lnk=gst&q=multiple+database#2dfee5fc77622529|Symfony + Propel + Multiple Schemas]]

==== Arbre de données ====
Ou gestion de catégories ;-)

Doctrine NestedSet
  * [[http://docs.doctrine-project.org/projects/doctrine-orm/en/2.0.x/reference/limitations-and-known-issues.html#nested-set|Limitations and Known Issues - NestedSet]] \\ NestedSet was offered as a behavior in **Doctrine 1** and will not be included in the core of **Doctrine 2**. However there are already two extensions out there that offer support for Nested Set with Doctrine 2
  * Doctrine 1 NestedSet behavior \\ [[https://zhaoscode.wordpress.com/2011/09/26/doctrine-nested-categories/]] \\ [[http://www.developpez.net/forums/d966051/php/bibliotheques-frameworks/symfony/orm/doctrine-nested-set-recuperer-items-toute-sous-arborescence/]]

Un peu vieux:
  * [[http://www.amicalement-web.net/symfony-gestion-d-un-arbre-en-propel-via-les-nestedset-part-1/2009/05/12/|How-to Symfony: Gestion d’un arbre en Propel via les NestedSet – Part 1]]
  * [[http://www.lexik.fr/sfblog/symfony/nested-set-doctrine-135|Gestion de la paternité]]
  * [[http://www.doctrine-project.org/documentation/manual/1_2/en/data-fixtures#fixtures-for-nested-sets|Fixtures For Nested Sets]] for Doctrine 1.2

==== Many-to-many relationships ====

Doctrine - Join Table Associations
  * [[http://www.doctrine-project.org/projects/orm/1.2/docs/manual/defining-models/en#relationships]]
  * [[http://www.doctrine-project.org/projects/orm/1.2/docs/manual/defining-models/en#relationships:join-table-associations]]
  * [[http://www.doctrine-project.org/projects/orm/1.2/docs/manual/yaml-schema-files/en#relationships:many-to-many]]

Symfony 1.4 Doctrine - Admin Generator - M:M - Many to many relationships \\
[[http://www.endertech.com/blog_list/symfony-1-4-doctrine-admin-generator-m-m-many-to-many-relationships]]

Schema-Files - Relationships - Many to Many \\
[[http://www.symfony-project.org/doctrine/1_2/en/04-Schema-Files]]


===== Template engine =====

Les templates de Symfony sont en php. Est-ce intéressant d'utiliser un moteur de template (Smarty, PhpTal, ...) ?
 
  * Avantages
    * Exécution plus rapide: pas de sur-couche d'interprétation, moins de transformation.
  * Inconvénients
    * Risque de déport de logique métier dans les templates.
  * Divers
    * Les Helpers génèrent du Html, l'édition des pages en wysiwyg s'en trouve limitée.

Du coup l'usage d'un moteur de template n'est pas très pertinent. Autant conserver les originaux html dans un coin, et les découper à l'intégration dans Symfony.

===== Dev tools =====

[[http://jlcoady.net/symfony/basic-continuous-integration-server-with-symfony-and-hudson|Basic Continuous Integration Server with Symfony and Hudson]]