| [SOLVED]Need help solving problem [message #32691] |
Wed, 01 August 2007 13:32  |
 fareasd
Messages: 29
Registered: May 2007 |
Junior Member |
|
|
everything works as expected, but in development mode i see this erorr ?
what is it how can I resolve this error ?
Thanks in advance
Fatal error: Uncaught exception 'sfStopException' in /usr/share/pear/symfony/action/sfAction.class.php:136 Stack trace: #0
/home/develop.interfeis.lv/www/arhiv/apps/frontend/modules/main/actions/actions.class.php(57): sfAction->forward('main', 'book') #1
/usr/share/pear/symfony/action/sfActions.class.php(53): mainActions->executeMenu() #2
/usr/share/pear/symfony/filter/sfExecutionFilter.class.php(115): sfActions->execute() #3
/usr/share/pear/symfony/filter/sfFilterChain.class.php(43): sfExecutionFilter->execute(Object(sfFilterChain)) #4
/usr/share/pear/symfony/filter/sfFlashFilter.class.php(50): sfFilterChain->execute() #5
/usr/share/pear/symfony/filter/sfFilterChain.class.php(43): sfFlashFilter->execute(Object(sfFilterChain)) #6
/usr/share/pear/symfony/filter/sfCommonFilter.class.php(29): sfFilterChain->execute() #7
/usr/share/pear/symfony/filter/sfFilterChain.class.php(43): sfCommonFilter->execute(Object(sfFilterChain)) #8
/usr/share/pear/symfony/filter/sfWebDebugFilter.class.php(35): sfFilterChain->execute() #9
/usr/sh in /usr/share/pear/symfony/action/sfAction.class.php on line 136
[Updated on: Wed, 22 August 2007 16:41]
|
|
|
| sfStopException after upgrade [message #33867 is a reply to message #32691 ] |
Wed, 22 August 2007 10:51  |
refactored
Messages: 8
Registered: August 2007 |
Junior Member |
|
|
fareasd please make your post title clearer. It will attract more attention if you go beyond simply asking for help.
sfStopException is normally caught and ignored by symfony. Since it is getting past the framework in only one environment narrow it down by switching off features enabled in this environment until it stops happening.
After upgrading to symfony 1.0.6, I am also getting the very same error in my fully instrumented 'dev' environment and nowhere else.
[Updated on: Wed, 22 August 2007 11:59]
|
|
|
| sfStopException after PHP/eAccelerator Upgrade [message #33885 is a reply to message #33867 ] |
Wed, 22 August 2007 11:56 |
refactored
Messages: 8
Registered: August 2007 |
Junior Member |
|
|
sfStopException is normally caught and ignored by symfony. You shouldn't see it. I began seeing it only after upgrading the runtime environment on my Windows XP Pro box:
symfony (1.0.5 -> 1.0.6)
PHP (5.1.6 -> 5.2.3)
eAccelerator (0.9.5 for PHP 5.1.6 -> 0.9.5.1 for PHP 5.2.3)
xDebug (2.0.0.rc4 for PHP 5.1.2 -> 2.0.0 for PHP 5.2.2).
Enabling eAccelerator in this new environment results in the exception. Doesn't matter if xDebug is enabled or not.
Why, I don't know. The condition is deterministic, meaning it will repeat given the same conditions.
Ticket open at symfony-forge:
http://www.symfony-forge.com/trac/ticket/1838
Can anyone shed more light on this one?
[Updated on: Wed, 22 August 2007 12:14]
|
|
|
|
|
Members
Search
FAQ
Register
Login
Home
