Ticket #972 (closed enhancement: fixed)

Opened 4 years ago

Last modified 2 years ago

No "save and continue editing" for pages

Reported by: anonymousbugger Assigned to: skippy
Priority: normal Milestone:
Component: Administration Version: 1.5
Severity: normal Keywords: bg|commit bg|has-patch
Cc: mysz

Description

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

Attachments

page-save-and-continue.diff (0.7 kB) - added by anonymousbugger on 05/21/05 06:35:23.

Change History

02/25/05 03:25:29 changed by anonymousbugger

  • Patch set to No.

02/25/05 05:40:29 changed by 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."

02/28/05 00:26:39 changed by 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.

02/28/05 09:34:22 changed by 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

03/01/05 05:47:45 changed by 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.

03/01/05 05:48:13 changed by coffee2code

  • Patch changed from No to Yes.

03/27/05 23:32:40 changed by anonymousbugger

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

05/21/05 06:35:23 changed by anonymousbugger

  • attachment page-save-and-continue.diff added.

06/30/05 14:30:28 changed by skippy

  • keywords set to bg|2nd-opinion bg|dev-feedback.
  • 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.

06/30/05 17:28:18 changed by markjaquith

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

08/11/05 12:41:27 changed by skippy

  • milestone set to 1.5.2.

08/14/05 12:24:54 changed by markjaquith

  • keywords changed from bg|2nd-opinion bg|dev-feedback to bg|commit.

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.

08/14/05 12:32:11 changed by markjaquith

  • keywords changed from bg|commit to bg|commit bg|has-patch.

08/14/05 18:06:06 changed by matt

  • status changed from assigned to closed.
  • resolution set to fixed.

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

08/30/05 23:06:04 changed by matt

  • status changed from closed to closed.
  • resolution set to fixed.

(In [2826]) Fixes #972 for 1.6

11/30/06 19:41:47 changed by

  • milestone deleted.

Milestone 1.5.2 deleted