summaryrefslogtreecommitdiff
path: root/doc/plugins/lockedit
diff options
context:
space:
mode:
authorJogo <Jogo@web>2009-10-12 16:44:12 -0400
committerJoey Hess <joey@kitenet.net>2009-10-12 16:44:12 -0400
commit7272938a116b2c87f8c34057034b5f4e9244cdf8 (patch)
tree37e2ff708803cc971f8d256c64dc70c00ac64bcb /doc/plugins/lockedit
parent6993d1f905c35bbad415d3f60cde924da32e80a4 (diff)
Diffstat (limited to 'doc/plugins/lockedit')
-rw-r--r--doc/plugins/lockedit/discussion.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/plugins/lockedit/discussion.mdwn b/doc/plugins/lockedit/discussion.mdwn
index 8a08edaad..867fc6a51 100644
--- a/doc/plugins/lockedit/discussion.mdwn
+++ b/doc/plugins/lockedit/discussion.mdwn
@@ -6,3 +6,13 @@ calls needsignin ].
> page is that you are not logged in. And without the jump to logging the
> user in, there is no way for the user to log in, without navigating away
> from the page they were trying to edit. --[[Joey]]
+
+>> Ok, but the problem is that when you don't want any signin form you end up
+>> with a lone login button. That might happend if you lock pages only on IP
+>> adresses, if you use another cookie from another webapp...
+
+>> That happends to me and I had to reimplement lockedit in my private auth
+>> plugin.
+
+>> Perhaps you could return undef on that case and let another plugin do the
+>> needsignin call ? -- [[Jogo]]