Closed Bug 967017 Opened 11 years ago Closed 10 years ago

Page move does not update the $json of the page

Categories

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

All
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: fs, Unassigned)

References

Details

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

What did you do?
================
1. Move a page
2. For example https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Properties_Index?redirectlocale=en-US&redirectslug=JavaScript_Properties_Index
3. Go to https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Properties_Index$json to see the json object of the page

What happened?
==============
Outdated info like "url": "/en-US/docs/JavaScript_Properties_Index" (which is the old URL) is shown.

What should have happened?
==========================
The document should get rebuild after the move and the info in $json should be up to date.

Is there anything else we should know?
======================================
Of course I can force a rebuild of the page using shift reload but it should happen automatically. See bug 839819 where the same happens when reverting a page.
Blocks: 971681
Commit pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/1355fe638d70a1d288bf04493ac9d89d90f0339c
Fix bug 967017: Re-render moved pages post-move.

This just does a brute-force re-render of every page affected by the
move, as the last part of the page-move task. This will address both
the issue in the bug (which is stale JSON -- that gets rebuilt during
the render) as well as any other stale data (it may also, as a side
effect, fix bug 973605 by rebuilding the list of translations).

Note that this doesn't clean up all stale-JSON issues; post-page-move,
for example, JSON may still be stale for the old URL.
Status: NEW → RESOLVED
Closed: 10 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.