I had trouble reproducing this too. I first saw it several months ago and couldn't reproduce it locally. Then I encountered it again a few days ago and I was able to reproduce it locally in an environment where `neighborhood.cache.duration` was set.
Just now I was able to to reproduce in our production environment on a high-traffic neighborhood. But saving did work ok in a neighborhood that is essentially never used (and thus likely not cached in some/all the procs). If needed perhaps we could just add some more logging to get more info about what's happening. That is, if we can think of good logging to add :) --- ** [tickets:#7890] Neighborhood cache preventing saving admin changes** **Status:** in-progress **Milestone:** unreleased **Labels:** 42cc **Created:** Thu Jun 04, 2015 09:04 PM UTC by Dave Brondsema **Last Updated:** Tue Jun 09, 2015 04:11 PM UTC **Owner:** Igor Bondarenko If you have `neighborhood.cache.duration` set in the `.ini` file then when you go to `/p/_admin/overview` (or any neighborhood) your changes will not persist. They may appear to show but if you refresh the page they won't be there. We don't need to worry about clearing/expiring the cache (especially since multi-process multi-server deployments will all have their own memory caches) but we should actually save the changes so that when the cache naturally expires the new values are used. --- Sent from forge-allura.apache.org because [email protected] is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
