> This is not the strategy I use. Instead, I subclass the User model and make > my additions there (i.e. class Player < User). Removing functionality is a > little tricky; you can remove ActiveRecord validations pretty easily (just > add your own validation callback and remove the errors), but removing other > callbacks might not be so simple.
Doesn't this mean that you have to replace every instance of User in your controllers and models with Player? It seems like a solution where you need to replace the minimum number of files possible would be best (though I'm at a loss for what that solution would be...). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CommunityEngine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/communityengine?hl=en -~----------~----~----~----~------~----~------~--~---
