> So are you saying that you changed the code in the POST action and > this changed the way the params were posted *to* that action (as seen > in the log file)? That seems rather odd as when the data are posted > it has not yet got to your modified action.
Yes! That is why this is so odd... because it *is* odd ;) It's like the params hash changes after you re-submit. The only correction I can surmise is to use a concrete GET/POST action for each user type :( This works though. Not what I want... and it obviously a smell... but it works. I wish it were easier to do the base class thing so it worked for users of all sub classes without this much headache. In Java, you can explicitly say, "I want this to be *user*" in an annotation - and that's it. It will use User for everything if you tell it to. -- 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.
