The discussion revolves around issues with theme components after updating to 3.5.0.beta2-dev. qingfeng1024 reports that numerous theme component functionalities have become nonoperative, including the Search Banner and Update option. Arkshine suggests checking the browser’s console for errors and asks if qingfeng1024 sees any errors as an admin. Arkshine later discovers that disabling the discourse-events plugin resolves the issue, and qingfeng1024 confirms that disabling the plugin fixes the problem. The issue is attributed to a severe bug in the latest version of the discourse-events plugin. Arkshine reports the problem, and sam closes the topic as it is related to a third-party plugin.
After the update( 3.5.0.beta2-dev), numerous theme component functionalities have become nonoperative, such as the “Search Banner,” and the “Update” option has vanished from the administrator settings interface.
There was once an option to update Discourse, which has since vanished. I am now at a loss as to where to perform the update, and can only do so by accessing the server directly.
There was once an option to update Discourse, which has since vanished. I am now at a loss as to where to perform the update, and can only do so by accessing the server directly.
Looking at the browser’s console, I see an error with the plugin Discourse Events:
Uncaught Error: Could not find module `discourse/mixins/singleton` imported from `discourse/plugins/discourse-events/discourse/models/provider`
at loader.js:247:1
at h (loader.js:258:1)
at u.findDeps (loader.js:168:1)
at h (loader.js:262:1)
at u.findDeps (loader.js:168:1)
at h (loader.js:262:1)
at requireModule (loader.js:24:1)
at y (app.js:170:18)
at b (app.js:193:19)
at app.js:156:29
at g.start (app.js:167:1)
at HTMLDocument.<anonymous> (start-app.js:5:7)
at discourse-boot.js:13:12
at discourse-boot.js:1:1
Can you try to disable it from the admin settings and reload the page to see if it helps?
Goodness gracious, you have pinpointed the issue with precision! After disabling the discourse-events plugin, everything returned to normal. It appears that this plugin has a severe bug in its latest version, which led to these malfunctions.
Given this is due to a third party plugin I am closing this topic, we only keep track of discourse official plugins and core in the Contribute > Bug category.