handle adding foo-plus-*type-plus-*content
handle adding foo-plus-*type-plus-*content+issue
This gets an application error, and creates "foo" but leaves the database messed up.
At the very least, leave the database in a useable state. It would be nice if the card could be created even if Organization didn't exist before (with Organization automatically being added as a cardtype?).
http://democracyinnovations.wagn.org/wagn/Organization - looks okay, but try editing it and you get:
Can't find it!
Couldn't find Card::Base with ID=418
404 Not Found
When I tried to add Organization+*type+*content Hoptoad said: RuntimeError: No class name for cardtype name Organization
fixed by clearing cache. we should make a ticket, but this case is pretty edgy, imho
agree on edginess. handle direct creation of new cardtype settings
--John Abbe.....Sun Jan 16 23:36:23 -0800 2011
this is going to be useful in the meantime for being able to reproduce (and fix?) cache wackiness.
--Ethan McCutchen.....Mon Jan 17 10:58:11 -0800 2011
closing, because it's been ticketed.
--Ethan McCutchen.....Wed Jan 19 14:48:35 -0800 2011
(don't always want to do this when the submitter is a non-insider seeking support, but when it's just us chickens...)
--Ethan McCutchen.....Wed Jan 19 14:49:19 -0800 2011
Is there a ticket for fixing cache wackiness, and if not what would it be called?
--John Abbe.....Wed Jan 19 15:08:26 -0800 2011
fix cache wackiness? would be great to start gathering examples. thanks for remembering this.
--Ethan McCutchen.....Wed Jan 19 17:25:56 -0800 2011