[
https://issues.apache.org/jira/browse/JSPWIKI-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18134728#comment-18134728
]
Arturo Bernal commented on JSPWIKI-579:
---------------------------------------
Part of this report is covered by pull request 561
(https://github.com/apache/jspwiki/pull/561, for JSPWIKI-851), which is not
merged yet. When a save is refused because the hash of the form is missing, the
text typed in the editor is no longer lost: the draft that the editor keeps in
the browser stays, the page SessionExpired now exists in the initial pages and
explains what happened, and opening the editor again offers to restore the
text. In a test on a running instance the restored text came back in the editor
and in the preview. What it does not do is recreate the session or save the
page on its own, as the report proposes: the user still has to open the page
and save again. Leaving the issue open.
> Recreating Sessions
> -------------------
>
> Key: JSPWIKI-579
> URL: https://issues.apache.org/jira/browse/JSPWIKI-579
> Project: JSPWiki
> Issue Type: Improvement
> Affects Versions: 2.8.2
> Reporter: Janne Jalkanen
> Priority: Major
>
> People have displayed annoyance at the way our current session expiry works:
> If you start editing a page, and the editing takes too long, the session may
> expire, and you are served a very cryptic page describing how to log into
> JSPWiki, or told something about Session expiration, which, of course, tells
> really nothing to the user.
> Since this causes a dataloss of your edits, we should really try very hard to
> restart the Session. Obviously, this is not possible if user credentials have
> expired, but if the wiki is open to all, or CookieAuthenticationLoginModule
> is in use, then restarting the Session should be possible.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
