[resolved] only get 404 response - bad configuration or missing dependency?

[seanr]

I'm getting symfony 1.0beta installed on a remote server (linux) for the first time and I'm having configuration problems. I am unable to access my index.php (or fooapp_dev.php). My local instance is running on OS X without any problems.

It is the same project on both computers, but on the remote server I only get the "Oops! Page Not Found The server returned a 404 response" response. This is what I am seeing on the remote server via the symfony toobar:

Code: Select all

1    Context   initialization
2    Controller   initialization
3    Routing   match route [homepage] "/"
4    Request   request parameters array ( 'module' => 'Survey', 'action' => 'list',)
5    Controller   dispatch request
6    Controller   action does not exist
7    Filter   executing filter "sfRenderingFilter"
8    Filter   executing filter "sfWebDebugFilter"
9    Filter   executing filter "sfCommonFilter"
10    Filter   executing filter "sfFlashFilter"
11    Filter   executing filter "sfExecutionFilter"
12    Action   change layout to "sf_root_dir/config/../data/symfony/modules/default/templates/defaultLayout"
13    Action   call "defaultActions->executeError404()"
14    View   initialize view for "default/error404"
15    View   render "sf_root_dir/config/../data/symfony/modules/default/templates/error404Success.php"
16    View   decorate content with "sf_root_dir/config/../data/symfony/modules/default/templates/defaultLayout.php"
17    View   render "sf_root_dir/config/../data/symfony/modules/default/templates/defaultLayout.php"

and on my local instance I see:

Code: Select all

1    Context   initialization
2    Controller   initialization
3    Routing   match route [homepage] "/"
4    Request   request parameters array ( 'module' => 'Survey', 'action' => 'list',)
5    User   automatic user logout
6    User   user is not authenticated
7    Controller   dispatch request
8    Filter   executing filter "sfRenderingFilter"
9    Filter   executing filter "sfWebDebugFilter"
10    Filter   executing filter "sfCommonFilter"
11    Filter   executing filter "sfFlashFilter"
12    Filter   executing filter "sfExecutionFilter"
13    Action   call "surveyActions->executeList()"
14    View   initialize view for "Survey/list"
15    View   render "sf_root_dir/cache/frontend/dev/modules/autoSurvey/templates/listSuccess.php"
16    View   initialize view for "Survey/_list_header"
[etc...]

I'm not sure what other details would be helpful... let me know and I'll follow up with them more info...

Thank you,
Sean

[tamcy]

Module and action names are case sensitive. You may check if the directory and action name match exactly to what you type on the address bar.

[N_Ox]

Actually, I am facing the same problem, I have two old propel-admin modules that can't stop giving 404 errors. The strange thing is that default propel-admin modules and newly created modules work.

EDIT : The problem had ABSOLUTELY nothing to do with a 404 error curse, just a mispelled sfActions class name in the authentication module, the mad ones were secured.

[seanr]

accidental post - delete me