agaul wrote:
> Sorry for the rare informations. Here's the logfile for one request.
>
> Sep 17 20:49:29 symfony [info] {sfRouting} connect "/login"
> Sep 17 20:49:29 symfony [info] {sfRouting} connect "/logout"
> Sep 17 20:49:29 symfony [info] {sfRouting} connect "/request_password"
> Sep 17 20:49:29 symfony [info] {sfContext} initialization
> Sep 17 20:49:29 symfony [info] {sfController} initialization
> Sep 17 20:49:29 symfony [info] {sfRouting} match route [default_index]
> "/:module"
> Sep 17 20:49:29 symfony [info] {sfRequest} request parameters array
> (  'module' => 'frontend_dev.php',  'action' => 'index',)
> Sep 17 20:49:29 symfony [info] {sfController} dispatch request
> Sep 17 20:49:29 symfony [info] {sfController} action does not exist
> Sep 17 20:49:29 symfony [info] {sfFilter} executing filter
> "sfRenderingFilter"
> Sep 17 20:49:29 symfony [info] {sfFilter} executing filter
> "sfWebDebugFilter"
> Sep 17 20:49:29 symfony [info] {sfFilter} executing filter
> "sfGuardBasicSecurityFilter"
> Sep 17 20:49:29 symfony [info] {sfFilter} executing filter
> "sfRenderingFilter"
> Sep 17 20:49:29 symfony [info] {sfFilter} executing filter
> "sfWebDebugFilter"
> Sep 17 20:49:29 symfony [info] {sfFilter} executing filter
> "sfGuardBasicSecurityFilter"
> Sep 17 20:49:29 symfony [info] {sfFilter} executing filter
> "sfCommonFilter"
> Sep 17 20:49:29 symfony [info] {sfFilter} executing filter
> "sfFlashFilter"
> Sep 17 20:49:29 symfony [info] {sfFilter} executing filter
> "sfExecutionFilter"
> Sep 17 20:49:29 symfony [info] {sfValidator} validation execution
> Sep 17 20:49:29 symfony [info] {sfAction} call "sfGuardAuthActions-
>   
>> executeSignin()"
>>     
> Sep 17 20:49:29 symfony [info] {sfView} initialize view for
> "sfGuardAuth/signin"
> Sep 17 20:49:29 symfony [info] {sfView} render "/html/symfony/plugins/
> sfGuardPlugin/modules/sfGuardAuth/templates/signinSuccess.php"
> Sep 17 20:49:29 symfony [info] {sfView} decorate content with "/html/
> symfony/apps/frontend/templates/layout.php"
> Sep 17 20:49:29 symfony [info] {sfView} render "/html/symfony/apps/
> frontend/templates/layout.php"
> Sep 17 20:49:29 symfony [info] {sfFilter} render to client
> Sep 17 20:49:29 symfony [info] {sfResponse} send status "HTTP/1.0 404
> Not Found"
> Sep 17 20:49:29 symfony [info] {sfResponse} send header "Status": "404
> Not Found"
> Sep 17 20:49:29 symfony [info] {sfResponse} send header "Content-
> Type": "text/html; charset=utf-8"
> Sep 17 20:49:29 symfony [info] {sfResponse} send content (23243 o)
> Sep 17 20:49:29 symfony [info] {sfTimerManager} Configuration 4.08 ms
> (16)
> Sep 17 20:49:29 symfony [info] {sfTimerManager} Action "sfGuardAuth/
> signin" 0.18 ms (1)
> Sep 17 20:49:29 symfony [info] {sfTimerManager} View "Success" for
> "sfGuardAuth/signin" 16.29 ms (1)
>
> Adding the "die" into the index.php causes no effect when calling the
> frontend_dev.php.
>
> A little more background-information: I'm wanted to deploy on a shared
> server as describled in the symfony-book on chapter 19 ("Modifying the
> Project Web Root").
>
> I it enough information now?
>
>
> >
>
>   
Try to put in the beginning of frontend_dev.php

die($_SERVER['PATH_INFO']);

and see if it will show 'fronend_deb.php/index' or only 'index'. If it 
is the first one then your shared hosting has a configuration which does 
not populate PATH_INFO correctly. What I would suggest then is to put

phpinfo(); exit;

at the top of frontend_dev.php and call it with 
frontend_dev.php/general/index and then see which one from the $_SERVER 
variables has the correct value. Sorry I cannot be more specific but 
that's how I would troubleshoot the problem.

HTH,
Kupo

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

Reply via email to