Thanks all for getting back to me on this with your help and suggestions and sorry for the long reply.
I believe the most logical approach would go along the the lines of Tyler's suggestion of handling the logic in the view as suggested below. Thanks all - and I would say this is resolved. Tyler Crocker wrote: > I usually use the same partial for creating and editing, what you said > is > about right, I usually just do; > *fields that are used for both creating and updating* > > % if @user.new_record? %> > %= submit_tag 'Create' %> > % else %> > %= submit_tag 'Update' %> > % end %> > > > and then throw in whatever else you need to like back buttons or > whatever. > For updating the password, you can either just have the two password > fields, > which will update the passwords if a new one is set, or you can do > another > if @user.new_record? statement in the form and have it show the fields > for > creating a password or updating a password. > > Hope this helps. > > > On Tue, Dec 30, 2008 at 5:53 PM, Clem Rock > <[email protected] -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
