fixed bug: entries are updated instead of stored multiple times
fixed an issue with the database not updating fast enough and propagating these changes to memcache when queried soon after the addition of a new user at signup.
hacked solution to ensure that the right content is displayed after an edit - problems with lag in the database and creating new instances instead of updating them cause incorrect behaviour. should fix this properly later.
lag problems didn't completely disappear so went back to basics and created handlers2. this accesses the DB every time but a short sleep after saving new instances solves the problems with lag. TODO: implement memcache correctly without lag issues.