Where will the extra information live? In a model, or templates? Is it static or dynamic content, managed or unmanaged?
School information can be attached to the user at login (in session, for example), and/or stored permanently. It's easy enough to extract the school information if login is via email address, or pull it from the database if there are separate user names. On Jan 19, 1:26 pm, DanC <[email protected]> wrote: > I would like to try and do this on email suffix recognition rather > than asking the user to specify their university at login if there is > an elegant way of doing so. -- 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.
