Hi,
I hope I am understanding your question but why don't you store you ini file
contents in Zend_Registry?
e.g.
config.ini
[general]
param1 = Me
param2 = You
Bootstrap.php
$configPath = './application/config/';
$config = new Zend_Config_Ini($configPath . 'config.ini', null, true);
Zend_Registry::set('config', $config);
You can then call get ini file settings easily anywhere in your application
using:
$var = Zend_Registry::get('config')->general->param1;
- Robert
-----Original Message-----
From: Eugen_cro [mailto:[EMAIL PROTECTED]
Sent: Wed 22/10/2008 09:18
To: [email protected]
Subject: Re: [fw-general] Major Issues with Zend Auth
Matthew Ishii wrote:
>
> Matthew,
>
> Unfortunately, after comparing the logout functionality between my app
> and the one you mentioned, I do not see any differences at all. What
> I did notice though, was an awful lot of my instantiating a
> configuration object out of the Zend_Registry. In fact I am doing it
> too much and in too many places. What I need to do is understand how
> I can get one copy of the config object (which is $config = new
> Zend_Config_Ini('../application/configuration.ini', null, false);) and
> set it so that all view level scripts can access it, such as my
> navigation includes in the layout level and the individual controller
> view scripts such as index.phtml and the like. Im currently pulling
> out this object in each script where I need it, but I would feel more
> secure about the code if I could share one common object.
>
> Anyway, Im convinced it isnt the way im calling the logout directives,
> as they look identical to yours, it must be something in the way i am
> doing the structure, or some kind of logic problem.
>
>
well one option is that you make base controller class My_Base_Controller
extends Zend_Controller_Action and in there you place all code that needs to
be accessible to your controllers.. Then all your controllers will be
extends of that base controller class IndexController extends
Zend_Controller_Action
Im sure Matthew have some other proposals but i think this is most straight
forward approach and most simple to get working..
--
View this message in context:
http://www.nabble.com/Major-Issues-with-Zend-Auth-tp20097127p20106060.html
Sent from the Zend Framework mailing list archive at Nabble.com.
________________________________________________________________________
This email has been scanned for all known viruses by the MessageLabs Email
Security Service and the Macro 4 plc internal virus protection system.
________________________________________________________________________
________________________________________________________________________
This email has been scanned for all known viruses by the MessageLabs Email
Security Service and the Macro 4 plc internal virus protection system.
________________________________________________________________________
