ZF-10924: Zend_Controller_Action::__call assumes formatActionName() result

Issue Type:
Bug
Created:
2011-01-07T04:09:55.000+0000
Last Updated:
2011-01-07T04:49:09.000+0000
Status:
Postponed
Fix version(s):
    Reporter:
    Pablo Grass (grass)
    Assignee:
    Matthew Weier O'Phinney (matthew)
    Tags:
    • Zend_Controller
    Related issues:
    Attachments:

    Description

    The __call method, trying to describe an occured error, uses a hard-coded, own implementation

    Zend/Controller/Action.php, line 483 [code] if ('Action' == substr($methodName, -6)) { [/code]

    to detect if the user tried to call an (non existing) action or method. If a user does not rely on Zend_Controller_Dispatcher_Abstract's formatActionName() but uses his onw dispatcher, the exception thrown is misleading, as indicating call to an action where a method was called and vice-versa.

    Comments

    Posted by Richard Tuin (richardtuin) on 2011-01-07T04:24:27.000+0000

    As far as i know this problem is identified in the ZF2 MVC interface proposals and planned to redesign in ZF2's MVC implementation.

    Find more information here.

    Posted by Matthew Weier O'Phinney (matthew) on 2011-01-07T04:49:02.000+0000

    Richard is correct -- fixes for this are planned for ZF2. For now, you will need to override the __call() method in your controllers (or a base controller you define) in order to alter the behavior.