![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 17 years ago
Closed 17 years ago
#9909 closed defect (bug) (invalid)
newer autosave than currently shown
| Reported by: | ranchnachos | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | Autosave | Version: | 2.7.1 |
| Severity: | minor | Keywords: | post autosave bug |
| Cc: | Focuses: |
Description
The bug is pretty much summed up in the title summary.
I went to edit a post, clicked on the "update" button and after the page refreshed a notice popped up at the top of the browser saying something about "There is a newer autosave than the post currently shown"
But how can that be, since the newest revision would be when I clicked the Update button after editing?!
Someone let me know if this is suppose to happen or if it really is a bug.
Change History (1)
Note:
See TracTickets
for help on using tickets.
Most likely it decided to autosave at almost the same time you clicked Save so there were two save requests to the server and the autosave one completed a bit slower.