WordPress.org

Ready to get started?Download WordPress

Forums

WP 2.5: "Save and continue editing" was a great feature. Why removing it? (27 posts)

  1. nonhocapito
    Member
    Posted 6 years ago #

    Sometime the eagerness to bring change can be VERY unmotivated.

    The button that said "Save and continue editing" in the editor was a great, obvious feature.
    I can't think of any imaginable reason to remove it, except that who removed it probably didn't use it. He maybe had a so fast connection he could get in and out of the editor at the speed of light.
    Whatever.

    It is absurd to write without saving now and then, or to save only when one has finished and can walk out of the page. Especially if you don't use the horrid wysywyg thing, like me.

    Please WP people, do consider give us back this feature. At least as an option in the settings "walk out of the page after saving" or something.

  2. nonhocapito
    Member
    Posted 6 years ago #

    here's a hack to work around this thing:

    open edit-form-advanced.php.

    look for

    <p class="submit">
    <input type="submit" name="save" id="save-post" value="<?php _e('Save'); ?>" tabindex="4" class="button button-highlighted" />

    and replace it with:

    <input name="save" type="submit" id="save" class="button" tabindex="3" value="<?php _e('Save and Continue Editing') ?>" />
    <p class="submit">
    <input type="submit" name="save" id="save-post" value="<?php _e('Save'); ?>" tabindex="4" class="button button-highlighted" />

    ...you will have your button back.
    Now, does anyone know how to turn this into a plugin?

  3. Keilya
    Member
    Posted 6 years ago #

    I think two of the reasons it was removed was because

    1) Auto-save feature. The presence of that (even in 2.3) kinda made the "Save and continue editing" button redundant. Though I do understand that many people would like to do some "manual saving" on the safer side.

    2) Changes in the page you're forwarded to after saving.

    -In 2.3 when you chose to edit a post from the "Manage" section, upon clicking "Save", the page would return to the default posting page with the original post gone, but now the edited post is loaded again. (Similar to "Save and Continue Editing".)

    -In 2.3, should you decided to click the "Edit" link visible to the adminstrator on the blog, the "Save" button would return you to the blog front page after editing. However now, the edited post is loaded instead, and it seems like to be fulfiling the function of "Save and continue editing" yet again.

    So mainly, I think they didn't take it out because they "didn't use it" or "had a fast connection", rather I think the team knew that everyone used it, and instead of having 2 save buttons, they deleted one off and gave the remaining one the same function (well rather similar) as the good old "Save and Continue Editing".

    But yeah, I guess for people who like to save drafts manually, it's become a bit of a pain.

  4. nonhocapito
    Member
    Posted 6 years ago #

    thing is, if you start a new post, and start writing, after how long do you think the autosave feature will kick in?

    I tried walking out of the page without saving after more than a minute and the post was nowhere around in the drafts! What if I had crashed the computer?

    So either they give me back the manual save or they fix the autosave feature.

    Bottom line, I want to have more control on this kind of thing. At least in the settings.

  5. Samuel Wood (Otto)
    Tech Ninja
    Posted 6 years ago #

    Autosave happens on 2 minute intervals.

    The new save button should work the same as the save and continue button used to.

  6. nonhocapito
    Member
    Posted 6 years ago #

    Well two minutes can be a long time.
    Anyway, the "save and continue editing" button used to keep you in the editor to go on working. The "save" button doesn't. That's the point.
    After saving, you either have to go back in the browser, or you have to find a "edit" link if it is there.
    Not very practical. I even don't understand why this should happen, especially before one has published the post.

  7. Samuel Wood (Otto)
    Tech Ninja
    Posted 6 years ago #

    Anyway, the "save and continue editing" button kept you in the editor to go on working. The "save" button doesn't. That's the point.

    Err.. the save button does go right back to the post editor. That's my point.

    I just tried it out myself. Created a new post, added a title and some text. Now, it auto-saved more or less immediately after I typed a title (it does this in order to give you the permalink editor space), but still, when I hit save, it went right back to the write post screen with a new yellow box at the top saying "Post Updated".

  8. Samuel Wood (Otto)
    Tech Ninja
    Posted 6 years ago #

    Here, I made a quick screencast showing off that behavior:
    http://screencast.com/t/diqc7SnCrs

  9. Roy
    Member
    Posted 6 years ago #

    Hahaha, I never saw that! I'm glad to see a "save" AND a "publish" button. I guess I can continue working like I do now whenever I upgrade to 2.5.

  10. moonlightingstudent
    Member
    Posted 6 years ago #

    This thread is an interesting example of innovation in 2.5. I used to use the "Save and Continue" button but knowing the autosave had my back, I mostly used it to save and stay in the post editor. The single save button that keeps you in the editor is an improvement. @Ottom42 Thanks for clarifying that.

    However, I noticed that Save no longer returns you to the public view of the post after you enter the editor via the "Edit" button on the post itself. If that is true, that's a bummer. (Just tested and noticed an option to "go back" instead of auto redirection...that is easy to live with).

    Seeing how Publish is on the right still, I don't actually miss the other post attributes cluttering up the right side of the screen like my first impression led me to feel.

  11. nonhocapito
    Member
    Posted 6 years ago #

    uhm, you're right, my experience was with posts that had already been published and that I was trying to edit, something that I do quite often.
    In those cases you do are walked out of the post. I guess that's a problem I have.
    Question: Does the autosave works when the post is already published?

  12. Samuel Wood (Otto)
    Tech Ninja
    Posted 6 years ago #

    Hmmm.. Still not seeing the problem here, it works the way I would expect it to work. Another screencast showing editing an existing post:

    http://screencast.com/t/dtFDAwuFrN

  13. moonlightingstudent
    Member
    Posted 6 years ago #

    No problem here. I'm guessing a few people are learning details about changes in 2.5 (I know of at least one for sure).

  14. nonhocapito
    Member
    Posted 6 years ago #

    Otto42: Believe it or not, when I'm into a published post and I hit save I am taken out of the editor page.

  15. paleomedia
    Member
    Posted 6 years ago #

    I too am now taken out of the editor when I save...

    But I have a different question. I used to use the save and continue editing feature to update a long post throughout the morning. Does that screw up the RSS feed or the blog flow or is it otherwise bad blogging protocol to do it that way. I basically have a longish list of links every morning and I like to update the post as I find the links... so is that bad form?

    I have also looked for a plugin that will time stamp a paragraph within a post... anyone heard of such a thing?

    you can see it at my site under the heading Newsrack: http://www.paleomedia.org

    Thanks,

    Nate

  16. paleomedia
    Member
    Posted 6 years ago #

    PS The Save feature does seem to work now... sorry. My protocol question still stands...

  17. Samuel Wood (Otto)
    Tech Ninja
    Posted 6 years ago #

    Does that screw up the RSS feed or the blog flow or is it otherwise bad blogging protocol to do it that way. I basically have a longish list of links every morning and I like to update the post as I find the links... so is that bad form?

    Generally speaking, yes. Your RSS feed will update the moment you update posts, but some of your readers may not see the post again in their feedreaders. This especially applies to anybody using Google Reader (which is usually the most popular one), because Google Reader caches your feed and will not update older posts like that.

    See, once you've published your content, then it's out there, and not everybody is necessarily reading your blog by looking at your site. Your content is syndicated, people might read it elsewhere. Almost all the blogs I read I don't actually go and visit unless I have a comment for them or something.

    So, it is generally bad form to modify a post after publication, or to do it too often. Better to post your links as separate posts, but style them differently or something. Search for "asides" for ideas on how to do this. For example, Matt's blog uses asides quite a lot, you can see that they're styled differently (red bar on their left, no title or author, etc). It's an idea, anyway.

  18. ericr23
    Member
    Posted 6 years ago #

    I just noticed that when the post is autosaved, a Preview This Post button appears above the publish status. If I do a manual save, though, I am taken out of the write window and to the (unpublished) post. Going back and forth that way is highly unproductive compared with going between two separate tabs/windows, i.e., the write window and the preview (which you can reload after each manual save -- e.g., to check a table or list layout).

  19. ictlogist
    Member
    Posted 6 years ago #

    So, any answer so far?

    I've got the same problem some have reported: when saving, I'm taken to the "preview" screen.

  20. mingofaust
    Member
    Posted 6 years ago #

    I'm seeing the same odd save-and-kick stuff. I haven't done an exhaustive test, but I do edit posts that have already been published, so maybe that's where I am seeing it. I find it very discombobulating (ching! $10!). My thoughts:

    1. IMHO, I believe the Save button should *always* leave you in the editor. All it should do is Save. It shouldn't assume I want to start a new post. It shouldn't assume I want to see the post I just saved. The interface already has choices for both of those.

    2. The Save button should perform an AJAX autosave, without reloading the page. Why does it have to reload the page? Is it doing something that autosave doesn't? If so, what?

    My 2 cents.

  21. jkuruppu
    Member
    Posted 6 years ago #

    I've got the same problem some have reported: when saving, I'm taken to the "preview" screen.

    how odd!

    i was a bit late in updating, but i've just checked out the editor behavior on our blog, and the "Save and Continue Editing" seems to be the default behavior - I don't get kicked out automatically to the preview page. In fact, after hitting "Save", the following message displays at the top of the page:

    Post updated. Continue editing below or go back.

  22. ninno
    Member
    Posted 6 years ago #

    Hi Friends,

    I try the save button, and I think that nonhocapito and Otto42 are booth right.

    1) I log as an administrator, create a new post, and click the save button, then the yellow caption appear, and I rest on the editing page (like on the Otto42's video).

    2) I log as an editor, create a new post, and click the save button, then the CMS navigete out from the editing page, to the preview (or something like this, so nonhocapito are right).

    I think it is not a feature, it is a bug, because the WordPress work another style, when your are an adminisrator, or your have other role. Unfortunetly I have many editors, and I don't want to give him admin role :(

  23. ictlogist
    Member
    Posted 6 years ago #

    ninno, does not work for me: I'm an admin in my own blog and sometimes I'm sent to the preview screen, sometimes I remain on the edit screen.

    Seems to happen at random, but surely there's a pattern...

  24. HarryRAR
    Member
    Posted 6 years ago #

    I'm also having the problem where 'save' saves and sends me to the preview screen. It's driving me nuts, because I keep doing it automatically and it catches me out every time.

    fwiw, it doesn't matter whether the post is a new one or I'm editing one that's already published; and I'm an admin.

  25. HarryRAR
    Member
    Posted 6 years ago #

    Huh. I just deactivated all plugins and reactivated them again and it seems to be back to the proper behaviour. Should have tried that earlier.

  26. hartley_h
    Member
    Posted 5 years ago #

    I just updated an installation from 2.0.7 to 2.6.1. Lots of changes to get used to. I'm sure I will but I personally miss the old "save and return to wherever you were" button (which was called simply "save". I used the "save and continue editing" as well so I'm glad it's still here (and now called "save").

    My blog is fairly private and I edit published content. I'd nice to be able to click the edit button on the blog page, make the change, save and be taken right back to where I was. It's not the extra click (on "go back") that I mind as much as it's another trip to the server which slows things down.

    If there is an option to "save and return to the blog page you were on" and I've missed it, please advise.

  27. kilwag
    Member
    Posted 5 years ago #

    (in 2.6.2) I find myself editing a published post, having to hit "save" and then having to hit the "go back" link. All the time. Of course you could tell me to edit more carefully before publishing, but still, we used to have three options, and "save" used to work like the current two page process of "save" and "go back"

    How about a:

    Save Button (Works the same as it does now)
    Publish Button (Works the same as it does now)
    Save and Return (Combines the current "Save" and
    "go back" two step process into one)

Topic Closed

This topic has been closed to new replies.

About this Topic