# Discourse.Dialect is undefined error **URL:** https://meta.discourse.org/t/discourse-dialect-is-undefined-error/66126 **Category:** Support **Created:** [July 13, 2017, 11:22am UTC](https://meta.discourse.org/t/discourse-dialect-is-undefined-error/66126 "2017-07-13T11:22:50Z") **Posts on this page:** 1 **Showing post:** 6
### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david) #### Post date: [July 13, 2017, 12:03pm UTC](https://meta.discourse.org/t/discourse-dialect-is-undefined-error/66126/6 "2017-07-13T12:03:22Z")
Yes, it is up to plugins to respect the “disabled” setting in their own programming - their javascript and ruby code is still loaded regardless. Some somewhat relavent discussion: > [@Reporting which plugin has caused the error](https://meta.discourse.org/t/reporting-which-plugin-has-caused-the-error/65925): > > based on the errors I get in the admin panel, I feel discourse can understand which plugin has caused the error. look at these errors e.g. Uncaught TypeError: Cannot read property 'inlineBetween' of undefined Url: https://padpors.com/assets/plugin-third-party-66034ae1bc6977c5ec45dcf7adb5f8f9799ab0ff261ffd958c9425a34a956605.js Line: 1 Col or this one: TypeError: Discourse.Dialect is undefined Url: https://padpors.com/assets/plugin-third-party-66034ae1bc6977c5ec45dcf7adb5f8f9799ab0ff261ffd958… > [@Reporting which plugin has caused the error](https://meta.discourse.org/t/reporting-which-plugin-has-caused-the-error/65925/2): > > This would be great. As a possibly related thing, it would be nice if one plugin throwing a JS exception didn’t break other plugins. I don’t know enough about how plugins are loaded to know whether that would be feasible though… --- _[View the full topic](https://meta.discourse.org/t/discourse-dialect-is-undefined-error/66126)._