1 At the moment, you go through the login shuffle and then are told that cookies are needed, so you lose all your data and login again. It would be much slicker to note by the edit link, or at least on the login page, that cookies are required.
3 > Hmm, it seems to me to be fairly obvious, since the vast majority of
4 > websites that have a login require cookies. Such warnings used to be
5 > common, but few sites bother with them anymore. --[[Joey]]
7 >> Very few websites break without cookies. Even fewer lose data.
8 >> Can ikiwiki avoid being below average by default? --[MJR](http://mjr.towers.org.uk)
10 >>> Can we avoid engaging in hyperbole? (Hint: Your browser probably has a
11 >>> back button. Hint 2: A username/password does not count as "lost data".
12 >>> Hint 3: Now we're arguing, which is pointless.) --[[Joey]]
14 Even better would be to only display the cookie note as a warning if the login page doesn't receive a session cookie.
16 > I considered doing this before, but it would require running the cgi once
17 > to attempt to set the cookie and then redirecting to the cgi a second
18 > time to check if it took, which is both complicated and probably would
21 >> Might this be possible client-side with javascript? A quick google suggests it is possible:
22 >> <http://www.javascriptkit.com/javatutors/cookiedetect.shtml>. MJR, want to try adding
25 Best of all would be to use URL-based or hidden-field-based session tokens if cookies are not permitted.
27 > This is not very doable since most of the pages the user browses are
28 > static pages in a static location.
30 >> The pages that lose data without cookies (the edit pages, primarily)
31 >> don't look static. Are they really? --[MJR](http://mjr.towers.org.uk)
33 >>> As soon as you post an edit page, you are back to a static website.
projects / ikiwiki / blob