forms and cardtypes
Any time you add a form to a cardtype, its cardtype should be the same as the cardtype's. (in fact, joining a cardtype to a card should give you a card of that type even if there isn't a form).
Related support tickets:Relevant user stories:add oneTags:
Really? The first part would create serious problems - if the cardtype has a hard form, the form card will become uneditable. --John Abbe
Good point. In fact, it seems like type forms should always be Basic and the cardtype should be uneditable. I'm on it.
--Ethan McCutchen.....Sun May 25 22:17:14 +0000 2008
actually now, I'm thinking perhaps the rform should always have that cardtype (but not the tform).
Anyway tforms are now uneditable. Can you test that part and tidy up this ticket (or tickets?) so the outstanding questions are captured and that the changes are communicated.
--Ethan McCutchen.....Thu May 29 19:04:39 +0000 2008
one other question. Before we had it so that you could not edit a form's name. Why? Would things go nuts if you changed a hard form's name or something? I think I may have commented that out. do we want it back?
--Ethan McCutchen.....Thu May 29 19:05:37 +0000 2008
Notes