How to Read Console Errors in Preview

If the preview on editor.clincoo.buzz is blank or a button does nothing, JavaScript usually stopped at the first error. The browser console is where that error is written, not the page itself.

Open the console

In Chrome or Edge, right-click the preview and choose Inspect. Open the Console tab. If the preview lives in an iframe, pick the preview frame in the console context selector so you see your site's logs, not the editor's.

Tell message types apart

A red error stops the script at that line. A yellow warning usually does not stop the page. A plain info line is only a note. Fix red errors first, top to bottom, because later errors are often fallout from the first one.

Read the file location

Click the file:line link on the right, for example app.js:42. That is the line the browser failed to run. is not defined means a variable or function name does not exist yet. Unexpected token usually means a quote, bracket, or comma was left open.

Copy the full message, file name, and line before you ask Clincoo's AI chat for help. Do not just write "error". After the fix, save the file and reload the preview so old errors are gone from the console.