Having functions that are not actions in a controller seems to result in an unexpected error type.
For example, if I have the protected function _protFunc() and accidentally call $this->_protFunk(), an EXCEPTION_NO_ACTION is generated by the ErrorHandler Plugin. But EXCEPTION_NO_ACTION is specifically defined as a situation in which the correct controller is called but an incorrect action is called. Is this by design? Should users not have non-action functions inside a controller? If it should be OK to have non-action functions inside a controller, then it seems that EXCEPTION_OTHER should be called rather than EXCEPTION_NO_ACTION (which is when one would usually display a 404 type page). -- View this message in context: http://www.nabble.com/Unexpected-EXCEPTION_NO_ACTION-from-ErrorHandler-tp15054625s16154p15054625.html Sent from the Zend Framework mailing list archive at Nabble.com.
