1200008 - Scripting error - TemplateExecutionError - ApiRef

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: Wiki pages, defect)

Description

[ksm19861]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Safari/537.36

Steps to reproduce:

I translated a document and saved it.
https://developer.mozilla.org/ko/docs/Web/API/Document


Actual results:

The page continuously showed an error message

Error type : TemplateExecutionError
In macro : ApiRef
Parsing macro : ApiReg([u'dom])  Full text of error : ......

At first I thought there might have been an error in my script, but it seems like it has another problem. I tried to update and fix it, but it didn't change.

Comment 1

[Jean-Yves Perrier [:teoli]]

That's strange. The macro is correct but:

the version displayed is not the last of history. So you have (and I have) corrected the initial problem (a missing brace) but this version is not displayed.

What is worrying is when clicking EDIT, the old version is displayed (with a draft-has-been-saved banner).

Ni/ Luke as I have never seen this double symptom.

Comment 2

[Justin Crawford [:hoosteeno] [:jcrawford]]

Marking as major because it may be a data problem.

Comment 3

[Luke Crouch [:groovecoder]]

Catching up on needinfo? ... every revision of the document since https://developer.mozilla.org/ko/docs/Web/API/Document$revision/908129 has included the proper ApiRef() call.

The rendered page can show stale content because KumaScript gets content from memcache. The EDIT page always shows the content from database.

A force-refresh will clear it up, but this document is a "deferred rendering" document, so the force-refresh may take a while.

:teoli - does that make sense?

Comment 4

[John Whitlock [:jwhitlock]]

https://developer.mozilla.org/ko/docs/Web/API/Document renders correctly now.

The issues with seeing an old revision when editing is strange, but should get a new bug if it still occurs. The editing system has had many changes over three years.

The stale document issue is tracked in bug 893210. Removing the cache is tracked in bug 1488479.