I’m now on the latest commit level (105634435f). I upgrade Discourse about every week or so. Usually there are no issues at all. But now multiple theme components failed to load. With fail to load I mean the components do not show up anymore. The log feature in the admin panel does not show anything strange that I can relate to this issue. Many of those errors seem incidental, and already occur over a longer period of time. Like rare MimeType errors and timeouts for DNS to Google, again, they occur rarely. These plugins fail to load after upgrading: DiscoTOC discourse gifs Discourse Jitsi Hamburger Theme Selector Nav Links Component Tag Icons The only ones that do work are: Discourse Kanban Easy Footer If more info is needed (I suppose there is), then I’m happy to provide it to you, please instruct. This post is more as a shoutout that something is wrong, and it’s probably a recent change. Sorry for the lack of info…

In addition, non-strict Javascript variable definitions like: xxx = 330; instead of var xxx = 330; will lead to JS “undefined variable” errors. We had to change all these in our scripts.

Yes, there is an issue with some theme components, we are working on a fix.

@pmusaraj thank you so much. Good luck

Do you know why errors are thrown for non-strict defined JS variables in components? Is this a post-processing error? Did anything change here?

The change that caused this problems was reverted an hour ago, please update to latest if your site was affected.

To add to what Falco said, the change will be added back in the next few days, but before I add it back I’ll make sure all our official themes/components are compatible with the change. So if you start seeing the problem with official themes/components again, updating them should fix the problem. I’ll also make a post to explain how to make themes/components compatible for people who have custom/private components on their sites. My apologies for the inconvenience today.

[imagem] Osama: I’ll also make a post to explain how to make themes/components compatible for people who have custom/private components on their sites. one of our themes (a banner theme) has been completely overwritten to its initial format and all of the changes we had made, has gone. there was no update for the theme since 2018. would we be able to revert the changes?

Hmm that’s really weird. Have you updated your instance again to include Revert "FEATURE: Introduce theme/component QUnit tests (#12517)" (#12… · discourse/discourse@2b9ab3a · GitHub? Can you elaborate a little more on what you mean by ‘initial format’? Do you mean you had local changes to the JS/CSS of the theme but now all those changes are gone?

Does this also explain the problem with JS variable definitions? If so, how?

I don’t think this issue has to do with this reverted feature, I had the same case with a component a few weeks ago, probably around the fork indicator feature (which concern plugins so :roll_eyes: probably irrelevant too, but I just had to fork the component to modify things).

Alteração futura em componentes de tema 'use strict' - temas quebram após atualizar o Discourse - #19 de Osama - Suporte ao Produto

Tópico		Respostas	Visualizações	Atividade
Upcoming core changes that may break some themes/components (April 12) Announcements	5	2892	12 de Abril de 2021
If you want to edit this theme, out of luck? Product Support	1	546	13 de Junho de 2021
Blank website after update Product Support	14	1925	26 de Agosto de 2020
Theme component update issue Development	7	451	7 de Junho de 2024
One of your themes or plugins needs updating for compatibility with upcoming Discourse core changes Development	2	319	6 de Julho de 2024