Opened 15 years ago

Last modified 15 years ago

#81 closed defect (FIXED)

After submitting, user should go to user page with notification

Reported by: Jef van Schendel Owned by:
Priority: minor Milestone:
Component: programming Keywords:
Cc: Parent Tickets:

Description

I think that once a user is done submitting/naming/ordering his media, he doesn't go to a special "Success" page, but rather back to his user page where his latest images are shown. Or maybe the gallery he posted those images in?

Either way it's probably a good thing if the user can see the new media, as a clear sign that it worked and that it's online. Preferably with an obvious notification that says "Submissions successful! [Upload more media]" or something similar.

Attachments (1)

temp.png (19.2 KB ) - added by Jef van Schendel 15 years ago.
temp.png

Download all attachments as: .zip

Change History (9)

by Jef van Schendel, 15 years ago

Attachment: temp.png added

temp.png

comment:1 by Jef van Schendel, 15 years ago

Jef van Schendel wrote:

Preferably with an obvious notification that says "Submissions successful! [Upload more media]" or something similar.

And after filing this bug I noticed that our bug tracker does pretty much the same thing, as shown in the attachment. :)

comment:2 by Christopher Allan Webber, 15 years ago

Good call. In our case images might not appear immediately and you might have to refresh to see them until we get things nice and ajaxy where new items automatically appear.

comment:3 by Christopher Allan Webber, 15 years ago

What I mean is that in the meantime it might say "media submitted and will appear here"

comment:4 by Jef van Schendel, 15 years ago

That sounds like a good stopgap solution to me. :)

How about: "Submission succesfull! Once it's done processing it will appear on this page.

comment:5 by Christopher Allan Webber, 15 years ago

The way that Zine does this is they keep messages in a "session 'flash' buffer".

    msg = _(u'The entry "%s" was updated successfully.')

flash(msg % escape(post.title))

and later:

def flash(msg, type='info'):
    """Add a message to the message flash buffer.

    The default message type is "info", other possible values are
    "add", "remove", "error", "ok" and "configure". The message type affects
    the icon and visual appearance.

    The flashes messages appear only in the admin interface!
    """
    assert type in \
        ('info', 'add', 'remove', 'error', 'ok', 'configure', 'warning')
    if type == 'error':
        msg = (u'<strong>%s:</strong> ' % _('Error')) + msg
    if type == 'warning':
        msg = (u'<strong>%s:</strong> ' % _('Warning')) + msg

    local.request.session.setdefault('admin/flashed_messages', []).\
            append((type, msg))

This seems like a good idea, having a messaging buffer. This might have been what aaronw was talking about earlier with adding a messaging framework like: https://docs.djangoproject.com/en/dev/ref/contrib/messages/

comment:6 by Jef van Schendel, 15 years ago

Status: NewClosed

comment:6 by Jef van Schendel, 15 years ago

This bug was fixed at http://bugs.foocorp.net/issues/409

comment:7 by Will Kahn-Greene, 14 years ago

The original url for this bug was http://bugs.foocorp.net/issues/366 .
Relations:
#48: related, #119: related

Note: See TracTickets for help on using tickets.