Closed Bug 893210 Opened 12 years ago Closed 5 years ago

Old revision displayed instead of most recent one

Categories

(developer.mozilla.org Graveyard :: Editing, defect)

Product:
developer.mozilla.org Graveyard
Component:
Editing
Platform:
All
Other
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jswisher, Unassigned)

References

Details

(Keywords: qawanted, Whiteboard: [specification][type:bug])

What did you do? ================ 1. Looked at an article and its history For example: https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement$history https://developer.mozilla.org/fr/docs/Project:MDN/contribuer/R%C3%A8gles_d_%C3%A9tiquettage https://developer.mozilla.org/fr/docs/Project:MDN/contribuer/R%C3%A8gles_d_%C3%A9tiquettage$history  What happened? ============== An older revision appears first in the revision list, and the corresponding version of the page is displayed. What should have happened? ========================== The most recent version of the page should be displayed, and the revision history should be in strict reverse chronological order. Is there anything else we should know? ====================================== A hard refresh did not help this problem.
I wonder if this is related to bug 893210.
Er, I wonder if this is related to bug 866536.
(In reply to John Karahalis [:openjck] from comment #2) > Er, I wonder if this is related to bug 866536. I don't think so there is no corruption in the $history page. But Bug 893778 clearly is a duplicate of this one.
An editor, delapouite, just got the same problem on this page: https://developer.mozilla.org/fr/docs/DOM/element$history This begins to be an epidemy! 4 pages in a week! I'm bumping severity to critical. Something corrupts the DB.
Severity: normal → critical
Depends on: 894393
Here's the full list of affected docs and the SQL to find them: http://pastebin.mozilla.org/2642831
Dammit: https://developer.mozilla.org/en-US/docs/Project:Topic_drivers I'm in the middle of trying to update that, too. I've noticed this, though: It seems to crop up if I save a page then immediately (within a few seconds, anyway), click the edit button again. I don't know if that's just because that's when I notice it most, or because there's a causal relationship though.
Sheppy, I think you revealed an important point. I just noticed the following phenomena. This morning, I'm editing a given page. After a Save, I got the right new pages. No problem, everything fine. But clicking EDIT (not necessary immediately afterwards, but after a couple of minutes too), I sometimes get an old page in the editor. I didn't try to save then, but if I go back a page and reload the editor, I usually get the latest page in the editor and all goes fine. So there may be two things here: 1) A bug allowing to save an outdated modified page (rather than to have a conflict at saving), 2) The editor being given an old page.
For example, even if the history is not corrupted, when I try to access https://developer.mozilla.org/en-US/docs/Web/API/element$edit I don't get the last version in the editor. I'm trying to edit this page (with the last version) since about 30 minutes (trying to reload, force-reload and so on). Will continue to try :-(
If I look in the admin console info about this page I see: Modified: July 17, 2013, 4:05 a.m. Revision Reviewed: 2013-07-16 08:08:12 (Strangely it is not the latest like other around it) Rendering: True deferred rendering / 2013-07-17 04:05:51 (last) / 2013-07-17 04:05:49 (started) / 2013-07-17 04:05:49 (scheduled) (The True deferred rendering is also a bit odd but I don't know if it is normal or not). Hope it helps.
Some of the pages linked from this bug are now straightened out, and some are not.
I just tried to save a change to https://developer.mozilla.org/en-US/docs/Web/JavaScript/A_re-introduction_to_JavaScript I got this error: " This document was modified while you were editing it. Please review the differences between your changes and the changes saved since you started editing. You may save again, but try to resolve any conflicts by hand so that the changes made since you started are not lost. Your Changes Revision 441143 by m_sturgeon on July 16, 2013 6:05:33 PM PDT Current Revision: Revision 441101 by m_sturgeon on July 16, 2013 3:50:32 PM PDT " Note that the revision listed for "Your Changes" is not by me, and was done yesterday.
Jean-Yves notes that this bug and bug 776531 occur at the same time. Are they related?
Flags: needinfo?(lcrouch)
Almost certainly, yes.
Flags: needinfo?(lcrouch)
Raymond, can you help us come up with STR for this bug? Some of us hit it some times, and others hit it very regularly.
Flags: needinfo?(mozbugs.retornam)
Keywords: qawanted
Hi Luke, I'm trying on stage and will let you know if I find a consistent STR.
Flags: needinfo?(mozbugs.retornam)
Just another update of data here: http://pastebin.mozilla.org/2646538 Only 5 documents seem to have been saved with a bad current_revision today. It looks like the bulk of the problem hit on 2013-07-12. Not sure if that helps diagnose the issue any further, but my eyes are bloody so I'm going to go eat.
Could we go back with this query back to last July (inclusive). We got this problem then, and I would like to know if it completely disappeared in between or was just very rare. This info would help to know if it is an old problem and only its frequency is varying or if it may be something recent. My bet is that it is an old problem (like Les said in another bug, likely inherited from Kitsune) but something is making it appears more often these last two weeks.
(In reply to Luke Crouch [:groovecoder] from comment #25) > Just another update of data here: > > http://pastebin.mozilla.org/2646538 > > Only 5 documents seem to have been saved with a bad current_revision today. > It looks like the bulk of the problem hit on 2013-07-12. > > Not sure if that helps diagnose the issue any further, but my eyes are > bloody so I'm going to go eat. Of course, the writers all basically quit working today because of this problem, so that could be part of the reason there were fewer occurrences.
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/4e76bd072993d7792b758a8e061a8ff7f8a2c4c6 bug 893210 - don't cache wiki models https://github.com/mozilla/kuma/commit/e4b7bfb88d7069d2e012ad156d9b33d81998af6c Merge pull request #1232 from groovecoder/remove-django-cache-893210 bug 893210 - don't cache wiki models
How is this going? Did the commit mentioned in comment 29 fix the issue?
Flags: needinfo?
Component: General → Editing
Flags: needinfo?
See Also: → 1488479
See Also: → 1200008
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.