• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.
As soon as Item3067 is somewhat done we should get rid of using ApacheLogin (which "just works") here at develop.twiki.org for a while and give TemplateLogin some attention.

It can still be made better and there are probably also some bugs to be found still. It is very important functionality imho (for instance it gives the user the ability to actually sign out ..) - it is not getting enough attention as is.

TemplateLogon will still have some quirks in i.e. I18N surroundings which we cannot test here, but we will catch the basic issues faster.

-- SP

We switched to the ApacheLogin, because some developers (for example I) could not log in consistently into the Bugs web, and we never figured out why. It appeared to be related to some cookies being written, but we never tracked it down and gave up in frustration. Let's make sure this does not recur... -- TW

As I remember it, the extra cookie was eliminated, but if not this just demonstrates the point, I believe.

If we would like to offer TemplateLogon as a non-beta, working feature of TWiki we should test it some more.

-- SP

Bugs web is an increasingly critical resource, and while I like having it running the shipped code, I'm nervous of alienating certain developers (especially those called Thomas) by making it unuseable by them.

How about identifying a useful purpose for Kenneth's test install, and using it instead? The problem is persuading people to visit it.....

CC

Another approach would be to assign two installations/dns names to the /data and /pub set used by dto and have the default one use TemplateLogin - and have the other handy with ApacheLogin in times where couriosities exist / for users experiencing problems.

A lot of code/mechanisms have changed around this login method, and some of us is using ApacheLogin because TemplateLogin has given us hazzles previously. My feeling is it is not being given the attention it should - but I might be wrong.

The cookie problem was eliminated last time, but if it's just not the right way /time to do it, I can live with that.

Discarding pending a better way/timing.

-- SP

I am ok with giving it a try. Just please if problems show up, let's switch back again to apache login.

If SP thinks the problem was eliminated, why not try it out... Just give me a way of alerting you if the problem recurs. -- TW

Any other opinions?

-- SP

The problem is finding a time to do it, and getting commitment to fix any bugs that might arise.

CC

Done by Sven (I think)

CC

Cleaned "WaitingFor" field.

-- TWiki:Main.GilmarSantosJr - 10 Aug 2008

ItemTemplate
Summary Switch to using TemplateLogin at develop.twiki.org
ReportedBy TWiki:Main.SteffenPoulsen
Codebase

SVN Range TWiki-4.1, Fri, 03 Nov 2006, build 11888
AppliesTo Engine
Component BugDatabase
Priority Normal
CurrentState Closed
WaitingFor

Checkins

TargetRelease n/a
ReleasedIn

Edit | Attach | Watch | Print version | History: r11 < r10 < r9 < r8 < r7 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r11 - 2008-08-10 - GilmarSantosJr
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback