WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#11043 closed defect (bug) (invalid)

Later autosave notification should check revision contents

Reported by: johnhennmacc Owned by: azaozz
Milestone: Priority: normal
Severity: normal Version: 2.9
Component: Autosave Keywords:
Focuses: Cc:

Description

A number of times, I have seen the situation where I am advised that there is an autosave of a post only to find that the contents of both were identification. I think that they way to reproduce this is to update a published post and then leave the screen unchanged for a while before navigating elsewhere. It has been seen on both the page and post editing screens.

Change History (3)

comment:1 @caesarsgrunt6 years ago

Yes; this is very annoying. I haven't tried yet, but I don't think it should be hard to fix.

comment:2 @lloydbudd6 years ago

  • Resolution set to invalid
  • Status changed from new to closed

Closing ticket as invalid. Need a reproducible scenario or technical diagnostics -- the exception is a wide spread, critical issue.

Aside, the revision feedback does not do a good job of identifying when the revision diff is meta (like comments are open) -- not sure if reported, if not should be a new tic.

PS. Please include your specific version or svn revision # in the Description -- particularly when using the trunk version.

comment:3 @westi6 years ago

  • Milestone Unassigned deleted
Note: See TracTickets for help on using tickets.