WordPress.org

Make WordPress Core

Opened 7 years ago

Closed 7 years ago

#6024 closed defect (bug) (fixed)

Draft: Save button behavior should be consistent

Reported by: lloydbudd Owned by: ryan
Milestone: 2.5 Priority: normal
Severity: normal Version: 2.5
Component: General Keywords:
Focuses: Cc:

Description

Draft: Save button behavior should be consistent

ENV: WP trunk r7080 2.5-beta1

Currently, the first time you click save it reloads the post, and the next time it takes you back to a blank new post or to manage posts depending on what was your path to create/edit the draft post.

A lot of people have complained about missing the Save & Continue button in trunk. When I ask them about their use case, it is that they have been trained to click the save button regularly while writing. The like and trust that experience, and it is frustrating that now, after that 2nd save they have any extra step to get back to their post.

This is very natural habit, because we don't have high confidence in autosaves or applications not crashing. Web apps with similar experiences, like web email for example, Save is an in place save, and Send (like Publish) is the completion (exit) of the task.

I guess you can argue that for people that trust autosave, or only save when they are done that it is an extra step, but I think these people are currently in the minority, and

There already are Related and I think it is better behavior to allow the person to explicitly leave editing when they want to.

ADDITIONAL DETAILS

Possible solution: Save button should always save and reload the post being edited.

Change History (8)

comment:1 @ryan7 years ago

When saving a published post that was edited by following a front page link, I think we should redirect back to the page. Saving unpublished posts should definitely always reload the editor, I think.

comment:2 follow-up: @ryan7 years ago

  • When saving a published post visited via an edit_post_link() on the blog, return to that post on the blog.
  • When saving a draft or pending post, always reload the editor. Save and continue.
  • When saving non-draft, non-pending and there is no referrer info, reload the editor.
  • When saving non-draft, non-pending and there is referrer info, redirect to referrer.
  • When publishing or submitting for review and there is referrer info, redirect to referrer.
  • When publishing or submitting for review and there is no referrer info, redirect to post-new.php. Maybe we should return to edit.php instead.

comment:3 @ryan7 years ago

(In [7084]) Change save post redirects. see #6024

comment:4 @ryan7 years ago

That changes the behavior for posts. I'll do pages once we're satisfied.

comment:5 in reply to: ↑ 2 ; follow-up: @zamoose7 years ago

Replying to ryan:

  • When saving non-draft, non-pending and there is referrer info, redirect to referrer.

How does this affect the bookmarklet behavior? I.e., I click "Press It" on a page I care to comment upon, I type up something briefly, then wish to save (To Be Sure) my progress and continue editing. In the past, I could hit "Save & Continue...", whereas the implication of your statement is that I will be redirected back to the referring page, regardless.

Or am I reading it incorrectly?

comment:6 in reply to: ↑ 5 @lloydbudd7 years ago

Replying to zamoose:

Or am I reading it incorrectly?

Why be worried if you're reading it correctly or not. Try it for yourself, and comment on the behavior you experience. Developers work to spec, testers work to implementations -- though appreciate greatly good specifications. Neither his explanation nor the implemented behavior is as you describe being concerned with, the behavior (I tested it) is "When saving a draft or pending post, always reload the editor. Save and continue."

ENV: WP trunk r7086 (2.5-beta1)

Ryan, the current behavior is as you describe, and I think it is very good.

If we wanted to improve it further, I would suggest that a Publish event (either clicking publish or saving an already published post) should always result (redirect) in the published post being displayed as it would be for any reader of the blog. This consistently would provide the clearest message that the post is published.

comment:7 @ryan7 years ago

(In [7116]) Change save page redirects. see #6024

comment:8 @ryan7 years ago

  • Milestone changed from 2.6 to 2.5
  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.