[fw-general] Best way to setup a Default controller that will be called if controller not found

2012-01-25 Thread Adam Dear
Hello, I am just starting to learn Zend Framework. As an exercise to learn the framework, I am creating a new site for my wife to showcase her handmade merchandise. On this site, as with most all sites, there will be quite a few purely informational pages (About, Contact info, etc.). My

RE: [fw-general] Best way to setup a Default controller that will be called if controller not found

2012-01-25 Thread Wilson Revehl (Go Media Inc.)
Hi Adam, I think you'll appreciate ZF once you get a grip on the magic with the way it handles URL routing. http://framework.zend.com/manual/en/zend.controller.router.html The default route, which you *shouldn't* have to stray from is url /:module/:controller/:action. ZF gets its params for

Re: [fw-general] Best way to setup a Default controller that will be called if controller not found

2012-01-25 Thread Hector Virgen
On Wed, Jan 25, 2012 at 7:20 AM, Adam Dear addrum...@gmail.com wrote: Is the proper way to create a custom route that routes every request to my default controller, and then define routes that send requests to few actual controllers that will exist or is there a mechanism that I could use in

RE: [fw-general] Best way to setup a Default controller that will be called if controller not found

2012-01-25 Thread Wilson Revehl (Go Media Inc.)
Wow, that's pretty wild (card) Hector! I haven't had a reason to do anything beyond a default front controller. Not sure if it would be more resource efficient, but you can simply set useDefaultControllerAlways = true; and loop all non existant controllers to your default action. I haven't

Re: [fw-general] Best way to setup a Default controller that will be called if controller not found

2012-01-25 Thread Adam Dear
Hector, I appreciate the help. I decided to use this method with the slight change of deciding to define the static pages with a .html extension. Continuing with the example I've been using, I'll access the non-controller pages using, for example, mysite.com/About-Us.html,