Nice,

Now I had 1.0.5 working  very well.

thx for your effort

2008/10/3 alvaro <[EMAIL PROTECTED]>:
>
> Lucas,
>
> I did the following with no problems:
>
> 1- I removed the plugin.
> 2- I installed the version 1.0.4 with this command:
>
> php symfony plugin:install firesymfonyPlugin --release=1.0.4
>
> 3 - I tested the project, and I had the error that you reported.
>
> 4 - I upgraded with the following command:
>
> php symfony plugin:upgrade firesymfonyPlugin
>
> cheers,
>
> Alvaro
>
>
> On Oct 4, 2008, at 1:05 AM, Lucas Stephanou wrote:
>
>>
>> alvaro,
>>
>> via plugin-upgrade doesn't update the plugin, seems that the version
>> is the same, 1.0.4
>>
>> cheers
>> Lucas
>>
>> 2008/10/3 alvaro <[EMAIL PROTECTED]>:
>>>
>>> Hi,
>>>
>>> The bug should be fixed now, please update the plugin.
>>>
>>> I also added a wiki entry with detailed instructions here:
>>>
>>> http://code.google.com/p/firesymfony/wiki/firesymfonyPluginSetupInstructions
>>>
>>> And a ticket here:
>>>
>>> http://code.google.com/p/firesymfony/issues/detail?id=3
>>>
>>> Regards,
>>>
>>> Alvaro
>>>
>>> On Oct 3, 2008, at 10:08 PM, Lucas Stephanou wrote:
>>>
>>>> Working with symfony 1.1 if content type is text/html
>>>>
>>>> But if I send my pages as application/xhtml+xml breaks the page and
>>>> firesymfony, 'cause the data from firesymfony plugin turns my xml
>>>> to a
>>>> bad-formatted one.
>>>>
>>>> if I change the content-type directive in view.yml to text/html,
>>>> everything works fine
>>>>
>>>> the problem is 'Logs & Messages' string, more precisely in "&", just
>>>> change to 'Logs and Messages' the error doesn't  appear, but raise
>>>> another js error."illegal character"
>>>> and I stop here :-)
>>>>
>>>>
>>>> 2008/10/2 alvaro <[EMAIL PROTECTED]>:
>>>>>
>>>>> Hi,
>>>>>
>>>>> What I did to get it working is the following:
>>>>>
>>>>> 1 - There is a new version of the plugin that should support all
>>>>> the
>>>>> symfony versions now. So first update the plugin.
>>>>>
>>>>> 2 - For symfony 1.0 do the following:
>>>>>
>>>>> Change ONLY the loggers.yml file like this:
>>>>>
>>>>> all:
>>>>> enabled: on
>>>>> level:   debug
>>>>> rotate:  off
>>>>> period:  7
>>>>> history: 10
>>>>> purge:   on
>>>>> loggers:
>>>>>   sf_web_debug:
>>>>>     class: fsWebDebugLogger
>>>>>     param:
>>>>>       condition: %SF_WEB_DEBUG%
>>>>>   sf_file_debug:
>>>>>     class: sfFileLogger
>>>>>     param:
>>>>>       file: %SF_LOG_DIR%/%SF_APP%_%SF_ENVIRONMENT%.log
>>>>>
>>>>> The only difference here with the default symfony 1.0 loggers.yml
>>>>> is
>>>>> the entry: class: fsWebDebugLogger
>>>>>
>>>>> If you clear the cache and reload your site you should see the
>>>>> debug
>>>>> data on the FireSymfony extension.
>>>>>
>>>>> ------
>>>>>
>>>>> For symfony 1.1:
>>>>>
>>>>> Change ONLY the factories.yml file like this:
>>>>>
>>>>> all:
>>>>>   logger:
>>>>>   class: sfAggregateLogger
>>>>>   param:
>>>>>     level: debug
>>>>>     loggers:
>>>>>       sf_web_debug:
>>>>>         class: sfWebDebugLogger
>>>>>         param:
>>>>>           level: debug
>>>>>           condition:      %SF_WEB_DEBUG%
>>>>>           xdebug_logging: false
>>>>>           web_debug_class: fsWebDebugForSf11
>>>>>
>>>>> The only difference here with the default symfony 1.1 factories.yml
>>>>> is
>>>>> the entry: web_debug_class: fsWebDebugForSf11   (I turned off
>>>>> xdebug_logging, but that shouldn't affect the plugin)
>>>>>
>>>>> If you clear the cache and reload your site you should see the
>>>>> debug
>>>>> data on the FireSymfony extension.
>>>>>
>>>>> ------
>>>>>
>>>>> For symfony 1.2:
>>>>>
>>>>> Change ONLY the factories.yml file like this:
>>>>>
>>>>> all:
>>>>> logger:
>>>>>   class: sfAggregateLogger
>>>>>   param:
>>>>>     level: debug
>>>>>     loggers:
>>>>>       sf_web_debug:
>>>>>         class: sfWebDebugLogger
>>>>>         param:
>>>>>           level: debug
>>>>>           condition:       %SF_WEB_DEBUG%
>>>>>           xdebug_logging:  false
>>>>>           web_debug_class: fsWebDebugForSf12
>>>>>
>>>>> The only difference here with the default symfony 1.2 factories.yml
>>>>> is
>>>>> the entry: web_debug_class: fsWebDebugForSf11   (I turned off
>>>>> xdebug_logging, but that shouldn't affect the plugin)
>>>>>
>>>>> If you follow this steps (depending on the symfony version you are
>>>>> using) it should work. Please let me know any issues. Also I will
>>>>> post
>>>>> this on the google group of the extension/plugin.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Alvaro
>>>>>
>>>>>
>>>>>
>>>>> On Oct 3, 2008, at 2:39 AM, Kiril Angov wrote:
>>>>>
>>>>>>
>>>>>> Good for the plugin but you probably so much time developing it
>>>>>> (them)
>>>>>> but your README us very unclear. Remember Symfony 1.2 is not
>>>>>> documented very well yet and just saying  "Edit the factories.yml
>>>>>> file
>>>>>> of your application and change the following entry:
>>>>>> web_debug_class:
>>>>>> fsWebDebug", does not mean anything. So how exactly do you enable
>>>>>> the
>>>>>> plugin?
>>>>>>
>>>>>> Thanks,
>>>>>> Kiril
>>>>>>
>>>>>> On Thu, Oct 2, 2008 at 8:34 AM, alvaro <[EMAIL PROTECTED]>
>>>>>> wrote:
>>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I just released the FireSymfony extension for Firebug and the
>>>>>>> plugin
>>>>>>> for symfony 1.2
>>>>>>>
>>>>>>> http://obvioushints.blogspot.com/2008/10/firesymfony-first-release-is-out.html
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Alvaro
>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Lucas Stephanou
>>>>
>>>>>
>>>> <fireSymfonyError.png>
>>>
>>>
>>>>
>>>
>>
>>
>>
>> --
>> Lucas Stephanou
>>
>> >
>
>
> >
>



-- 
Lucas Stephanou

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to