Hi, Your task is cannot be that complicated, but for first reading it seemed, and a bit long.
Try to draw it first! First you have to find out: the user experience! It will make clear what datas you need, so what models, which kind of controllers you have to write with different actions. And from this writing a before filter will be easier. You haven't wrote how you solved the user authentication - from scratch? In FireFox there is an excellent Add-on, called Pencil, with this you can make a sketch easily! Now I cannot spend more time with this, but write me in private more detailed, if you would like to, and in these days I will try to help. good luck gezope On okt. 7, 03:53, radhames brito <[email protected]> wrote: > please help!! T_T On okt. 7, 18:01, radhames brito <[email protected]> wrote: > > Remember a controller does not need to map to a model. > > Yes i know, thanks. > > > Again that is not necessarily a problem, though it is all a matter of > > degree of course. > > If you really think that here you have different types of users rather > > than users with different roles you could look at STI as an > > alternative. > > Well i know is not a problem, but i wanted to know if there is a better way > to do all this. > STI creates a problem when authenticating user and creating permissions, i > would need an ability and a login per user type. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
