Closed Bug 1034598 Opened 10 years ago Closed 4 years ago

Preview Pages with Macros Sometimes Fail Due to No Parent Page Path Access

Categories

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

x86
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: sole, Unassigned)

References

Details

(Whiteboard: [LOE:5])

Attachments

(1 file)

I'm getting this when editing https://developer.mozilla.org/en-US/docs/Web/API/Window.devicePixelRatio , and I have no clue why. Maybe because I entered some HTML in the content using the source editor?

I don't know, but this is a terrible user experience after having to wait for something like 45 seconds for the page to be created initially.
Mentor: application.error9
Assignee: eshepherd → nobody
Component: General → Editing
Product: Developer Documentation → Mozilla Developer Network
Severity: normal → major
Component: Editing → KumaScript
Summary: MEGA error when previewing an update → APIRef macro errors out when trying to preview a page that uses it
I can reproduce this both on the page shown in the screenshot and on other pages. Previewing pages that use the {{APIRef}} macro results in this error.
Assignee: nobody → dwalsh
Status: NEW → ASSIGNED
Right away I can identify a big problem:

var pageFolders = pageURL.split('/');
if (pageFolders) { ... }

String.prototype.split returns an array, even if empty, so that will always be true.

The larger issue, I believe, is that the full page path and such isn't used by our preview page code, still looking into it.
Ali:  How should we prioritize improvement of previews?  Is this a more or less important than other things?

This will take large effort.  Probably LOE5.
Flags: needinfo?(aspivak)
Whiteboard: [LOE:5]
Added Justin, so he can help figure out where in the stack of other bugs this belongs. 

It looks like this particular bug only affects pages using the {{APIRef}} macro, correct? Do we have any idea how many pages use that macro, and how important they are? We're doing a lot of work on the API dos and encouraging others to write them, so its important the API pages & macros work optimally. 

In general, from a content/community point of view, preview bugs are usually P2, in that we can live with them for a short while, but they do need to get fixed because they are frustrating to people writing, and could cause newer contributors not to return.
Flags: needinfo?(aspivak) → needinfo?(hoosteeno)
needinfo? myself to find out how many users this affects ...
Flags: needinfo?(hoosteeno) → needinfo?(lcrouch)
1168 documents use APIRef [1], 2,076 (0.01% of total) pageviews of preview-wiki-content since the bug was reported [2], and 36 of these errors in the last week. (New Relic)

[1] https://developer.mozilla.org/en-US/search?locale=*&kumascript_macros=APIRef
[2] https://www.google.com/analytics/web/?authuser=1#report/content-pages/a36116321w64965862p66726481/%3F_u.date00%3D20140704%26_u.date01%3D20140918%26explorer-table.filter%3Dpreview-wiki-content%26explorer-table.plotKeys%3D[]/
Flags: needinfo?(lcrouch)
Summary: APIRef macro errors out when trying to preview a page that uses it → Preview Pages with Macros Sometimes Fail Due to No Parent Page Path Access
Removing myself as assignee -- this isn't a kumascript bug, it's a preview page / processing bug.
Assignee: dwalsh → nobody
No assignee, updating the status.
Status: ASSIGNED → NEW
No assignee, updating the status.
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: 4 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.

Attachment

General

Created:
Updated:
Size: