[Tickets #13264] Re: Search "entire message" member function fetch() on a non-object

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/13264
------------------------------------------------------------------------------
  Ticket             | 13264
  Updated By         | jasper.olbrich at students.uni-marburg.de
  Summary            | Search "entire message" member function fetch() on a
                     | non-object
  Queue              | IMP
  Version            | Git master
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


jasper.olbrich at students.uni-marburg.de (2014-08-21 16:54) wrote:

>> 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.

I almost guessed that testRW() was suboptimal, but can you please  
check/verify that param['cache'] is always Horde_Cache and the  
branching in the constructor has to depend on its _storage?

> More important: this just masks the configuration problem of "why is  
> your cache backend not working in the first place"?
Not working or not configured. Perhaps it would make sense to document  
the consequences of using NOT RECOMMENDED" settings?