Continuing the discussion from Admin panel not working after including buggy js in head/:
Would it be worth it to permanently exempt the admin section from any customizations?
AI-generated summary
The discussion revolves around the impact of customizations on the admin panel in Discourse. A user, Michael_Katrantzis, experienced an issue where adding a script to the <head> section broke the admin panel. calmh suggested exempting the admin section from customizations to prevent such issues. johnmuhl pointed out that customizations are disabled when accessing the admin panel directly via the URL. However, calmh and Michael_Katrantzis discovered that the <head> customization still applies, while other customizations do not. calmh found this behavior to be a weird special case. The discussion was eventually marked as a duplicate of a previous topic CSS Admin contents reloaded by calmh.
Yes probably…although it would be nice if its not done permanently and could include it back if necessary.
If you go http://discuss.example.com/admin manually (as opposed to through the menu) customizations are disabled.
I don’t think it does…
It does but I would have to go to admin/customize/css_html/2/head-tag edit and then save. Which still doesnt work
If I add some test tags to the </head> customization, those are certainly present when loading /admin directly as well.
Ah sorry you’re right head/ is present. All other customization (CSS and html) isnt.
Ah. Just my test then. 
That’s a weird special case? And why the difference depending on how it loads? Hidden referrer checking for … the win…?
Ah, this is a duplicate.
1 me gusta