Bug 38480 - [PATCH] The error handler page should contain a link back to the authoring gui.
Summary: [PATCH] The error handler page should contain a link back to the authoring gui.
Status: NEW
Alias: None
Product: Lenya
Classification: Unclassified
Component: Miscellaneous (show other bugs)
Version: Trunk
Hardware: All All
: P1 enhancement
Target Milestone: 2.0.1
Assignee: Lenya Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-01 18:46 UTC by J
Modified: 2007-11-02 07:10 UTC (History)
0 users



Attachments
adds a link to the error page to provide a sane way back to the authoring interface. (1.75 KB, patch)
2006-02-01 19:07 UTC, J
Details | Diff
this is the correct version, the other had a wrong link. (1.75 KB, patch)
2006-02-01 19:12 UTC, J
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description J 2006-02-01 18:46:27 UTC
right now, the "Apache Lenya: An error occured" page offers no way for users to
get back to a place where they can continue their work.

so they are bound to use the browser's "back" key, which can lead to lost data
when they use an edit form that no longer has a lock on the file (i.e. they will
not be able to save).

i suggest to include a link to {pubname}/{area}/index with a message that they
should probably save this page and show it to the site admin.
Comment 1 J 2006-02-01 19:07:09 UTC
Created attachment 17566 [details]
adds a link to the error page to provide a sane way back to the authoring interface.
Comment 2 J 2006-02-01 19:12:45 UTC
Created attachment 17567 [details]
this is the correct version, the other had a wrong link.
Comment 3 J 2006-02-14 19:15:25 UTC
i just realized that the error handler page is also displayed in the live, so
the message text should probably more generic and not mention editing.
Comment 4 Andreas Hartmann 2007-04-23 02:35:27 UTC
Any news here?
Comment 5 J 2007-04-23 05:44:07 UTC
not really. this is non-trivial, for a number of reasons:

* when a problem happens during editing, should we roll back the usecase and
re-display the editor? the user might run into the very same problem next time
s/he saves, but might also be able to work around the problem and avoid data loss.
* it's area-dependent
* there are several error handlers

i haven't found time to look into it further, but we should....
Comment 6 J 2007-11-01 13:57:55 UTC
andreas, now that you've been digging into the error handling some more, is
there a quick way of dealing with it? if only a link back to <pub>/<area> ?
and maybe we could mention a workaround to avoid data loss when an editor
crashes: use the back button, try to salvage as much data as possible by copying
it into the clipboard...
Comment 7 Andreas Hartmann 2007-11-02 02:35:44 UTC
(In reply to comment #6)
> andreas, now that you've been digging into the error handling some more, is
> there a quick way of dealing with it? if only a link back to <pub>/<area> ?

The link should be no problem.

> and maybe we could mention a workaround to avoid data loss when an editor
> crashes: use the back button, try to salvage as much data as possible by copying
> it into the clipboard...

I guess this would make sense. The question is if we should include this message
on each error page, I see no easy way to find out if it was an editor which
caused the error (except maybe for checking the lenya.usecase request parameter).
Comment 8 Richard Frovarp 2007-11-02 07:10:26 UTC
(In reply to comment #6)
> andreas, now that you've been digging into the error handling some more, is
> there a quick way of dealing with it? if only a link back to <pub>/<area> ?
> and maybe we could mention a workaround to avoid data loss when an editor
> crashes: use the back button, try to salvage as much data as possible by copying
> it into the clipboard...

The back trick should only work in a non-SSL environment.