(05:41:25 PM) emanuele: So, I was thinking...
(05:41:29 PM) emanuele: (and that's bad)
(05:42:25 PM) emanuele: ...in most of the cases there is an error (for example with Tokens) Elk shows a nice "back" button with a js attached that moves the browser back of one page in the history
(05:43:02 PM) emanuele: now, with tokens that's completely useless and even counterproductive
(05:43:13 PM) Norv: Yes
(05:43:20 PM) emanuele: what could we do instead?
(05:43:52 PM) Norv: Nice button 'Re-try', which reloads the page?
(05:44:51 PM) Norv: It'd be the simplest thing
(05:44:52 PM) emanuele: Serving again the same page with the new values ready for a "save" seems a bit tricky (it may lead to situations where you are directed to the local forum from an external page and tricked to click the save and apply the new settings without thinking)
(05:45:04 PM) Norv: Hmm.
(05:45:27 PM) Norv: We have such cases (admin login)
(05:45:43 PM) emanuele: mmm...nope (at least not anymore)
(05:45:59 PM) emanuele: if the POSTed page comes from a different domain is stopped
(05:46:03 PM) Norv: No? I thought it saved after logging in
(05:46:04 PM) emanuele: by checkSession
(05:46:08 PM) Norv: Of course, of course
(05:46:37 PM) Norv: I meant, such cases where you save after admin was required to login, values ready in session
(05:47:16 PM) emanuele: I tried the adminLogin once, but after the issue with checkSession last year I removed the code because I was not entirely sure it was the proper way to go
(05:48:31 PM) Norv: Why don't we load the page, as it is, with values, and add an error box?
(05:48:49 PM) Norv: Instead of this page for error message alone with a 'back' button.
(05:49:11 PM) Norv: (just brainstorming; coffee coming up)
(05:49:14 PM) emanuele: with the current values stored in the database?
(05:49:31 PM) Norv: With the values the user was trying to save
(05:50:50 PM) Norv: I mean, why do we make an error page at all?