Do not use natlogon on dakar, use the TemplateLogin LoginManager
will not break most probably. At least I hope so.
natlogon used to work on dakar too but since the recent changes
in the Client.pm code (see Item2158
) this somehow broke. Good guess: session does not
get flushed out anymore. Internal APIs used by natlogon
changed in twiki4. (yeah, it shouldn't rely on internal APIs, I know, but hey
Actually, the changes were to do with make sure the session is
flushed. it now flushes much more aggressively....
Can you be more specific as to what "broken" means in this case?
I agree that natlogon should be deleted / consolidated into templatelogin - this is feature (bone) not a (skin).
Why did I know you will say that again? Damn, how do I "templatelogin" on
cairo and beijing then? MC
, you just volunteered to backport
to cairo and beijing. Where's your code?
Just for your information: using any login scheme the LoginManager
provides is just fine with NatSkin
TWiki::Client::userLoggedIn() was flushing the session object to disk previously as soon as the user was authenticated. Now it flushes only if the
user is not
authenticated. Flushing an authenticated session object is delayed til TWiki::Client::finish() is called now.
Reasigned to engine. You are not able to login for the same reason you have not been able to log out as reported in Item1820