[Tickets #3304] 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
 Updated By         | Michael Rubinsky <mrubinsk at horde.org>
 Summary            | Registry losing applications after api calls from configuration screens
 Queue              | Horde Framework Packages
 Version            | HEAD
 State              | Feedback
 Priority           | 1. Low
 Type               | Bug
 Owners             | Horde Developers, Michael Rubinsky, Michael Slusarz
-----------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2006-01-22 22:06) wrote:

OK. I'm in unknown territory here with the cache code so please bare with
me... Looking at the keys that are being updated in __registrycache this is
what is happening - 

When loading the setup page that contains the api call - the
['applications'] and the ['_confcache'] entries are being updated.  I don't
think the problem is with calling the api function though.  If I load the
setup page, I see the expected values.  If I exit the page without saving
anything everything is fine.

When you generate conf.php, the only key that is being updated is
_confcache...but that also seems to be the behavior when using a setup page
that does not include an api call as well.

I have no idea if this is expected behavior or not...


> I would suggest setting some checkpoints in _shutdownCache() to 
> figure out if/why that code is updating the cache.  Since I can't 
> reproduce the behavior, I can't do any more debugging at this time.