6.0.0-beta6
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
4/10/26
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#13264] Search "entire message" member function fetch() on a non-object
*
Your Email Address
*
Spam protection
Enter the letters below:
. .. . .\ /. . \ /| |_/ >< |_/ \/ |___| \/ \| \
Comment
>> I'm afraid that your changes didn't really fix this issue. From my >> debug-logging, I see that the 'cache' parameter always is of the >> Horde_Cache type, regardless of the cache driver/backend. > > This is incorrect. testReadWrite() should NOT be used in a production > environment first of all (brutal performance hit). And regardless - > this exists to catch permission issues when running Horde scripts > from the command line. > > More important: this just masks the configuration problem of "why is > your cache backend not working in the first place"? Any cache > backend other than Null should obviously be read/write to Horde. Or > else what's the point of defining a cache driver if you can't use it?
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