Ticket #67 (WontFix)Mon Oct 23 16:26:09 UTC 2006
Log in links do not allow "back" or a return to the previous location
| Reported by: | Andrew Hodgkinson (6) | Severity: | Minor |
| Part: | Web site: Hub (single sign-on mechanism) | Release: | 2nd public site release |
| Milestone: | 2nd public site release completed | Status | WontFix |
Details by Andrew Hodgkinson (6):
Hub only supports explicit return-to locations presently. This means that the “log in” link and similar mechanisms tend to return to the tasks control panel, not an originating page, except for the explicitly set cases.
In future, it might be better if Hub could examine, say, the HTTP referer header (if set) should an explicit return path not exist, when logging in.
Changelog:
Modified by Andrew Hodgkinson (6) Mon, October 23 2006 - 20:33:59 GMT
- Severity changed from Enhancement to Minor
This is quite important for Typo with the level of Hub integration present from Changeset #111. The “You must log in to add a comment” link gives no history of the article being viewed so the user has to navigate back to it manually, one way or another. Raised the severity to “Minor” from “Enhancement” because the usability wrinkle, in this case, is sufficiently large to be considered a bug.
Modified by Andrew Hodgkinson (6) Wed, April 04 2007 - 18:31:06 GMT
- Status changed from Open to WontFix
Typo was in fact the only application left that had a manual login route into Hub, using the login_hop mechanism in Hub to attempt to store a return path. The integration of Typo 4.1 with Hub implements a new articles controller method which is not cached and requires login; this means Hub redirection falls out in the wash transparently. Meanwhile, the everyday article reading page can still be cached, providing a distinct performance improvement over earlier versions. Hence, all in all, this doesn’t need to be “fixed” anymore.
See Changeset #193 (huge!) and Changeset #194 for Typo 4.1 details.
