The original poster, Neel_Shah, is experiencing issues with their community site, where content is not showing up and the header is repeating multiple times after making changes to their theme.
Arkshine welcomes them and asks about the customizations made, suggesting the use of safe mode to disable them. However, Neel_Shah clarifies that the issue occurs only when admins log in.
JammyDodger suggests checking the /logs and browser console for errors, linking to a possible solution for the repeating header issue. Neel_Shah provides the logs and error screenshots, which Firepup650 and Moin review.
Neel_Shah mentions that the issue is browser-specific, with Firefox working fine but Chrome and Edge still experiencing problems. Firepup650 asks if they’ve tried the steps suggested by JammyDodger, which Neel_Shah confirms they have.
david points out that Cloudflare’s Auto Minify feature is still active, which is causing the issue, and advises clearing the cache. Neel_Shah provides an error screenshot, and david explains that Auto Minify is end-of-life and will be removed. He advises against using it, as it breaks Discourse’s code.
Suresh_Suthar mentions that disabling Auto Minify and cleaning the cache didn’t resolve the issue, and david suggests contacting Cloudflare support to resolve the issue with minified assets.
We have created a community site on self hosted platform and it worked perfectly but after we changed some portion in theme the site had become very strange, content is not showing up and the header is repeating atleast 10 times in a single page have attached the screenshot below. The portal looks fine but when we login the content is not shown.
Please see and suggest some steps to get the community portal working again.
Hey, welcome to Meta 
What customizations did you add?
Looking at the forum, it looks okay on my side:
On a side note, you can use the safe mode if customizations are blocking you. This way you can enter the admin panel again and disable them. 
The problem occurs when the admin login’s and see’s the content.
Apart from that with login to other person and without login to us it looks fine.
We have just added the banner image component in our theme nothing else.
I feel there might be some request limit issues sort of thing.
Are there any errors in your /logs or in the browser console that could provide more details?
Also, the repeating header sounds like this issue Resolving "SyntaxError: Unexpected identifier #..." caused by Cloudflare Auto Minify.
I have tried the safe mode also but there also, no content is shown.
Could you please help me out.
Are there any errors in the browser console?
I used Firefox now and it seems fine but in Chrome and Edge the error still prevails, hope any user of our community doesn’t face problem with this.
Did you try the steps in the topic Jammy suggested?
yes we had done the steps on Cloudflare.
But it is still not working properly
Is there any other alternative as we can’t do the Auto Minify step because our website would also get effected directly .
What’s your opinion on it’s effect on our main website?
Is there any other way to tackle the situation?
Cloudflare’s ‘Auto Minify’ system is end-of-life, and will be removed imminently:
It does not support modern JS syntaxes, and therefore breaks Discourse’s code before it reaches the browser.
So I’m afraid there’s nothing we can do on the Discourse side to fix this. Cloudflare’s Auto Minify feature is broken and no longer supported 
The general advice is that minification should be done ‘at build time’ instead. That’s what we do at Discourse, and it might already be the case for your main website as well.
Here’s a discussion about the feature’s deprecation on Cloudflare’s own community:
https://community.cloudflare.com/t/deprecating-auto-minify/655677
Hey,
We disable ‘Auto Minify’ & also Clean Cache but it still same issue also showing this error :
Uncaught (in promise) Error: There is no route named admin
The root cause is the errors further up, which say things like
Unexpected identifier ‘#s’
Your assets are still showing as minified. If you’ve definitely disabled the auto-minify feature, and you’ve totally purged the cache, then I’d suggest getting in touch with cloudflare support to see why it’s still messing with the assets:
