6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
11/28/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#11015] Recurring "Undefined class constant 'MAX_SIZE' in /var/www/pear/php/Horde/Memcache.php" messages
*
Your Email Address
*
Spam protection
Enter the letters below:
.__ \ /.__ .__ . . [__) >< [ __| \|_/ | / \[_./|__/| \
Comment
>>> 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. > >
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers