Bug 1384723 - ops ui should render formal 404 error page like ssui
Summary: ops ui should render formal 404 error page like ssui
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Martin Hradil
QA Contact: Matouš Mojžíš
URL:
Whiteboard: general:ui
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-14 01:23 UTC by Dave Johnson
Modified: 2018-01-05 23:48 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-05 18:56:28 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dave Johnson 2016-10-14 01:23:19 UTC
Description of problem:
=================================
ops ui should be consistent with the ssui and have a formal page to render for 404 errors...  see bug 1384722


Version-Release number of selected component (if applicable):
=================================
5.6.2 and 5.7.0.4

Comment 5 Martin Hradil 2017-10-02 14:15:09 UTC
So.. the current state is this:

* API - any 404 from the API is either hidden from the user, or displays our error modal
* $http - any error displays our error modal
* jQuery - either the error modal gets displayed or the right side gets replaced by our rails exception screen (depends on where it happens)
* full page reload - a rails exception screen is shown (which one depends on where it happens)


So.. this is partly solved by having extended the error modal across the JS bits.

But it's probably silly to try to recreate the error modal on a rails exception, + the modal wouldn't look that great floating above nothing, since there will be no pre-existing content on rails exceptions.


Feels like a WONTFIX until we're an SPA, WDYT Dan? :)


Note You need to log in before you can comment on or make changes to this bug.