[dev] (no subject)

[Michael Rubinsky]

OK. This is really strange.  I'm trying to add a <configspecial> entry  
in Turba's configuration. It seems that if you do a  $registry->call()  
from Config.php and then generate the file so that it is actually  
*written* to disk, any further attempts to use *any* of Horde fatals  
with "<appname> is not activated."

If you just view the configuration page without generating the file,  
or if the file generation fails due to lack of permissions then there  
is no problem.

Even stranger is replacing horde/config/registry.php with the .dist  
version restores functionality - no matter what application you are  
attempting to edit configuration for.  A diff shows no differences  
between the files and permissions are correct etc...  Also, closing  
and opening the browser will also restore functionality.

I have removed the phpa cache extension from php.ini, so it is not a  
byte code cache problem...

What is really confusing me is that just viewing the page (which is  
calling the api function since the values are populated as expected)  
doesn't break anything...it's only once the conf.php page is written  
that causes the problem.

Am I missing something really obvious here that I haven't checked -  
maybe some type of horde cache issue?

Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk at horde.org