[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         | Michael Slusarz <slusarz at horde.org>
  Summary            | Search "entire message" member function fetch() on a
                     | non-object
  Queue              | IMP
-Version            | 6.2.0beta2
+Version            | Git master
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-08-21 10:44) 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.

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?