X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/665da89c270f98e93b1eaa89e729f3975973ab8f..096619f738a097a3ed42a863c8b5e0c001829c99:/doc/plugins/lockedit/discussion.mdwn

diff --git a/doc/plugins/lockedit/discussion.mdwn b/doc/plugins/lockedit/discussion.mdwn
index b058b2b07..867fc6a51 100644
--- a/doc/plugins/lockedit/discussion.mdwn
+++ b/doc/plugins/lockedit/discussion.mdwn
@@ -1,21 +1,18 @@
-This plugin not only locks pages but ensures too a user is logged in. This seems to me redundant with signedit. I propose :
+This plugin not only locks pages but ensures too a user is logged in. This
+seems to me redundant with signedit. I propose [removing the if block that
+calls needsignin ].
 
-    sub canedit ($$) {
-    	my $page=shift;
-    	my $cgi=shift;
-    	my $session=shift;
-    
-    	my $user=$session->param("name");
-    	return undef if defined $user && IkiWiki::is_admin($user);
-    
-    	if (defined $config{locked_pages} && length $config{locked_pages} &&
-    	    pagespec_match($page, $config{locked_pages},
-    		    user => $session->param("name"),
-    		    ip => $ENV{REMOTE_ADDR},
-    	    )) {
-    		return sprintf(gettext("%s is locked and cannot be edited"),
-    			htmllink("", "", $page, noimageinline => 1));
-    	}
-    
-    	return undef;
-    }
+> That was added because the most typical reason for being unable to edit a
+> 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]]