Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
it’s probably obvious because i didn’t find anyone who talk’s about it:
there is module/controller/action – but what if the website depth is much deeper
?
for example:
module/controller/action/sub-page(s)/sub-sub-page(s)/and so on..
is routes is the correct way for it?:
puting the action for the module/controller/action/sub-page in the controller and making a route for it.
Am i missing something or this is the way to do it?
The Sub-page is a actually not a Sub-page but still rendered by an view script that refers to an controller/action.
Your logic would mean that after the view script is again a controller/action but this is not correct and would violate MVC structure.
Read Zend Framework & MVC Introduction.