#1317: Forward system action error_404 never gets set from the
AgaviExecutionContainer
----------------------------------+-----------------------------------------
Reporter: m...@… | Owner: david
Type: defect | Status: new
Priority: normal | Milestone: 1.0.4
Component: controller | Version: 1.0.3
Severity: normal | Keywords:
Has_patch: 0 |
----------------------------------+-----------------------------------------
All system_actions go thru the condition in AgaviExecutionContainer, where
the NS 'org.agavi.controller.forwards.X' gets set for 'unavailable',
'login', 'secure'... etc except for 'error_404'.
Well, around the ending lines of AgaviRouting::execute() the action and
module names get set like this:
$container->setModuleName(AgaviConfig::get('actions.error_404_module'));
$container->setActionName(AgaviConfig::get('actions.error_404_action'));
This prevents the AgaviExecutionContainer from action accordingly for
error_404, since the checking of the file is correct. AgaviRouting needs
to do something different in order for
createSystemActionForwardContainer() to work with error_404 the same way
the rest of the system actions.
--
Ticket URL: <http://trac.agavi.org/ticket/1317>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
