As a note, this instance was installed using Cloudstore and they updated it just a week ago to the newer version. Cloudstore also told me that they had seperately reported to Wagn that the "undefined method 'type_id' for nil:Nilclass" error has been occurring implying this is impacting other users.
--Tom McFarland.....2012-10-07 22:05:52 +0000
I took a quick look and it's probably over my head. My guess is this won't help, but one way you can sometimes learn more about a card that gives an error is to go directly to edit mode, in this case by going to http://tomsplayground.945.cldstr.com/wagn/card/edit/Cardtype instead of http://tomsplayground.945.cldstr.com/wagn/Cardtype
(I don't have an account, so I can't sign in to see the result.)
--John Abbe.....2012-10-07 23:00:29 +0000
Unfortunately, the Sign In card gives a rendering error so I'm no longer able to sign in as administrator.
Think it would be possible to have Cloudstore do a repair install or over install to reset all the core cards without eliminating the cards I've created? (Not whether they are willing to do it, but whether this is feasible and might fix it.)
--Tom McFarland.....2012-10-08 22:05:52 +0000
It looks to me like *all+*default got altered or deleted on your wagn. That probably explains most of the problems you're seeing. I just wrote some new code that should fix it so that this card is no longer needed for things to run smoothly; let's see if this problem persists.
--Ethan McCutchen.....2012-10-08 22:40:33 +0000
Hi Ethan,
Thank you! It's working great! I appreciate your help.
Tom
--Tom McFarland.....2012-10-09 21:31:39 +0000
you're welcome!
Do you have any idea how that card got changed in the first place?
--Ethan McCutchen.....2012-10-09 21:37:22 +0000
Oh yeah. Not completely certain what I did exactly, but pretty sure this was a i.10t error. I deleted it manually as administrator.
I thought I was deleting a customized default card which would allow the set to return to using the global default. Evidently, my set was already using the *all default on the set.
--Tom McFarland.....2012-10-09 22:35:00 +0000
you know what, I may have found a bug that caused this. kinda looks like it was my fault on many levels :(
--Ethan McCutchen.....2012-10-09 22:56:55 +0000
(I've posted a patch. it will be deployed soon)
--Ethan McCutchen.....2012-10-09 22:57:21 +0000