> This is because 0.7.x (not sure which version) did not recognize > subclasses as a hobo_model, > and we came to the conclusion that hobo_model inside a subclass solves > it. So I thought it might > be needed for hobo_user_models aswell.
Ah yes - I remember something like this now. Looking at the code, the only thing that might not happen for the subclass is to have the class registered with Hobo. This would cause things like the model being skipped when the Rapid cards and forms are being generated, for example. You could register the model yourself with this call in the subclass: Hobo::Model.register_model self I guess we could do that in the inherited callback in the future. Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
