nonhocapito

I’m not experiencing any instabilities, at least with the last version 2.5.2. It seems to look cooler and be faster than other similar plugins right now.

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

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?

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.

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.

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?

Same problem here.

I solved this problem.
Open plugins.php and replace the code:

wp_redirect('plugins.php?error=true'); // we'll override this later if the plugin can be included without fatal error
ob_start();
@include(ABSPATH . PLUGINDIR . '/' . $plugin);
$current[] = $plugin;
sort($current);
update_option('active_plugins', $current);
do_action('activate_' . $plugin);
ob_end_clean();

with the code:

<p>$current[] = $plugin;
sort($current);
update_option('active_plugins', $current);
include(ABSPATH . PLUGINDIR . '/' . $plugin);
do_action('activate_' . $plugin);</p>


…this way it will throw a reassuring parse error ??

–so nobody has a hint about this? Seems pretty important to me… ??