Solution to Wordpress 2.5.1 Auto-save Problem
Surfacing issues and bugs with ‘my’ install of WordPress 2.5.1 - 2.5.1 AutoSave Bug
This is quite common so it would seem and is a very very frustrating one at that. Simply, the Autosave kicks in on a repeated cycle, thus pretty much locking you out of the site.
It seems to make repeated Ajax requests which means you cannot do any editing. It even locks out the browser windows, so that any other site you have in other browser tabs within the same window, also become unresponsive. The only solution is to quite out and go back in. But the issue starts up again after the first AutoSave or manual save, what ever comes first.
It is well documented on the Wordpress Forums, here is one post that highlights the issue, along with some of my own comments. The main post is here:
Problem 2.5.1 post_new.php and post.php
My comments are further down.
Solution to Wordpress 2.5.1 Auto-save Problem
But I have found a, what seems to be, simple solution or fix, or hack or bodge, whatever you want to call it which I have posted here direct on the WordPress forums:
Inelegant Fix Here for Autosave duration.
After seeing many posts and replies on this issue here, including several by myself:
http://wordpress.org/support/topic/172302/page/2?replies=34
I have posted the following article at the end of that post, but thought it wise to create a new post so people can easily find it while searching the forums.
Not being a coder, I decided to take a crack myself. I think I have found a make do hack, until it can be solved properly.
Edit your ‘autosave.js’ file which can be found in ‘WP-includes’>’JS’>’autosave.js’
There are some values on line 5-7:
jQuery(function($) {
autosaveLast = $('#post #title').val()+$('#post #content').val();
autosavePeriodical = $.schedule({time: autosaveL10n.autosaveInterval * 1000,
func: function() { autosave(); }, repeat: true, protect: true});
So I changed this:
{time: autosaveL10n.autosaveInterval * 1000, func: function()
{ autosave(); }
to something like this:
{time: autosaveL10000n.autosaveInterval * 1000000, func: function()
{ autosave(); }
All i did was take a guess and increase these values to some silly high number.
Not sure if this will have any other unwanted side affects, guess time will tell or someone can tell me.
So far, after creating a post and manually saving it, the autosave has not kicked in. This giving me time to actually write a post etc.
I’m not too sure what these values equate to in time wise, milliseconds etc, but it appears to work.
You could try removing the complete ‘autosave.js’ file and see what happens, I may try that later. Just back it up.
Hope that helps for the time being.
2 comments ↓
This solution didn’t work for me.
I fix it by commenting line 103 in post.php and line 6 in post-new.php:
//wp_enqueue_script(’autosave’);
I hope this helps…
manuels last blog post..Los SMS no afectarán a los jóvenes a la larga
MANUEL> Well, glad you found a solution that works for you, seems one of these problems that has various causes thus various fixes.
Im gonna try your fix later after I revert my fix back to how it was.
Thanks for leaving the useful comment.
I would suggest leaving your fix on the Wordpress that I mentioned, this would be useful for other people to see.
Best
Leave a Comment