2019-07-02 22:47:03 |
Jennifer Pringle |
description |
Evergreen 3.3.0
Similar to https://bugs.launchpad.net/evergreen/+bug/1813646
The web client switches between the old angularJS and new angular log in page and home page depending on what page you're on when you log out.
For example if you log out while you're on the Server Administration page you are taken to https://SERVER/eg2/en-US/staff/login When you log back in you go to https://SERVER/eg2/en-US/staff/splash
If you log out while you're on the Local Administration page you are taken to https://SERVER/eg/staff/login When you log back in you go to https://SERVER/eg/staff/
On a server running the Concerto data set the login and home pages look a little different between the old angularJS and the new angular. If consortia have customized the home page (we have links specific to our consortium) than the two home pages look quite different.
Ideally Evergreen uses the same login and home page regardless of what page you're on when you log out. |
Evergreen 3.3.0
Similar to https://bugs.launchpad.net/evergreen/+bug/1813646
The web client switches between the old angularJS and new angular login page and home page depending on what page you're on when you log out.
For example if you log out while you're on the Server Administration page you are taken to https://SERVER/eg2/en-US/staff/login When you log back in you go to https://SERVER/eg2/en-US/staff/splash
If you log out while you're on the Local Administration page you are taken to https://SERVER/eg/staff/login When you log back in you go to https://SERVER/eg/staff/
On a server running the Concerto data set the login and home pages look a little different between the old angularJS and the new angular. If consortia have customized the home page (we have links specific to our consortium) than the two home pages look quite different.
Ideally Evergreen uses the same login and home page regardless of what page you're on when you log out. |
|