Can't get to the example at the moment, but it sounds like one relevant question for Wagn installers here is: How do i turn on Ruby (or Script) cards? --John
It is related, I would think. Not sure if there is maybe an underlying bug too.
--Gerry Gleason.....Sat Sep 26 11:33:11 -0700 2009
I found another aspect of this. If I want to make a regular card into a cardtype, this problem is triggered too. I was adding a Forum thing at FlowPlace, and I accidentally forgot to put the type "Cardtype" when I created the "Topic" card. In order to clear this, I had to first delete the card "Topic", then go into mysql and there was still a key for that in cards. I delete that record, restart the server, and then was able to create Topic correctly.
--Gerry Gleason.....Mon Oct 26 03:09:40 -0700 2009
different issue: add extensions when cardtype is changed.
However, might be linked via solution: codenames.
--Ethan McCutchen.....Mon Oct 26 07:56:46 -0700 2009
I see your point, but shouldn't it have worked to delete the Topic card and re-add it? I mean it should add the extension when it is a "new" card, which it was when I tried again. I had to delete it and there was still a topic key in the cards table. I deleted that and then it was ok when I redid it.
--Gerry Gleason.....Mon Oct 26 08:58:53 -0700 2009
deleting doesn't actually remove cards from the database, it just puts them in the trash. when you "create" them again, you're actually updating that trashed record, not creating a new record. But currently creating a new record is the only process that actually handles the extension.
--Ethan McCutchen.....Mon Oct 26 09:45:22 -0700 2009
So that's what "trash" means. I couldn't figure that out at first. That makes not adding the extension an even worse bug. I'm sure it has bit me a number of times before, but I didn't quite realize it yet.
--Gerry Gleason.....Mon Oct 26 10:08:30 -0700 2009
closing. underlying issues not fixed yet, but I think they're addressed in tickets.
--Ethan McCutchen.....Mon Dec 07 11:56:35 -0800 2009