What is Symfony?
Get started
Documentation
Community
Services
News

Latest News

New in Symfony 2.3: Small things matter

by Fabien Potencier – May 17, 2013

What happened last week in Symfony?

This week, Symfony 2.3.0 released its second and last beta version. Among other features, this version supports the interactive management of the parameters.yml file and some nice improvements for the Console component. In addition, the Symfony 2.1.10 maintainance version and the Twig 1.13.0 version were released.

Upcoming Events

The Symfony Community organizes events all over the world on a regular basis. Here are the next ones.

United States, Portland — SymfonyLive Portland 2013

from May 20, 2013 to May 24, 2013

Netherlands, Utrecht — Symfony Meetup - Netherlands/Utrecht

on May 22, 2013, from 19:00 to 22:00

France, Montpellier — eZ UnConference #2

from May 27, 2013 to May 29, 2013

Germany, München — Symfony User Group München

on June 05, 2013, from 18:30 to 22:30
About

Blog

FireSymfony: Installing and Configuring the Plugin
by Alvaro Videla – September 09, 2009 – 8 comments

In the previous post we went through the features provided by FireSymfony. In this post we are going to see how to install the Firefox Add On and the symfony plugin.

Plugin Installation

To install the symfony plugin go to your project root folder and type in the command line:

> php symfony plugin:install firesymfonyPlugin

If you're used to install plugins using svn externals, you can obtain the plugin code from here

Then edit your factories.yml file and enable FireSymfony under the all label like this:

all:
  logger:
     class: sfAggregateLogger
     param:
       level: debug
       loggers:
         sf_web_debug:
           class: sfWebDebugLogger
           param:
             level: debug
             condition:       %SF_WEB_DEBUG%
             xdebug_logging:  true
             web_debug_class: fsWebDebugForSf12
         sf_file_debug:
           class: sfFileLogger
           param:
             level: debug
             file: %SF_LOG_DIR%/%SF_APP%_%SF_ENVIRONMENT%.log

If you prefer you can configure FireSymfony for a specific environment.

The important line there is the web_debug_class configuration.

The on your databases.yml file and for the environment which needs debugging (usually will be dev) be sure that you setup the database class name as this:

classname: DebugPDO

In this way FireSymfony will be able to collect the query logs.

Add On Installation:

Open Firefox and go to the Tools menu and click on Add-ons
Select the Get Add-ons tab
Enter FireSymfony in the search box and press enter
Select and Install the add-on
Restart Firefox

If you like to install the add on manually you can download it from here

If you point Firefox to myproject/fronted_dev.php it should show symfony debug information inside Firebug in the symfony tab. If you see the data there it means you succeed in the installation.

Support:

If you had problems installing FireSymfony you can ask for help in the mailing list

For reporting bugs please go to the Google Code project page if the issue hasn't been reported yet, please file it there.

You can find all those links together at the extension website which we plan to improve soon.

Thanks for reading so far and I hope to read your comments and suggestions here or at the FireSymfony mailing list.

Add a Comment

Connect to post a comment

Comments

#1 jeremy said on the 2009/09/09 at 15:58

DebugPDO looks like it is for Propel only. Is there an equivalent file for Doctrine?
#2 Massimiliano Arione said on the 2009/09/09 at 17:56

You're missing one step: after installing the plugin, you should enable it in config/ProjectConfiguration.class.php, unless you use blacklist options for plugins (that's not recommended)
#3 J_Wesker said on the 2009/09/09 at 17:56

Ok! It's pretty cool but doesn't work when being redirected :/ the question is now how to uninstall it? I've tried to do php symfony plugin:uninstall firesymfonyPlugin but it just says it is not installed but the files are still there :S
#4 alvaro said on the 2009/09/09 at 18:00

@jeremy Please ask at the symfony users mailing list about Doctrine, I don't have experience with it

@Massimiliano thanks for the tip

@J_Wesker I will take a look into that issue
#5 ornicar said on the 2009/09/09 at 18:30

Little typo in factories sample:

web_debug_class: fsWebDebugForSf12
#6 A. Botero said on the 2009/09/10 at 15:37

@jeremy DebugPDO works with Propel and Doctrine
#7 jayson said on the 2009/09/11 at 05:46

@jeremy, there is no need to set DebugPDO for doctrine, the log will be enabled just like symfony logging, by set sf_debug & sf_logging_enabled to true.
#8 netouent said on the 2009/09/14 at 11:45

Realy interesting, work perfectly with ff 3.5.3

But database query logger may be improved to replace :p1, :p2, ... with their value to be realy useful