Closed Bug 851210 Opened 11 years ago Closed 11 years ago

Manually restore content and revision history of Jsval article

Categories

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

All
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: openjck, Unassigned)

Details

(Whiteboard: [specification][type:bug])

What did you do?
================
1. Load https://developer.mozilla.org/en-US/docs/SpiderMonkey/JSAPI_Reference/Jsval

What happened?
==============
The history page shows no entries before March 13, despite many revisions before that time. The only revisions that do exist are redirects. All of the content for this page -- past and present -- is gone.

What should have happened?
==========================
Revision history should be intact (not exactly sure when the first edit was, but certainly before March 13). The current content of the page should also be intact.

Is there anything else we should know?
======================================
Take a look at bug 851199 for some background.

When I say "intact" above, I do not necessarily mean on the Jsval page. Considering the page was moved, I guess this history and current content should appear under the new slug that was chosen during page move.

This bug is for manually restoring this content now. Bug 851199 is about fixing the underlying problem longer-term.
Any way to prioritize this?  I have more changes I want to make to that page (or to the new location it was being moved to).  Also, right now, with the page-move-loss, there's no documentation *at all* for jsval/JS::Value.  This is the fundamental data type for values in the SpiderMonkey API, and it shows up everywhere, so this is really bad.

Could someone at least say what the deadline for this is, to know whether I should just overwrite the current contents with my saved-offline backup in the meantime?  I'm hesitant to do it now because then we'd have to reconcile the old history and the new changes, and it's not worth the trouble if I know this will get fixed soon enough.
:groovecoder mentioned this could wait until Monday. I'll take a look at what I can find now.
grepping in backup files is a pain, I'm restoring the developer_mozilla_org database  (backup from 3/11) now so I can run queries to find the right data.
Hey Jeff.

This is our highest priority right now. I estimate that this will be fixed by tomorrow (Tuesday) evening. Please open a separate bug for any other problems.
Sounds good.
I restored the page at https://developer.mozilla.org/en-US/docs/SpiderMonkey/JSAPI_Reference/jsval from the backup. This is before the move, and is from the 3/11 backup.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.