Issue 500: move default template routing into the routing system
http://code.google.com/p/qubit-toolkit/issues/detail?id=500

New issue report by vangarderen.peter:
- stop the use of setTemplate() calls in the default
create,edit,show,update actions
- assign the standard/template context (e.g. 'rad', 'isad', 'dc') to a
$routing object default parameter in each of the actions
- use the routing.yml rules to infer the correct action to call (e.g.
editRad, editIsad) if a generic action is being called (e.g.
informationobject/edit)
- this solves bug#1: 'dead-end' action/template logic (e.g. routing to an
editRad template without running the editRad action)
- this solves bug#2: 'informationobject/show' being called from _treeview
will route to the correct standard template that is currently in scope


Issue attributes:
        Status: Accepted
        Owner: vangarderen.peter
        Labels: Type-Defect Priority-High Milestone-Release-1.0.4

-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Qubit Toolkit Issues" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/qubit-issues?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to