fix container caching bug

Ticket

+commit
 

 

I think a rails upgrade switched us from using files as cache to using memory- meaning each rails process has it's own version of the cache.  that would expect to be wonky like this.  I've set all the wagns to use file_cache explicitly- lets see if that clears up the weirdness

 

 

the developer menu bug you were seeing, JohnAbbe_ seems to be a caching thing too.
right now I'm signed in on wagn.org, but not on www.wagn.org
*sidebar is getting cached by whichever views it first.
signed in should see it, not signed in shouldn't.

--Ethan, from IRC