In designing a new Turbine app I've found it necessary to override the default user login action from Turbine to add additional functionality. When doing so, I followed the steps in the default LoginUser action nearly to the letter to ensure I wasn't doing anything untoward.
Apparently, however, I did. When setting my new action as the default login.action in TR.props I began having trouble with the one session tool used by this application. The tool itself is instantiated on login (i.e. a log message in the init() method gets printed) but it doesn't seem to be in the Velocity context for the very first page to which the user is redirected after logging in. After the first followed link, the session tool functions just fine but that initial redirected page never sees the benefit of the session tool's existance. I thought I'd heard something like this on the list previously but searching the archives has turned up nothing. Does anyone have ideas on what I could be doing wrong in a revamped LoginUser action to cause my session tools to be absent from the velocity context only on the first template viewed after login? Thanks, -j ------------------------------------------------- James Diggans Bioinformatics Programmer Gene Logic, Inc. Phone: 301.987.1756 FAX: 301.987.1701
