Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COOh i see, thanks for the reply, but the thing I want to do is: Depend on how many parameters I have on the URI, the Controller_Action I will use to render. So I can define at router level that if the forum controller gets the first parameter will be rendered with the "sectionAction" and if I've two parameters I will render with the "topicAction" where I only have to do something like `public function sectionAction() { $section = $this->_request->getParam('section'); //@TODO : get from Db and render }` Is that possible to be done with Zend_Controller_Router?
      singulars
    2. COI done something like that in codeIgniter, where on the routes config I set an Array like `$routes['forum/(a-z)'] = 'forum/section'` and to match the second parameter just add a new router filter like : `$routes['forum/(a-z)/(a-z)'] = 'forum/topic'` Is that possible to match with Zend Routers? like a redirect, but only get the uri parameters and redirect to the needed action.
      singulars
    3. COCodeigniter uses segment based check whereas zend checks for the request! so there is no such thing as 'segment' but, u fetch things using Request-Param... Here, as I mentioned you will have to re-plan the application... actions come under controllers... Example, Users controller can have view,add,amend,delete.. routes are used for example routes - "my-dashboard" which routes to User controller - tools and options action... Cool?
      singulars
 

Querying!

 
Guidance

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