I mashed together your NoRoute and bigroom.co.uk's and I did end up using ReflectionClass. Do you have any idea what kind of performance hit this may have in big projects? With catching the exception, the 404 code would only be executed if it doesn't exist in the first place, but using reflection it's done every time. It is, however, nice to have all the 404 stuff contained in one nice plugin.

Sometimes I put private functions in my controllers, like little helpers that really don't deserve to go elsewhere (e.g. filtering and validating the same post/get data on multiple actions). To display a 404 for private functions you have to then also use ReflectionMethod. But, although this may have been obvious, I noticed a better way to hide protected functions in controllers.

Don't do:
private function validateAction()

Do:
private function validate()

Because there's no Action at the end, to the dispatcher (and how I used ReflectionClass) it looks like it doesn't exist at all. Now I just need to make sure that I don't add "Action" to the end of method names out of habit (which is why it took me so long to notice this feature in the first place).

You could probably do some reflection to work out if the action function exists in the controller class.

It's easier to catch the exception to be honest :)

Regards,

Rob…

Is there an easy way to make this work with non existent actions as well, rather than a __call in every controller?

Instead of using a plugin I've thought about catching exceptions from dispatch() but that's just not as nice.

In these cases, don't use initView()

:)

Regards,

Rob…

Regards,

Rob…

zf-tutorial/application/views/indexDelete.tpl.php

become :
zf-tutorial/application/views/scripts/index/delete.phtml

Seems It will not work.

Part of code from initView() method:
"
$baseDir = dirname($dirs[$module]) . DIRECTORY_SEPARATOR . 'views';
if (!file_exists($baseDir) || !is_dir($baseDir)) {
throw new Zend_Controller_Exception('Missing base view directory ("' . $baseDir . '")');
}
"

So, Zend expect that the view directory must by in subdirectory 'view' in the same directory where controller placed(and it generates exception in other case). It can be a little bit inconveniently in some projects, I think.

What I mean is that the call to $this->initView() in the action's init() handles setting up the path to the view templates.

I don't see why you can't override it with a call to $this->view->setScriptPath() after the call to $this->initView() though.

Regards,

Rob…

" It also sets up the Zend_View object to look in
views/scripts/{controller name} for the view scripts to be rendered
"

I've tried use: $this->view->setScriptPath('../user/templates');

But it didn't work.