Nevermind, Zend_Application must do this by default.
Creating a new template project in ZS on both machines return the same result. No "action" param when requested controllers/action doesn't exists, with the following in the application.ini resources.frontController.defaultModule = "default" resources.frontController.defaultControllerName = "index" resources.frontController.defaultAction = "index" resources.frontController.useDefaultControllerAlways = true -----Original Message----- From: Terre Porter [mailto:[email protected]] Sent: Monday, August 03, 2009 1:53 PM To: [email protected] Subject: [fw-general] execution order for the Zend_Application style? What's the execution order for the Zend_Application style design? I found this but it seems to refer to the older style not using the zend_application. http://www.kitpages.fr/cms/site/tutoriaux/sequence_globale.jpg I'm attempting to trace down where the code loses the action parameter. (see other message below) I've put in dump statements trying to find the spot where it strips the action param. In my empty acl plugin file I've added in a preDispatch and postDispatch function I have the following: ~--- public function preDispatch(Zend_Controller_Request_Abstract $request) { Zend_Debug::dump( 'AclMgr: preDispatch'); Zend_Debug::dump( $request->getParams()); } ~---- --> ACL Plugin: preDispatch ----> params array(3) { ["controller"] => string(5) "atest" ["action"] => string(8) "somthing" ["module"] => string(7) "default" } *** I contains the action param. A similar function in the IndexController for init the indexAction is missing the action param. *** --> IndexController: init ----> params array(2) { ["controller"] => string(5) "atest" ["module"] => string(7) "default" } --> AclMgr: postDispatch ----> params array(2) { ["controller"] => string(5) "atest" ["module"] => string(7) "default" } **** This exact code works on another machine with out problems, the action param is not striped out of the request. What other functions can I use that are between the ACL:preDispatch and the IndexController:init so that I can dump the page params ? -----Original Message----- From: Terre Porter [mailto:[email protected]] Sent: Sunday, August 02, 2009 10:14 PM To: [email protected] Subject: [fw-general] request missing action param Hello, I made a new VMware devbox the other day and noticed an odd issues today when attempting to use the framework on it. Something on my new box is causing the framework to lose the action param. I use a copy of a pre-build centos image, then installed virtualmin/webmin, installed and setup samba, configured the website home directory to be shared, then created a project in ZS, and went to making the site modular. I added this in the Index action of the default index controller : Zend_Debug::dump($this->getRequest()->getParams()); There is no controller or action for this request, this is falling back to the default controller, per being set in the application.ini file. I get the following: Old Dev: testsite.dev1\atest\somthing array(3) { ["controller"] => string(5) "atest" ["action"] => string(8) "something" ["module"] => string(7) "default" } New Dev: testsite.dev2\atest\somthing array(2) { ["controller"] => string(5) "atest" ["module"] => string(7) "default" } I've tried both version 1.8.3 and 1.9.0 or the frameword with the same results. I think this means its not a framework direct problem. But what could be causing it on the server? I've compared the php.ini files there is nothing that jumps out as a problem or really that different. Anyone had this problem before or got any ideas? Thanks Terre
