aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/No___34__sid__34___in_forms_resulting_in_Error:_Your_login_session_has_expire...
diff options
context:
space:
mode:
authorJoey Hess <joey@kodama.kitenet.net>2008-04-28 13:38:53 -0400
committerJoey Hess <joey@kodama.kitenet.net>2008-04-28 13:38:53 -0400
commitaa4f9fe23208bd95d248f0a5d7a3ee5fdefedb45 (patch)
tree7f125eef91a6568f6247388401782e6de5e82c82 /doc/bugs/No___34__sid__34___in_forms_resulting_in_Error:_Your_login_session_has_expired..mdwn
parent74d98c69b1a865aa4b136a01f21ccf23a66a2784 (diff)
downloadikiwiki-aa4f9fe23208bd95d248f0a5d7a3ee5fdefedb45.tar
ikiwiki-aa4f9fe23208bd95d248f0a5d7a3ee5fdefedb45.tar.gz
response
Diffstat (limited to 'doc/bugs/No___34__sid__34___in_forms_resulting_in_Error:_Your_login_session_has_expired..mdwn')
-rw-r--r--doc/bugs/No___34__sid__34___in_forms_resulting_in_Error:_Your_login_session_has_expired..mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/No___34__sid__34___in_forms_resulting_in_Error:_Your_login_session_has_expired..mdwn b/doc/bugs/No___34__sid__34___in_forms_resulting_in_Error:_Your_login_session_has_expired..mdwn
index fb0885e90..bd0d78b9b 100644
--- a/doc/bugs/No___34__sid__34___in_forms_resulting_in_Error:_Your_login_session_has_expired..mdwn
+++ b/doc/bugs/No___34__sid__34___in_forms_resulting_in_Error:_Your_login_session_has_expired..mdwn
@@ -11,3 +11,13 @@ View source of editing page or preview+edit page shows no "sid" input value. (I
> Further info. In the "prefs" dialog, it does have hidden "sid" defined. Viewing HTML source also shows this is in the fb_hidden class and Generated by CGI::FormBuilder v3.0501. I tried multiple times and never see "sid" in the HTML source of editing a page. --[[JeremyReed]]
>> Found problem: Needed to update my editpage.tmpl to add TMPL_VAR FIELD-SID. This bug can be closed once that is documented -- and that documentation is obvious to find.
+
+>>> Whenever you choose to locally copy an ikiwiki template and modify it,
+>>> it's really up to you to keep it up-to-date. I did consider adding a
+>>> new item about this rather than just mentioning it in the changelog,
+>>> since I knew it would break locally modified templates -- but I've
+>>> never documented template changes in the new file before, and most of
+>>> them do lead to breakage of one kind or another if a locally modified
+>>> template is not kept up-to-date. I don't think that bloating the news
+>>> file with mentions of every single change to every template file would
+>>> be a win. --[[Joey]]