My preferred version of doing this (when a project requires it) is this: 1. Use fusebox (That's Extended FB2 Taz edition)
2. If the session expires, copy the requested Fuseaction into a variable called "Attributes.RequestedFuseaction" 3. Copy all Attributes scope variables (form and url) into the login form as hidden fields, including "Attributes.RequestedFuseaction", but obviously not "Attributes.Fuseaction" 4. If a file has been submitted, upload it to a temporary folder and set a file flag in the form, which includes a reference to the filename. 5. The form is then submitted with the login info. If the login fails, a check for the existence of "Attributes.RequestedFuseaction" so that you don't overwrite it with the login fuseaction. All the form/url data re-populates the form. 6. When the login is complete, instead of going to a default welcome page, grab the Attributes.RequestedFuseaction and pass the information to the required circuit. The only major problem is file uploads. Your file ops must be able to check for the existence of either a file upload field, or a temporary file flag and filename. Yadda yadda yadda Taz -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
