handle direct creation of new cardtype settings
When you create foo+*type+*content directly without first making foo and making it a cardtype, the database is left
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?).
Related support tickets:Relevant user stories:add oneTags:
merging in better error message for forms of nonexistent types
URLs such as http://www.wagn.org/wagn/seth+*type return a virtual card, and the only indication that there's an error is where it tries to list cards of type seth. How about, in a class instruction div: Oops! There's no card type called "seth".
I'm ok with just the error message. Not wild about automatically making a new cardtype.
--Ethan McCutchen.....Thu Dec 01 14:19:40 -0800 2011
Notes