Closed
Bug 782114
Opened 13 years ago
Closed 13 years ago
Automatically regenerate pages using a modified kuma template
Categories
(developer.mozilla.org Graveyard :: Editing, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 772704
People
(Reporter: teoli, Unassigned)
Details
When we modify a template, we have to manually do a shift-reload to see the change taken into account by the pages using this template.
This is annoying for three reasons:
1) We don't have the list of which pages use it (that's bug 773855 )
2) There may be 100s of them... Updating manually is not practical.
3) Some kumascript are used as a simple DB, meaning that some articles will be outdated and un-synchronized (read: incoherent info provided to the user).
Note: no need to have them updated synchronously when we check-in a change in the template. There is no problem having to wait up to 10 minutes to have all pages updated.
Priority: though not a P0, I believe this one is quite important (P1 or at least P2). Little by little, more pages are not up-to-date.
To mitigate the problem we could regenerate all pages periodically (once a week?), like we did right after the launch. Doing this would push the priority from P1 to P2 or even P3.
Comment 1•13 years ago
|
||
I think this is already filed as bug 772704
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•13 years ago
|
Version: Kuma → unspecified
| Assignee | ||
Updated•13 years ago
|
Component: Docs Platform → Editing
Updated•6 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
•