---
title: KumaScript 에러 해결하기
slug: MDN/Tools/KumaScript/Troubleshooting
translation_of: MDN/Tools/KumaScript/Troubleshooting
---
<div>{{MDNSidebar}}</div>

<div class="summary">
<p><a href="/en-US/docs/MDN/Kuma/Introduction_to_KumaScript"> </a>빨갛고 무서운 상자 안에 든 <a href="/en-US/docs/MDN/Kuma/Introduction_to_KumaScript">KumaScript</a> 에러는 매우 보기 불편합니다. 하지만 다행히도, MDN 계정이 있다면 누구나 문서를 편집해 이 문제를 해결할 수 있어요. When a page has an error it gets added to the list of <a href="/docs/with-errors">documents with errors</a>.  Site editors go through this list regularly to find and fix errors. This article details the four types of KumaScript error, and some steps you can take to fix them.</p>
</div>

<h2 id="DocumentParsingError">DocumentParsingError</h2>

<p><code>DocumentParsingError</code> errors appear when KumaScript has trouble understanding something in the document itself. The most common cause is a syntax error in a <a href="/en-US/docs/MDN/Contribute/Content/Macros">macro</a>.</p>

<p>Check for:</p>

<dl>
 <dt>Use of curly braces without intending to call a macro.</dt>
 <dd>If you need to write  \{ in a document without calling a macro you can escape it with a \ like this: <code>\\{</code></dd>
 <dt>Use of a special character in a macro parameter.</dt>
 <dd>If you need to use a " or a \  inside of a macro parameter they can be escaped with a \ like this: <code>\\</code> or <code>\"</code></dd>
 <dt>Missing commas between macro parameters.</dt>
 <dd>Macro parameters need to be delimited by a comma (,) but not at the end of the list of parameters; for example <code>\{\{anch("top", "Back to top")}}</code>.</dd>
 <dt>HTML tags appearing inside a macro call</dt>
 <dd>If you apply styling to a macro, it will often break because, for example, a <code>&lt;/code&gt;</code> tag may have appeared inside the macro code in the source code. Check the source view to see what's there, and remove any unnecessary styling.</dd>
</dl>

<ul>
</ul>

<h2 id="TemplateLoadingError">TemplateLoadingError</h2>

<p><code>TemplateLoadingError</code> errors appear when KumaScript has trouble finding which <a href="/en-US/docs/MDN/Contribute/Content/Macros">macro</a> to include on a page.</p>

<p>Check for:</p>

<dl>
 <dt>Misspelling of macro names or renamed macros.</dt>
 <dd>You can look at the list of known macros in the <a href="https://github.com/mdn/kumascript/tree/master/macros">Github repo</a>.</dd>
</dl>

<div class="note">
<p><strong>Tip:</strong> You can make it quick and easy to jump to a specific macro by adding a <a href="http://kb.mozillazine.org/Using_keyword_searches">search keyword</a> to Firefox. See {{SectionOnPage("/en-US/docs/MDN/Contribute/Tools/KumaScript", "Using search keywords to open template pages")}} for a step-by-step guide to creating the search keyword for this.</p>
</div>

<h2 id="TemplateExecutionError">TemplateExecutionError</h2>

<p><code>TemplateExecutionError</code> errors appear when KumaScript encounters an error in the macro. These errors can only be fixed by admin users and need to be reported as bugs.</p>

<p>Before reporting an error check to see that it hasn't already been fixed. You can do this by forcing KumaScript to give you a fresh copy of the page by holding down <kbd>Shift</kbd> while you refresh the page (<kbd>Shift</kbd> + <kbd>Ctrl</kbd> + <kbd>R</kbd> on Windows/Linux, <kbd>Shift</kbd> + <kbd>Cmd</kbd> + <kbd>R</kbd> on Mac).</p>

<p>If the error persists, <a href="https://bugzilla.mozilla.org/form.doc">report a bug</a>, including the URL of the page and the text of the error.</p>

<h2 id="Error_Unknown">Error &amp; Unknown</h2>

<p>This is the category errors end up in if they are not one of the other kinds of error.</p>

<p>Check for fixes and report persistent bugs like described under <a href="#TemplateExecutionError">TemplateExecutionError</a>.</p>