[Tickets #11015] Re: Recurring "Undefined class constant 'MAX_SIZE' in /var/www/pear/php/Horde/Memcache.php" messages

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/11015
------------------------------------------------------------------------------
  Ticket             | 11015
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Recurring "Undefined class constant 'MAX_SIZE' in
                     | /var/www/pear/php/Horde/Memcache.php" messages
  Queue              | Horde Base
  Version            | 4.0.13
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2012-02-20 14:43) wrote:

> commit aef5a56a6c2e40bcca7ea4f9a213ca9f689ede70

Actually, this has nothing to do with this issue.  The problem is in  
IMP's hooks file.  Specifically this:

22. IMP_Hooks->prefs_init()
23. Horde_Registry->call()
/var/www/imp/config/hooks.php:29
24. Horde_Registry->callBy
Package() /var/www/pear/php/Horde/Registry.php:979

prefs_init() should not be calling other applications via the  
registry.  This is documented in horde/config/hooks.php.dist.   
However, we (have) a
voided this in IMP because it requires authentication.  The only way I  
can think of off the top of my head to bypass this would be to use  
transparent authentication.  Which, on a practical level, should never  
be used with IMP.

The demo site would not happen to be using transparent auth, is it?