The second parameter to addHelperPath is the prefix for the view helpers, you could try passing an empty string or NULL/no argument (as you have no prefix).

However I am not getting any further. I am still having the same problem:

$view = new Zend_View(); $mypath=$this->view->getHelperPaths(); $view->addHelperPath($mypath['Login_View_Helper_'][0], ‘RenderIfExists’); $this->renderIfExists(‘login.phtml’);

Above code gives me the error:
Message: Method “renderIfExists” does not exist and was not trapped in __call().

My path to my helper is correct. I’ve checked it with echo $mypath['Login_View_Helper_'][0]

Any ideas where to look for a solution?

$view = new Zend_View();
$view->addHelperPath(‘Path/To/Helper’, ‘Pro_View_Helper’);

If you are using full ZF MVC then you can add additional lines of config to your application.ini:

resources.view.helperPath.Pro_View_Helper = “Path/To/Helpers”

How can I implement this into Zend? I can’t get it to work. I placed the file in my /library directory but I am keep getting an error:
Message: Method “renderIfExists” does not exist and was not trapped in __call()

What do I need to do to finally get it to work?

Thanks in advance!

With the implementation I used I’d simply filter the navigation tree to the module I was in which meant that you only get the relevant pages. Navigation set up something like:

- Master link
– Admin module
—- Index
—- etc
– Public module (default)
—- Index
—- etc

So only displaying links from ‘admin module’ down in my admin module hides links I don’t want the user to see.

Thanks for replying. I actually got my module based navigation working by modifying your solution above. I cant thank you enough, i was struggling on this issue for around 2 days.

I have actually implemented an ACL system but when on the admin side of my system I do not want any of the main navigation to be visible, but still have access to the main side of the system. In my head module based navigation was the way forward, it just seemed a cleaner approach.

Regards,
-Ben

This was really helpful, thanks. At the moment i am having real trouble implementing a module specific navigation plugin. Could this solution for layouts be applied to navigation?

-Ben

resources.router.routes.sitemap.type = “Zend_Controller_Router_Route_Static”
resources.router.routes.sitemap.route = “sitemap.xml”
resources.router.routes.sitemap.controller = “index”
resources.router.routes.sitemap.action = “sitemap”
resources.router.routes.sitemap.defaults.module = “www”
resources.router.routes.sitemap.defaults.controller = “index”
resources.router.routes.sitemap.defaults.action = “sitemap”
resources.router.routes.sitemap.defaults.route = “www-index”

I have router.ini

resources.router.routes.sitemap.type = “Zend_Controller_Router_Route”
resources.router.routes.sitemap.route = “sitemap.xml”
resources.router.routes.sitemap.defaults.controller = index
resources.router.routes.sitemap.defaults.action = sitemap

and bootstrap.php

protected function _initRouter()
{
$frontController = Zend_Controller_Front::getInstance();
$config = new Zend_Config_Ini(APPLICATION_PATH . ‘/config/router.ini’);
$router = $frontController->getRouter();
$router->addConfig($config, ‘router’);
}

and I receive this error:

Exception information:

Message: Invalid controller specified (sitemap.xml)

Request Parameters:

array (
‘controller’ => ‘sitemap.xml’,
‘action’ => ‘index’,
‘module’ => ‘default’,
)

Guessing you’re not using modules? But if so your model should be called _News for ZF to pick up by default (I don’t use this system myself).

I’d suggest checking the include path from your bootstrap method to see if it contains “application/models” or include the file manually.

Guessing you’re not using modules? But if so your model should be called _News for ZF to pick up by default (I don’t use this system myself).

I’d suggest checking the include path from your bootstrap method to see if it contains “application/models” or include the file manually.

I think it can be too easy to stay in your comfort zone in terms of using what you know, especially when you are under pressure of deadlines. The 5.3 exam certainly forces you to look at some of those areas you might otherwise avoid.

I wouldn’t hesitate to recommend ZCE (PHP 5.3) certification to anyone.

moduleName.db.user = ”
moduleName.db.password = ”
moduleName2.db.user = ”
…etc…

Then simply generate your database connection as you see fit (Zend_Db::factory() or similar) and stash it away in the registry or set it as the default adapter if using Zend_Db_Table (Zend_Db_Table::setDefaultAdapter()).

FROM: http://www.evilprofessor.co.uk/334-zend-certified-engineer-zce-5-3/

The exam itself follows the description of the previous exams. I was slightly worried about questions covering the new 5.3 features but I this was unfounded,…

I definitely found the process worthwhile. Brushing up on aspects of php/related technologies that I wouldn’t necessarily need very often, as well as learning why certain things work the way they do has certainly improved my programming I feel.

In the getInstance() example the class is instantiated like:
$class = Class::getInstance();
Rather than:
$class = new Class();
Generally this is used when implementing the singleton pattern.

Thanks

For example my latest project uses the following routing:

; ==============================
; Resource Routing
; ==============================
resources.router.routes.www.type = “Zend_Controller_Router_Route_Hostname”
resources.router.routes.www.route = “:module.example.com”
resources.router.routes.www.defaults.module = “default”
resources.router.routes.www.chains.index.type = “Zend_Controller_Router_Route”
resources.router.routes.www.chains.index.route = “:controller/:action/*”
resources.router.routes.www.chains.index.defaults.controller = “index”
resources.router.routes.www.chains.index.defaults.action = “index”
resources.router.routes.sitemap.type = “Zend_Controller_Router_Route”
resources.router.routes.sitemap.route = “sitemap.xml”
resources.router.routes.sitemap.defaults.controller = index
resources.router.routes.sitemap.defaults.action = sitemap

Therefore in my navigation.xml (or whatever config you decide to use), you’ll need to specify the routing to use, e.g.

default.pro.pages.aboutUs.label = “Company profile”
default.pro.pages.aboutUs.module = “www”
default.pro.pages.aboutUs.controller = “about-us”
default.pro.pages.aboutUs.action = “index”
default.pro.pages.aboutUs.resource = “www_pages”
default.pro.pages.aboutUs.route = “www-index”

Can you give me a call when you get 5 minutes please.

Darren

I Googled for something completely different, but found your page…and have to say thanks. nice read….