Could someone help me make sense of this error that I’m seeing in my logs? Discourse.Dialect is undefined

Is it possible that a plugin is causing this error even when it is disabled (i.e. it’s still in the app. yml but not activated in site settings)? If so, everything seems to point to the abbreviations and acronyms plugin: [imagen] Abbreviations and acronyms plugin Plugin …

Yes absolutely will mark it now Plugin needs to be removed and app rebuilt

[imagen] sam: Plugin needs to be removed and app rebuilt So is this true for plugins in general: they can cause errors even when deactivated?

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: [imagen] Reporting which plugin has caused the error Feature based on the errors …

[imagen] david: it is up to plugins to respect the “disabled” setting in their own programming Okay, I read that as: it depends how the plugin is programmed, so that it is possible to program it so that it has no effect whatsoever when it is disabled. I think that is a valuable design specifi…

[imagen] tophee: so that it is possible to program it so that it has no effect whatsoever when it is disabled. I’m not 100% sure that is true. Because some items get loaded automagically and just referencing a library that no longer exists will cause it to break, and that is before your setti…

[imagen] tophee: it has no effect whatsoever when it is disabled Yeah, ideally that would be the case. Sadly it’s not entirely realistic, especially for things like broken imports. (e.g. when discourse/lib/ajax was moved last year) Edit: @cpradio beat me to it

Yeah if we wanted easy peasy 100% robust disable Core would have to be able to issue a “restart” to all the services it is running Core would have to split up every plugin to have its own js file and have one js include per plugin (which may be desirable anyway cause it helps debugging a lot) (1)…

[imagen] tophee: everything seems to point to the abbreviations and acronyms plugin: To be fair, removing the acronyms and abbreviation did not stop those errors from occurring. So this plugin was either not causing any of them or it was not the only one doing so. Next try will be the affilia…

I can confirm that the affiliate plugin causes this error when core is upgraded but not the plugin. I dealt with this exact error earlier today. Updating the affiliate plugin solved it.

Error de Discourse.Dialect no definido

Soporte

sam (Sam Saffron) 13 Julio, 2017 11:30 2

Yeah it is ancient code we removed, upgrade all plugins, if it persists, remove one by one till it’s gone and report back with the culprit

Tema		Respuestas	Vistas
Reporting which plugin has caused the error Feature	5	1295	10 Julio 2017
Some users get javascript errors when trying to load our Discourse Support	1	3349	16 Enero 2023
Rebuilding caused a JavaScript error on load Support	8	1186	17 Junio 2016
Some official discourse plugins break after last update Bug	3	1418	31 Octubre 2016
Error when upgrading to the latest version due to third party plugin Self-hosting	3	699	2 Octubre 2019

Error de Discourse.Dialect no definido

Temas relacionados