How to check for JS errors

  1. Home
  2. Knowledge Base
  3. Documentation
  4. Troubleshooting
  5. How to check for JS errors

Major parts of our plugins are built in JavaScript. When something is not working as expected, it’s always a good start to check the current page for JavaScript errors. Here’s how:

The JS console

To see JavaScript errors you first need to open your browsers JS console and then reload the current page. The console is usually displayed at the bottom of the browser window.

  • How can I access the JS Console?

    Every browser has a JavaScript console. Usually, you can open this console with a simple keyboard shortcut:

    – Chrome: Press ++J (on a Mac) or Ctrl+Shift+J (on Windows).
    – Firefox: Press ++K (on a Mac) or Ctrl+Shift+K (on Windows).
    – For other browsers or more details, read the official guide on

The console looks a little different in all browsers, but the general layout is always the same: You have a tab bar with several registers to choose from – look for the register that says “Console” and open that register.


JS Console in Google Chrome (dark mode)
JS Console in Firefox (German)

Find Errors

Once you see the Console, reload the page (F5 or Cmd+R) and look for the text inside the Console. In most cases you will see many lines of text appear – that’s normal. Keep an eye open for red warning icons or red text, as those indicate errors!

Look for errors, not warnings:

You can safely ignore the normal and yellow text lines, as those are details that are intended for developers but do not impact the plugin behavior.

Not all errors are relevant

Often you will see red entries that look similar to this:

Missing images will trigger 404 errors in the Console – those are irrelevant

Any “GET …/some.jpg 404” tell you that an image is missing. Those errors have no impact on the plugin behavior.
We’ve never seen an issue that was caused by a 404 error, but if you are uncertain then get in touch, and we’ll double-check your console output.

Found an error?

If you find any error that looks relevant, it’s best to take a screenshot of it and submit it via our Support Form. When there are multiple errors then take a screenshot of all of them – usually, the first error is the one we need to debug the issue.

Was this article helpful?

Related Articles