[wp-trac] [WordPress Trac] #11232: UI improvements for 2.9 bulk plugin/theme updater (esp. success/fail msgs)
WordPress Trac
wp-trac at lists.automattic.com
Tue May 25 14:12:31 UTC 2010
#11232: UI improvements for 2.9 bulk plugin/theme updater (esp. success/fail msgs)
--------------------------+-------------------------------------------------
Reporter: jeremyclarke | Owner: ryan
Type: defect (bug) | Status: new
Priority: normal | Milestone: 3.0
Component: UI | Version:
Severity: normal | Keywords: needs-patch ui-feedback
--------------------------+-------------------------------------------------
Comment(by jeremyclarke):
Replying to [comment:36 johnonolan]:
> If I finish approving all my comments and I hit "update" I don't want to
be returned to the comments screen after updating.. there's nothing else
for me to do there.
In WordPress after a bulk comments operation is completed you are
redirected back to the comments page and shown a message about the results
of the bulk update. That is exactly how it should work because there are
many things you are likely to want to do there, such as continue your work
on other comments. You may also want to make sure that there is nothing
else that needs to be done with regard to comments before you move to
another task.
Just because someone performed a bulk operation on several objects doesn't
mean they finished everything, and it is always better to lead people back
to something they at least recognize as part of the menu structure than to
leave them in dead-end limbo with a text success message.
Replying to [comment:36 johnonolan]:
> I also don't want to be returned to the original updates screen, because
I just updated everything and there's nothing for me to do there either.
One common case where this system gets shown is when you go to
'''Upgrade''' and before updating WP you do a bulk upgrade of your
plugins. In that scenario the user starts toward a goal, updating WP, and
is lead to a dead end after the plugin bulk upgrader. Yes they could go to
the updater again manually, or just wait until they see the update nag
again, but a button that leads back to the updater makes perfect sense
here. It gives the user a next action they can take.
If they know for sure that the updater isn't what they want then they
don't have to press the button/link, but if they're not sure what to do
next clicking that button is a good idea. They will be brought back to the
general updater screen where they can be informed that nothing else needs
updating (or maybe that core wp still needs updating)
--
Ticket URL: <http://core.trac.wordpress.org/ticket/11232#comment:39>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list