[Tickets #3304] NEW: Registry losing applications after api calls from configuration screens

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://dev.horde.org/horde/whups/ticket/?id=3304
-----------------------------------------------------------------------
 Ticket             | 3304
 Created By         | Michael Rubinsky <mrubinsk at horde.org>
 Summary            | Registry losing applications after api calls from configuration screens
 Queue              | Horde Framework Packages
 Version            | HEAD
 State              | Unconfirmed
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
+New Attachment     | test.patch
-----------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2006-01-19 07:33) wrote:

Possibly related to Bug: 3191 and Bug: 3224 - but this happens regardless of
what combination of language settings you use.  This is with HEAD from about
10 minutes ago, all config/ files refreshed, framework freshly symlinked
etc...

To reproduce:

1) Create a <configspecial> section in any application's conf.xml file and
create code to handle it in framework/Horde/Horde/Config.php.  This code
should call some arbitrary api function.  I've tested using numerous api
calls from numerous applications.

2) Reconfigure the application using the 'Setup' interface.

3) The setup page works normally, succesfully calling the api function.

4) Generate the new conf.php file.  If the file is succesfully written to
disk, the registry loses *all* applications and all attempts to use Horde
causes a fatal.

5) Either closing the browser or rewriting horde/config/registry.php will
restore functionality.

I've attached a very simple test patch to demonstrate.

I'll try to track this down, but I'm not promising anything ;)