- **status**: in-progress --> review - **Comment**: Closed #801. `ib/7890`
A simplest fix actually worked. I've just added a line to get neighborhood from mongo to the beginning of "update" controller. Notes for QA: - get [the script](https://forge-allura.apache.org/p/allura/pastebin/557ed1556d19cd6c8b87121c) - run it as `python ./scripts/get_neighborhood.py http://<your_host>/p/wiki/Home>` - set `neighborhood.cache.duration` to something small (5 - 10 seconds) On master: - go to `/p/_admin/overview`, change something and submit the form - make sure you see new values - wait for cache to expire and reload the page, make sure you see old values Checkout the branch and repeat the above. After form submission you will not see new values, but after cache expires you should see them. --- ** [tickets:#7890] Neighborhood cache preventing saving admin changes** **Status:** review **Milestone:** unreleased **Labels:** 42cc **Created:** Thu Jun 04, 2015 09:04 PM UTC by Dave Brondsema **Last Updated:** Mon Jun 15, 2015 01:38 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.
