Title: &quot;Uncaught SyntaxError: Unexpected token
Last modified: August 21, 2016

---

# "Uncaught SyntaxError: Unexpected token

 *  [Yaniv](https://wordpress.org/support/users/yaniv691/)
 * (@yaniv691)
 * [11 years, 10 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-4/)
 * Hi,
 * I’m using Disqus on our company blog, which works great. I have a small issue(
   error) in the browser console caused by Disqus:
 * `Uncaught SyntaxError: Unexpected token <`
 * This is an example URL:
    [http://www.ravellosystems.com/blog/continuous-integration-with-jenkins/](http://www.ravellosystems.com/blog/continuous-integration-with-jenkins/)
 * When I disable Disqus, the error is gone.
    How can I fix this? Will this be fixed
   in the next update?
 * * Note: I’m using WP Super Cache on the blog, but I don’t think this has anything
   to do with the JS error.
 * Thanks,
    Yaniv
 * [https://wordpress.org/plugins/disqus-comment-system/](https://wordpress.org/plugins/disqus-comment-system/)

Viewing 6 replies - 1 through 6 (of 6 total)

 *  [Lara Schenck](https://wordpress.org/support/users/notlaura/)
 * (@notlaura)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-4/#post-5139715)
 * I’m having the same problem. Did you figure anything out?
 *  Plugin Contributor [ryanv12](https://wordpress.org/support/users/ryanv12/)
 * (@ryanv12)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-4/#post-5139716)
 * I’m not seeing this error at the moment, did you find a way to fix it?
 *  [Lara Schenck](https://wordpress.org/support/users/notlaura/)
 * (@notlaura)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-4/#post-5139717)
 * Oh, I did! I believe it was from wpautop which happens even when using the ‘text’
   tab of the WYSIWYG editor. I was using ACF and used a text area field instead
   of the WYSIWYG to avoid the issue. In other words, it seems that wrapping the
   embed code in a `<p>` causes the error.
 *  [Lara Schenck](https://wordpress.org/support/users/notlaura/)
 * (@notlaura)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-4/#post-5139718)
 * Also – that’s using the raw embed code, not the plugin.
 *  Plugin Contributor [ryanv12](https://wordpress.org/support/users/ryanv12/)
 * (@ryanv12)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-4/#post-5139719)
 * Was the raw embed code placed inside the post editor? It would make sense then
   because those editors usually escape certain characters and break the syntax 
   of the script.
 *  [Lara Schenck](https://wordpress.org/support/users/notlaura/)
 * (@notlaura)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-4/#post-5139720)
 * Essentially, yes – I was using a WYSIWYG custom field through Advanced Custom
   Fields, but I’d imagine it acts the same way. `wpautop` isn’t run on the text
   area field type, so I think that’s what fixed it.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘"Uncaught SyntaxError: Unexpected token’ is closed to new replies.

 * ![](https://ps.w.org/disqus-comment-system/assets/icon.svg?rev=1636350)
 * [Disqus Comment System](https://wordpress.org/plugins/disqus-comment-system/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/disqus-comment-system/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/disqus-comment-system/)
 * [Active Topics](https://wordpress.org/support/plugin/disqus-comment-system/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/disqus-comment-system/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/disqus-comment-system/reviews/)

 * 6 replies
 * 3 participants
 * Last reply from: [Lara Schenck](https://wordpress.org/support/users/notlaura/)
 * Last activity: [11 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-4/#post-5139720)
 * Status: not resolved