[wp-trac] [WordPress Trac] #39917: AutoSave is not disabling in spite of settings added in wp-config.php
WordPress Trac
noreply at wordpress.org
Mon Feb 20 15:43:06 UTC 2017
#39917: AutoSave is not disabling in spite of settings added in wp-config.php
-------------------------------+------------------------------
Reporter: subrataemfluence | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Autosave | Version: 4.7.2
Severity: normal | Resolution:
Keywords: reporter-feedback | Focuses: administration
-------------------------------+------------------------------
Comment (by azaozz):
Replying to [comment:5 subrataemfluence]:
It's a bit more complex :)
There are two autosaves:
- to the server: creates a revision post or updates the post if it is a
draft by the same author.
- in the browser's sessionStorage: this is for "disaster recovery" and is
accessible only if the browser crashes or the post cannot be saved,
network is down, etc.
The user can only control the interval for the aurosave to the server.
This was intended for reducing the server requests while the Edit Post
screen is loaded (some very cheap hosting accounts had issues with too
many requests). However now it's mostly a left-over as we use Heartbeat
for autosaves.
> Setting in `wp-config.php` does have some effect in preventing auto-
drafting (auto-saving) partially. If I keep that on, only title and
content gets auto saved and only once
Not quite. Auto-drafts cannot be disabled. As dd32 explained above they
are user to "reserve" a row/post_ID in the posts table for the upcoming
post when the user loads the Add New Post screen (and in few other cases).
If no post is saved they are deleted a week later.
> Without the setting, auto save also works in edit mode but not when the
setting is added.
Right. Autosave to the server is triggered at least once after loading the
Add New Post screen. This is not affected by the interval from
`AUTOSAVE_INTERVAL`.
Can I ask why would you want to disable autosaves? They are there to
safeguard the content typed by the users and are "basic functionality"
that is always needed.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/39917#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list