The answer you provided doesn't seem to make much sense, if you are saying you added <?php
to the top of the file where your class is written, all I can say is "Welcome to PHP!"
otherwise the following may help in the future... or not.
Using the master application.ini
from feibeck as a reference, I came up with:
//excerpt from application.ini
resources.view.helperPath = APPLICATION_PATH "/views/helpers"
resources.view.helperPathPrefix = "My_View_Helper"
however you are using the defaults for the MVC so you shouldn't require any config at all.
This may be a case of too much config.
That being said:
I've never been a fan of setting view options in the application.ini
as I'm never quite sure of what effect I should expect (am I adding or setting an option?). I much prefer to setup the view in the bootstrap as most of the methods used are more verbose and tell a more complete story:
//bootstrap.php
protected function _initView()
{
//Initialize view
$view = new Zend_View();
//add custom view helper path
$view->addHelperPath(APPLICATION_PATH . '/../library/My/View/Helper');
//add custom script path for partials
$view->addScriptPath(APPLICATION_PATH . '/../library/My/View/Scripts/');
//set css includes, path is relative to /public
$view->headlink()->setStylesheet('/bootstrap/css/bootstrap.css');
//add javascript files, path is relative to /public
$view->headScript()->setFile('/bootstrap/js/jquery.min.js');
$view->headScript()->appendFile('/bootstrap/js/bootstrap.min.js');
//add it to the view renderer
$viewRenderer = Zend_Controller_Action_HelperBroker::getStaticHelper(
'ViewRenderer');
$viewRenderer->setView($view);
//Return it, so that it can be stored by the bootstrap
return $view;
}
Hope this provides some help.