aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/Anon_edit_caused_lock_out_on_entire_site_.mdwn
diff options
context:
space:
mode:
authorsmcv <smcv@web>2017-05-14 08:31:49 -0400
committeradmin <admin@branchable.com>2017-05-14 08:31:49 -0400
commit365a930c2c39d1f727aa620155c179c004acdcc1 (patch)
treeb2bebdaa90c3a8546260e6190f5f3b47f26d246d /doc/bugs/Anon_edit_caused_lock_out_on_entire_site_.mdwn
parentf6fc4543fb7549c3524373448ef4138031049e4a (diff)
downloadikiwiki-365a930c2c39d1f727aa620155c179c004acdcc1.tar
ikiwiki-365a930c2c39d1f727aa620155c179c004acdcc1.tar.gz
complete last paragraph
Diffstat (limited to 'doc/bugs/Anon_edit_caused_lock_out_on_entire_site_.mdwn')
-rw-r--r--doc/bugs/Anon_edit_caused_lock_out_on_entire_site_.mdwn13
1 files changed, 11 insertions, 2 deletions
diff --git a/doc/bugs/Anon_edit_caused_lock_out_on_entire_site_.mdwn b/doc/bugs/Anon_edit_caused_lock_out_on_entire_site_.mdwn
index 3cbcf6032..02d43e827 100644
--- a/doc/bugs/Anon_edit_caused_lock_out_on_entire_site_.mdwn
+++ b/doc/bugs/Anon_edit_caused_lock_out_on_entire_site_.mdwn
@@ -107,5 +107,14 @@ Is there a session file or something to logout this phantom user?
>> I think I've sent right away when you asked, anyway I still have the tarball hanging around. The last *iikb* domains will expire next month though, the wiki will only be accessible by mirror <https://notabug.org/iikb/dev.iikb.org>.
->>> I see you have a lot of uncommitted changes. This is probably because
->>> whatever is causing the anonymous accesses to succeed is
+>>> I see from the tarball that you have a lot of uncommitted changes. This is
+>>> probably because whatever is causing the anonymous accesses to succeed is
+>>> breaking other code paths by giving them an empty username: in particular
+>>> it seems reasonably likely that the `git` plugin will refuse to commit
+>>> changes in that situation.
+>>>
+>>> I would expect that you should be getting error messages on the ikiwiki
+>>> CGI script's `stderr` in this situation. In Apache they would normally
+>>> end up in `error.log`; I don't know how nginx does logging, but it is
+>>> probably something similar. Please check that log for relevant-looking
+>>> error messages. --[[smcv]]