StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The easiest way to configure routing is by using the <a href="http://framework.zend.com/manual/en/zend.application.available-resources.html#zend.application.available-resources.router" rel="nofollow"><code>Zend_Application_Resource_Router</code></a>.</p> <p>Configuration goes in your <code>application.ini</code> file and that's it, no further code required.</p> <p>As it appears you're using a static route (no variable path components), try this in your <code>application.ini</code> file</p> <pre><code>resources.router.routes.guestbook.type = "Zend_Controller_Router_Route_Static" resources.router.routes.guestbook.route = "guestbook" resources.router.routes.guestbook.defaults.module = "default" resources.router.routes.guestbook.defaults.controller = "guestbook" resources.router.routes.guestbook.defaults.action = "index" </code></pre> <p>Remove the <code>_initRoutes()</code> method from your <code>Bootstrap</code> class.</p> <hr> <p>Also, this is just an aside but when using other resources such as the front controller in a bootstrap <code>_init*</code> method, you <strong>must</strong> ensure they've been properly bootstrapped. To do so, retrieve them like this</p> <pre><code>protected function _initSomething() { // make sure resource is bootstrapped $this->bootstrap('frontController'); // retrieve resource $front = $this->getResource('frontController'); } </code></pre> <p>See <a href="http://framework.zend.com/manual/en/zend.application.theory-of-operation.html#zend.application.theory-of-operation.bootstrap.dependency-tracking" rel="nofollow">http://framework.zend.com/manual/en/zend.application.theory-of-operation.html#zend.application.theory-of-operation.bootstrap.dependency-tracking</a></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload