Thread

Hi there,

blank site with 2.1.3 installed, and

$config['autosave_interval_seconds'] = "0";

set in the config.php but autosave is still enabled (showing the autosave time next to the submit button on the publish page)

Is there a new way to disable this in 2.1.3 that I’ve overlooked?

Cheers,

Rob,

Ok it still disables it, as in the button does not appear on edit page any more. I would submit what you see beside the publish submit button as a bug in our tracker

Hi John, you’re right the button is not on the edit page, however, in the publish page, if you open firebug and the console log, it fires this on every single keypress:

200 OK 140ms jquery…7873683 (line 131) 
POST <a href="http://bwf.epwebsites.co.uk/admin/index.php?S=070a70181a67e175aa7b75571a0c174472310e0e&D=cp&C=content_publish&M=autosave">http://bwf.epwebsites.co.uk/admin/index.php?S=070a70181a67e175aa7b75571a0c174472310e0e&D=cp&C=content_publish&M=autosave</a>

I’m not sure if it’s actually writing anything to the DB but it is definitely updating the time by the submit button. Would this be the same bug for the tracker?

Here’s a screenshot to show you what I mean: http://grab.by/9fd4

Rob,

Yes, just submit all your findings in the Bug Tracker as one bug maybe title ‘Disable Autosave showing on Publish page’

Will do, cheers!

Cheers 😊

THREAD RESURRECTIONNNN

Hi guys, this is still happening in 2.1.5 and 2.2 Dev preview. If you open Firebug, go to the Console tab and type in any normal text input field, or title, or URL title, you will see a gazillion autosaves, one for every single character you type.

This is with autosave_interval_seconds set to ‘0’. Seems like EE is taking this quite literally, rather than turning it off!

On my ticket: https://support.ellislab.com/bugs/detail/15369/ it says it’s been fixed for next release, is there some way I can re-open my ticket? Or is it referring to a release that hasn’t finished i.e. 2.2 (post dev preview)?

Thanks,

Rob

Hey Rob–

I think the comment on that bug report will be enough. I’ll make sure it gets escalated to our dev team so they can look into it.

Quick question: has this problem re-surfaced, or did it never go away in the first place?

Kevin

Thanks Kevin,

It started with 2.1.3 and has never gone away since

Rob

Thanks Rob,

I will keep this thread open for a while longer in case our dev team have any questions for you

Err guys..

“Fixed a bug (#15369) where setting the autosave interval to 0 caused it to continually fire instead of disabling it.”

Not sure if it’s a 2.1.3 -> 2.2 upgrade issue, but this is definitely still happening.

THREAD RESURRECTIONNNNNNN

Oh and also, the ‘autosaved data’ has gone back to showing up on the edit page now!

Hi Rob,

Hmm… there’s a minor bug in the implementation. Looks like the zero needs to be an integer for it to work right now, so the config line needs to read:

$config['autosave_interval_seconds'] = 0;

Notice the lack of quotes around the zero. In the upcoming release, we’re type casting the config.php value to make sure it works whether its a string or an integer.

Does that work?

That works Kevin!

Thanks!

Rob

Glad that Kevin helped you out, Robzor.  If you need anything else, please let us know in a new thread.