6.0.0-beta1
7/18/25

[#12264] New memcache abstraction broke caching
Summary New memcache abstraction broke caching
Queue Horde Framework Packages
Queue Version Git master
Type Bug
State Resolved
Priority 1. Low
Owners
Requester torben (at) dannhauer (dot) info
Created 05/18/2013 (4444 days ago)
Due
Updated 05/21/2013 (4441 days ago)
Assigned 05/18/2013 (4444 days ago)
Resolved 05/21/2013 (4441 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
05/21/2013 04:11:31 AM Michael Slusarz Comment #6
State ⇒ Resolved
Reply to this comment
Closing this due to multiple fixes in the last week.

A new bug report can be opened with specific details of any issues 
being encountered.
05/18/2013 07:42:01 PM torben (at) dannhauer (dot) info Comment #5 Reply to this comment
Testing this kind of setup without using the latest git framework 
code is probably not going to be useful, since a bunch of things 
have been changed/fixed in the last few days.
Of course I'll do that based on the newest Git Code...
05/18/2013 07:14:36 PM Michael Slusarz Comment #4 Reply to this comment
Testing this kind of setup without using the latest git framework code 
is probably not going to be useful, since a bunch of things have been 
changed/fixed in the last few days.
05/18/2013 07:10:30 PM torben (at) dannhauer (dot) info Comment #3 Reply to this comment
Can't reproduce.

You haven't mentioned which cache backend you are using.  But I can 
verify that both the Hashtable backend and/or using the memory cache 
config option both work fine with the latest git (there is no 
Memcache cache driver).
I configured the "Distributed Hash Table" to use Memcache.
After that I configured the Horde Cache to use the distributed 
Hashtable Server.
Finally I set CSS Caching to Yes + Driver= Horde Cache.

Hmm, I'll do further test to get more details.

Thanks,
Torben
05/18/2013 07:00:55 PM Michael Slusarz Comment #2
Priority ⇒ 1. Low
State ⇒ Feedback
Reply to this comment
Can't reproduce.

You haven't mentioned which cache backend you are using.  But I can 
verify that both the Hashtable backend and/or using the memory cache 
config option both work fine with the latest git (there is no Memcache 
cache driver).
05/18/2013 08:28:39 AM torben (at) dannhauer (dot) info Comment #1
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ New memcache abstraction broke caching
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
The introduced memcache abstraction via HashTable broke Horde Caching.

After the fixed bug 12263, horde-memcache-stats now shows the stats as 
expected.

Some (horde?) items reside in memcache, but enabling CSS caching in 
Horde breaks CSS rendering, only the plain text liks are shown any more.

I haven't tested Javascript caching yet, since I cannot verify it 
without the CSS caching.

Thanks,
Torben


Saved Queries