Scott, Turns out I missed something. It is all now working just as I need it to. Sorry for the useless email.
Lori -----Original Message----- From: Funk, Lori K. Sent: Wednesday, October 10, 2001 2:25 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Extending TurbineUser - a catch Scott, I found, and have used, your document on how to extend TurbineUser. It's a great document that helped alot! I do, however, still have a problem. I'm new to Turbine so please forgive me if this is a stupid question. My need was to add several additional fields to the user (e.g. title, middle name, suffix, phone, etc.). I am generating the sample app that ships with the TDK but trying to incorporate the extended user into it. After following the instructions in your how-to document I also modified the FluxUserForm.vm and FluxUserList.vm templates to include my additional fields. If I manually build a user into the database including my new fields, I can see, displayed in the user list (or deletion confirmation), all the user fields including my additional fields. If I create a new user through the user interface, however, although I'm prompted for the new, addtional, fields they are not saved to the database. Is this the problem you describe as the 'catch' in your email? Can you please tell me how (from what class) the set methods defined in the TurbineUserAdapter class created according to your instructions are actually called? Thanks Lori --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
