Opened 9 years ago

Closed 8 years ago

#182 closed task (fixed)

Logging in should take me back to the page where I clicked the login link

Reported by: Karen Rustad Owned by:
Priority: minor Milestone: 0.3.2
Component: programming Keywords:
Cc: deletesoftware@… Parent Tickets:

Description

Right now, it always takes me back to my profile. This is often an
interruption -- if I'm e.g. logging in to comment on someone's
photo, I then have to go to some other page to login, get sent to
my profile page, and then have to figure out how to get back to the
photo I wanted to comment on.

Ideally, logins ought to be entirely "in-place"--not require going
anywhere else. So the workflow would be: click upper-right login
link -> login fields appear via JS in the top right (or in an
overlay over the page, whichever) -> I enter my credentials and hit
the button -> Without refreshing, the page gets AJAXily updated to
reflect that I'm now logged in (different top-right links, 'edit'
links, comment fields, and the like appear in the appropriate
places on the page, etc), or a handy-dandy 'your login info didn't
work, foo'!' message appears in the top right.



Subtickets

Change History (7)

comment:1 Changed 9 years ago by Will Kahn-Greene

The original url for this bug was http://bugs.foocorp.net/issues/474 .

comment:2 Changed 9 years ago by Aleksej

Cc: deletesoftware@… added
Milestone: 0.2.1

comment:3 Changed 9 years ago by Aleksej

Milestone: 0.2.1

comment:4 Changed 8 years ago by Aleksej

Component: uiprogramming
Type: defecttask

comment:5 Changed 8 years ago by spaetz

1) Do login in-place, or 2) use django's method of adding an optional ?next=<URL_REFERER> parameter to the login url. On successful login, you'll be redirected back to URL_REFERER.

comment:6 Changed 8 years ago by spaetz

This would be fixed in this branch "182_login_next_url" repo: git://gitorious.org/~spaetz/mediagoblin/spaetz-mediagoblin.git

comment:7 Changed 8 years ago by spaetz

Milestone: 0.3.2
Resolution: fixed
Status: acceptedclosed

Elrond has now reviewed this branch and OK'd it. Pushing to master before the 0.3.2 release as it's a small code change, but a great win in usability. Fixing this bug in a record 16 months :-). Thanks for reporting.

Note: See TracTickets for help on using tickets.