CAKE_NICE is experiencing an issue with the theme editor in Discourse, where the custom CSS/HTML editor fails to load. The problem persists despite trying various troubleshooting steps, including clearing browser cache, disabling plugins, and using different browsers.
After further investigation, CAKE_NICE discovered that the issue is caused by the ace.js file failing to load, even in safe mode. pmusaraj suggested checking the browser’s JavaScript console for errors and verifying if the issue is specific to a particular theme.
CAKE_NICE found that the issue is related to incompatibility between the Air theme and Ace.js. However, pmusaraj was unable to reproduce the issue locally.
david suggested that the problem might be due to an incorrect file name, as the current version of Discourse uses a different file name instead of ace.js. He recommended verifying if the ./launcher rebuild app command completed successfully during the update process.
I’m encountering an issue with the theme editor on my Discourse site. When I try to edit the custom CSS/HTML under the “CSS” tab, the loading indicator keeps spinning, and the editor never loads. I have attached a screenshot to illustrate the problem.
Here is what I’ve tried so far:
Cleared my browser cache.
Disabled all non-official plugins.
Used different browsers and devices.
Verified that my admin account has the necessary permissions.
Despite these efforts, the issue persists. Has anyone else encountered this problem or have any suggestions on how to resolve it?
I’m encountering an issue where the ace.js file fails to load, even when running Discourse in safe mode. This issue prevents the theme editor from functioning properly. I’ve attached a screenshot showing the failed request.
Here is what I’ve tried so far:
Cleared browser cache and cookies.
Attempted to access the site using different browsers.
Checked server logs but found no clear indication of the issue.
Verified file permissions and paths on the server.
Rebuilt the app using ./launcher rebuild app.
Ensured all Discourse and plugin updates are installed.
Despite these efforts, the problem persists. Has anyone else encountered this issue or have any suggestions on how to resolve it?