Tickets :: Comment on [#12416] Can't change app-level access perms without disabling or manually clearing cache

* Your Email Address
* Spam protection	Enter the letters below: . .. .. .\ /._. \|__\|\| \|\|__\| >< \| \| \|\|/\\|\| \|/ \_\|_
Comment	>>> No, not using a Redis cluster. Just a very simple Redis install, then >>> started with app defaults. >> >> You are SOL then. > > ?? Huh? > >> Your version of redis is probably too old. There >> is no reason keys() should not work (and I can't reproduce). > > 2.4.10, released March 2012, so not very old. Pear redis is up to date. > >> >> Regardless, as has been said multiple times before - you can't be >> using memcache-like caching mechanisms and expect to clear the cache. >> This is not how those backends were designed. If you have a redis >> backend that doesn't support keys(), you will have to manually purge >> the backend yourself through some other mechanism. > > So, some questions please: > > 1. A google search for memcache horde clear cache came back with > nothing that I could see as relevant. Could you please point me in > the direction of the discussion, or summarise? > > 2. Can you clarify your statement that I can't "expect to clear the > cache". I have no issues at all clearing the cache, as I stated > earlier: "...if I run "redis-cli flushall" after making the > permissions change it works." That runs without error, and clears the > redis cache, as I would expect. The issue is that I am having to do > that manually when I make a change in Horde, rather than Horde doing > it automatically when I make a change that results in stale cache. > > 3. If Horde is configured to use redis, does running > horde-clear-cache call a redis-cli flushall? What redis mechanism is > called to clear the cache? > > 4. Does making a change in Horde that is likely to be impacted by > stale cache (e.g. a permissions change such as that described here) > automatically attempt to clear the cache? In other words, if redis > cache was working correctly (i.e. supports keys()), would a change in > permissions such as I have done in this ticket automatically clear > the cache, thus not requiring me to "manually purge the backend..."? > > If a newer version of redis will result in automatic cache clearing, > then I will happily upgrade it. If not, then my reasoning behind this > ticket still stands - > > "If it is too complex to automate a cache-clear with permissions > changes, perhaps an Apply button that does a cache-clear? Or at the > very least commentary on the permissions page that changes may not > take effect until cache is cleared."
Attachment
Watch this ticket

Saved Queries