david
2017 年7 月 13 日 12:03
6
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:
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…
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…
3 个赞