> I'm having problems getting started with Turbine. I'm attempting to > change the default screen that users see when first accessing the > web app by changing screen.homepage in tr.props to the name of the > screen template (Index.vm) I want loaded. However, it's still loading > the default Login. Index.vm is located in /templates/app/screens. > > If I set Index.vm to be the default template for an invalid login > attempt, it loads. (Proving it can be found). > > I've also attempted to change the default login action to MyLoginUser > located at /WEB-INF/classes/ca/bcit/cstwebproject/modules/actions and > Turbine is still loading the default LoginUser class. > > Am I just missing something obvious here? This is similar to the battle I have been fighting over the last couple of days. I suggest you look at the code in org.apache.newapp.modules.screens.SecureScreen.isAuthorised() and org.apache.turbine.modules.actions.LoginUser.doPerform() These interact with the properties defined in TR.properties to provide the behaviour you are interested in. I think there may be a bug in LoginUser but I am not completely sure - check one of my messages earlier today with the subject "Frustrating Problem" As you are using a different initial screen your problem may not be exactly the same as mine, but I think this information may be of some help to you. Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
