Question

In zend framework I register my namespace like this (in application.php):

'autoloaderNamespaces' => array(
    'Cms_'
)

And after this – I’d expect that Zend would always check that path in addition to Zend and ZendX paths if unknown class is called. But for some reason this doesn’t work with for example view helpers.

I still have to register a separate path for my view helpers even though view helper scripts are named according to Zend coding standards and are located in:

Cms/View/Helper/

And this is how I register helper path in config file:

view' => array(
    'charset' => 'UTF-8',
    'doctype' => 'XHTML1_TRANSITIONAL',
    'helperPath' => array(
        'Cms_View_Helper_' => 'Cms/View/Helper'
        )
),

So – I’m not sure why I have to register “Cms” namespace twice first through ‘autoloaderNamespaces’ and then through View “helperPath”? Shouldn’t Cms namespace include Cms/View/Helper namespace?

can someone plz clarify this:)

Answer 1

I believe it is exactly as you describe, the documentation on custom view helpers is pretty explicit about it:

You may, and should, give the class name a prefix, and it is recommended that you use ‘View_Helper’ as part of that prefix: “My_View_Helper_SpecialPurpose”. (You will need to pass in the prefix, with or without the trailing underscore, to addHelperPath() or setHelperPath()).

This does make some sense to me though. In theory you could build a library of generic view helpers that could be re-used across multiple applications, so binding them to a specific application namespace would be inconvenient, i.e. if all my helpers were prefixed ‘MyApp_’ I would have to rename them to be able to use them in ‘MyOtherApp’.