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

bugs at horde.org bugs at horde.org
Mon Feb 20 23:33:49 UTC 2012


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

Ticket URL: http://bugs.horde.org/ticket/11015
------------------------------------------------------------------------------
  Ticket             | 11015
  Updated By         | Gunnar Wrobel <wrobel 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             |
------------------------------------------------------------------------------


Gunnar Wrobel <wrobel at horde.org> (2012-02-20 23:33) 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?

No. The backend is a Kolab server but the Horde frontend is configured  
to use SQL and uses no Kolab features. And auth runs against the IMAP  
server provided by the Kolab server (cyrus).

If it helps I can either

a) provide you with a clean instance with the same setup as the demo server
b) provide you with access to the demo server itself.







More information about the bugs mailing list