Our self-hosted instance is broken after rebuilding with the latest commits (commits on Jun 10 and later since one of the builds on June 10 worked fine). We are on the tests-passed update branch. For non-admin (and non-moderator) users, it looks like all plugins are broken in a similar way. [image] For admin users (including mods), we see the same set of issue, plus a similar error with the admin module (below the retort plugin), which breaks early enough, that the app is completely broken. [image] The safe mode doesn’t help so much for admin users, as that doesn’t seem to disable the admin module anyway, and also this doesn’t seem to be a plugin specific problem. I’m assuming this is an issue with the latest commits. But if that’s not the case, would anyone have suggestions to help us resolve this issue ?

Hi @ja3, unfortunately this is a Cloudflare bug. You can find instructions to work around it here: [image] Resolving "SyntaxError: Unexpected identifier #..." caused by Cloudflare Auto Minify Sysadmins Cloudflare’s ‘Auto Minify’ feature will break recent versions of Discourse. In the browser console, you will see an error like: Uncaught SyntaxError: Unexpected identifier '#...' Cloudflare are aware of the issue, and have added this message to their dashboard: Note: Please note that this feature may not be fully compatible with certain newer CSS and JS language features, which could potentially affect the functionality of the site Unfortunately, despite this critical issue, the feature wi…

Thanks! That was it :smile: I had previously disabled Rocket loader to solve a similar issue. Should have known this might be similar. Anyway, I’m not seeing any noticeable difference in the load times after the change, given these are minified anyway as part of the Discourse build.

Hi, I’ve just hit the same problem .. but it was affecting some people all of the time and some people some of the time. I guess this was some sort of caching issue, however whereas turning off minification seemed to help, the issue quickly returned. I’ve now set the CloudFlare account in “development mode”, which bypasses the proxy, this seems to solve it (for now at least). I tried setting development mode previously and purging the cache, but it had no effect .. now it seems development mode AND disabling minification works. (which makes little sense to me) This is a very odd problem and is something that’s going to make me think twice before I click the upgrade button again. If anyone has any more info on this it would be much appreciated. (just to note; this is a new issue, nothing apart from updates has really changed in the last few months)

@oddjobz I didn’t need to use development mode. Purging cache for the site did the trick (to clear out the incorrectly minified files). One aspect to check is… do you have any configuration rules, which might be enabling/disabling minification. Or perhaps caching rules which does caching based on certain criteria.

Mmm, so minification + dev mode previously fixed the issue for both myself and other users. Last night the issue came back (I wasn’t able to check with anyone else) I went back to the CF console and minification was still disabled. Developer mode however had seemingly “automatically” turned itself off (!) I’m kinda guessing it has an expiry period (?) Anyway, developer mode + cache clear immediately re-fixed the issue for me. This isn’t sustainable for me so I’ve started looking at CF alternatives, does anyone have any recommendations or indeed any possible alternatives?

Looks like Fastly is the recommended CDN. I haven’t used it with discourse but they are generally very good. [image] Enable a CDN for your Discourse Self-Hosting So you’d like to use a CDN to speed up worldwide access to common assets on your Discourse forum? You might want to go all-in and Set up file and image uploads to S3 (see also Configure an S3 compatible object storage provider for uploads). If you want a CDN without the added complexity of S3 and having two CDNs, this is the guide for you. The CDN will reduce some load on your server by letting the CDN serve those assets so that the server doesn’t have to. It also can speed things up by deliver…

Ok, many thanks, I’ll take a look :slight_smile:

Latest commits in v3.3.0.beta3-dev seems to break Discourse

Product Support Self-hosting

oddjobz (Gareth) June 19, 2024, 9:33pm 8

Ok, many thanks, I’ll take a look

Topic		Replies	Views
Latest update requires cache purge in CloudFlare Self-hosting	70	7125	December 5, 2017
Resolving "SyntaxError: Unexpected identifier #..." caused by Cloudflare Auto Minify Sysadmins	0	706	June 10, 2024
Broken layout for admin login Product Support	5	268	September 10, 2024
403 errors, unresponsive buttons and admin menu disappearing Product Support	5	210	July 22, 2024
JS error after upgrade Product Support	7	1429	July 11, 2016

Latest commits in v3.3.0.beta3-dev seems to break Discourse

Related topics