Ticket #972 (closed enhancement: fixed)
No "save and continue editing" for pages
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| 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
Change History
comment:2
coffee2code — 7 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."
comment:3
anonymousbugger — 7 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.
comment:4
nbachiyski — 7 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
comment:5
coffee2code — 7 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.
comment:7
anonymousbugger — 7 years ago
Thank you, Scott. That's exactly what I thought.
- 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.
comment:9
markjaquith — 7 years ago
Agreed. I think a unified post entry screen is the way to go.
comment:11
markjaquith — 6 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.
comment:13
matt — 6 years ago
- Status changed from assigned to closed
- Resolution set to fixed

