Make WordPress Core

Opened 19 years ago

Closed 19 years ago

Last modified 17 years ago

#972 closed enhancement (fixed)

No "save and continue editing" for pages

Reported by: anonymousbugger's profile anonymousbugger Owned by: skippy's profile skippy
Milestone: Priority: normal
Severity: normal Version: 1.5
Component: Administration Keywords: bg|commit bg|has-patch
Focuses: Cc:


Why isn't there a "save and continue editing" button for pages like there is for posts?

Attachments (1)

page-save-and-continue.diff (724 bytes) - added by anonymousbugger 19 years ago.

Download all attachments as: .zip

Change History (16)

#1 @anonymousbugger
19 years ago

  • Patch set to No

#2 @coffee2code
19 years ago

If by save you mean saving a page as a draft, it's as Matt said in bug #485: "It's not doable with the [current] implementation."

#3 @anonymousbugger
19 years ago

No, that's not what I mean. I missed 0000657 on my pass through mosquito, but this is not a duplicate of 0000485. I am not talking about a draft. I am talking about publishing the page, but being able to make more changes immmediately. This is analagous to regular word processing and saving the document regularly.

I don't understand why this can't be done, as all it would require is a normal save with an added redirect back to the page in question's edit screen.

#4 @nbachiyski
19 years ago

In the patch: added a 'Save and Continue Editing' button in edit-page-form.php.
post.php handles both page and post save&continue request perfectly.
Or I am missing something?

edited on: 02-28-05 15:19

#5 @coffee2code
19 years ago

Yes, the "can't be done at the moment" primarily applies to saving pages as drafts. Save-as-you-go should still be viable.

#6 @coffee2code
19 years ago

  • Patch changed from No to Yes

#7 @anonymousbugger
19 years ago

Thank you, Scott. That's exactly what I thought.

#8 @skippy
19 years ago

  • Keywords bg|2nd-opinion bg|dev-feedback added
  • Owner changed from anonymous to skippy
  • Status changed from new to assigned

this should get rolled into a proposed unified post entry screen, with a single "Save" button.

See this thread for some opinions.

#9 @markjaquith
19 years ago

Agreed. I think a unified post entry screen is the way to go.

#10 @skippy
19 years ago

  • Milestone set to 1.5.2

#11 @markjaquith
19 years ago

  • Keywords bg|commit added; bg|2nd-opinion bg|dev-feedback removed

Tested the patch on /branches/1.5/ and it works as it should. A lot of people have been wanting to get this in for 1.5.2, so I'm recommending it for commit.

#12 @markjaquith
19 years ago

  • Keywords bg|has-patch added

#13 @matt
19 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [2780]) Fixes #967, Fixes #972, Fixes #1578, Fixes #1580, Fixes #1567, Fixes #1481, Fixes #1186

#14 @matt
19 years ago

  • Resolution set to fixed

(In [2826]) Fixes #972 for 1.6

#15 @(none)
17 years ago

  • Milestone 1.5.2 deleted

Milestone 1.5.2 deleted

Note: See TracTickets for help on using tickets.