Ticket #590 (new defect)

Opened 14 years ago

Last modified 13 years ago

standard error message should not break navigation

Reported by: bdelbosc Owned by: trac
Priority: P2 Milestone: CPS 3.5.7
Component: CPSDefault Version: unspecified
Severity: normal Keywords:
Cc:

Description (last modified by fguillaume) (diff)

standard error message should not break navigation

the 'not found' or 'site error' page is displayed in an anonymous context, which is confusing for the user as he may think that it is logged out.

the error message page should be redirect to be displayed in the user context, if it is not possible we should display the message in a blank page with 2 links: back and advanced search.

Change History

comment:1 Changed 14 years ago by anonymous

  • Summary changed from standard error message should not break navigation to standard error message ashould not break navigation

comment:2 Changed 14 years ago by fguillaume

  • Description modified (diff)
  • Summary changed from standard error message ashould not break navigation to standard error message should not break navigation

comment:3 Changed 14 years ago by fguillaume

  • Milestone changed from unspecified to CPS 3.4.0

comment:4 Changed 14 years ago by lregebro

Just some notes: Not Found errors happen during traversal, before there is a security context. Redirecting to place that exists, so that you can have a security context, must preserve error information, and there must be an way way to get back to where you were before. Pressing the "back" button in that position would, unless I'm mistaken, try to get to the page where you got the error, which again redirects you, and therefore it's almost impossible to go back. This is highly annoying to me when that happens, and to somebody that doesn't understand what is happening, it basically appears as if the browser have completely failed.

So I think we need to make a use case analysis on this and look at all the options.

So far I'm inclined towards your "blank page" suggestion, but I would say that instead of making it blank, just make it a standard page, but prevent the login box from showing.

comment:5 Changed 14 years ago by fguillaume

Well, error information that has to be preserved is just the URL that caused the Not Found, that's easy.

If you do the redirect in javascript there are ways to replace the history so that back works correctly.

comment:6 Changed 14 years ago by ebarroca

  • Milestone changed from CPS 3.4.0 to CPS 3.4.1

comment:7 Changed 13 years ago by sfermigier

  • Milestone changed from CPS 3.4.1 to CPS 3.4.2
Note: See TracTickets for help on using tickets.