I can't reproduce this. Maybe there are some other deployment related options which affect this? Can you confirm it still persists?
--- ** [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:** Mon Jun 08, 2015 08:52 AM 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.
