Opened 13 years ago

Last modified 4 years ago

#176 accepted defect

Return behavior after adding media is non-intuitive

Reported by: Karen Rustad Owned by:
Priority: minor Milestone:
Component: ui Keywords: bitesized
Cc: Parent Tickets:

Description (last modified by Christopher Allan Webber)

After I add a new piece of media, the site takes me to my profile
page, of all places. Even if I didn't start out on my profile page
when I clicked the 'Submit media' button. How silly.

Two solutions:

1.) After adding new media, always take the user back to their
gallery page. Makes more sense than their profile page--what does
that have to do with their pictures?

2.) After adding new media, take the user back to whatever page
they started out on when they started the media-adding interaction.
This is probably more complicated to code, but it does make adding
media slightly more smooth for the user.



Change History (6)

comment:1 by Jef van Schendel, 13 years ago

A big +1 on this to, as far as I'm concerned.

Originally I think we wanted to show the user a page that contains
the piece of media they just submitted. This (and of course the
message at the top of the page) would tell them that yes, it did in
fact submit and we've got it. So yeah, that would be the gallery
page.

I think one of the objections was that the media will be processed
first and thus can't appear right away. Nonetheless, IMO we should
get as close as possible to the above description. Maybe instead of
a thumbnail, show a small "processing" placeholder image or
something to that effect?



comment:2 by Christopher Allan Webber, 13 years ago

I think some of this will be solved by when we have a panel that
shows media in-processing... it might be that when a user is logged
in and looking at their gallery it'll have a link to the processing
panel and something like:

::

      You have 2 pieces of media processing [-> panel]

Though that might be worthless if it will appear in a microsecond
later.

This might be a job for ajaxyness :)

Regardless, I'm fine with the idea of redirecting to the gallery..
that makes sense to me.



comment:3 by Will Kahn-Greene, 13 years ago

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

comment:4 by Emily O'Leary, 11 years ago

Keywords: bitesized added

Looking at the code for this, one of the simple implementations for this could be to just change the
redirect code to point to the new URI for the media entry.

return redirect(request, "mediagoblin.user_pages.user_home",
                                user=request.user.username)

comment:5 by Christopher Allan Webber, 11 years ago

Description: modified (diff)

I'm not sure there's any clear indication on where to go from here in this bug. It's pretty old... but I agree at the high level that it could be better.

I don't think moving to a user's gallery is better than their homepage though. I think their current homepage is a pretty good place to be.

I'm not sure this bug should be open though... it would be much better for this to be rolled into some "uploading process improvements" type ticket. I wrote up a plan for some better uploading process on the mailing list; that might be a good way to move forward..

comment:6 by Ben Sturmfels, 4 years ago

I think fixing #5564 and redirecting to the processing panel would be enough to close this ticket.

Note: See TracTickets for help on using tickets.