No "save and continue editing" for pages

[anonymousbugger]

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

[coffee2code]

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."

[anonymousbugger]

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.

[nbachiyski]

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

[coffee2code]

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

[anonymousbugger]

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

[skippy]

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

See ​this thread for some opinions.

[markjaquith]

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

[markjaquith]

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.

[matt]

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

[matt]

(In [2826]) Fixes #972 for 1.6

[(none)]

Milestone 1.5.2 deleted