Closed
Bug 1228524
Opened 9 years ago
Closed 9 years ago
After a revert, the page is not regenerated
Categories
(developer.mozilla.org Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1209025
People
(Reporter: teoli, Unassigned)
Details
(Keywords: in-triage, Whiteboard: [specification][type:bug][dupeme?])
What did you do? ================ 1. Reverted a page to a former revision. What happened? ============== Reverted in the history, not for the user. What should have happened? ========================== Cached copy invalidated, new one generated. Is there anything else we should know? ====================================== We forgot to do this most of the time, so we got complains in IRC: <Aryx> hi, why does https://developer.mozilla.org/en-US/Add-ons/Distribution$history not use the latest revision (the revert) but the second last?
Updated•9 years ago
|
Severity: normal → major
Keywords: in-triage
Whiteboard: [specification][type:bug] → [specification][type:bug][dupeme?]
Blocks: 1209025
Here is a live example (reverted on Oct 5) - https://developer.mozilla.org/en-US/docs/Web/HTML/DASH_Adaptive_Streaming_for_HTML_5_Video
Updated•9 years ago
|
Comment 3•8 years ago
|
||
Also see bug 839819, which may be a previously fixed incarnation of this bug.
Comment 4•8 years ago
|
||
So this seems to be a regression from bug 1174498 and https://github.com/mozilla/kuma/pull/3483
Assignee: nobody → jezdez
Updated•8 years ago
|
Assignee: jezdez → nobody
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•