# Ensure admin isn't messed up by customizations

**URL:** <https://meta.discourse.org/t/ensure-admin-isnt-messed-up-by-customizations/33747>\
**Category:** Feature\
**Created:** [September 25, 2015, 1:56pm UTC](https://meta.discourse.org/t/ensure-admin-isnt-messed-up-by-customizations/33747 "2015-09-25T13:56:19Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![calmh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/calmh/32/115466_2.png) [@calmh](https://meta.discourse.org/u/calmh)\
**Post date:** [September 25, 2015, 1:56pm UTC](https://meta.discourse.org/t/ensure-admin-isnt-messed-up-by-customizations/33747/1 "2015-09-25T13:56:19Z")

</div>

Continuing the discussion from [Admin panel not working after including buggy js in head/](https://meta.discourse.org/t/admin-panel-not-working-after-including-buggy-js-in-head/33746):

> [@Admin panel not working after including buggy js in head/](https://meta.discourse.org/t/admin-panel-not-working-after-including-buggy-js-in-head/33746/1):
>
> The above was added in the head/ section and not only it didnt work but now I cannot edit the head/ again or rather save it or complete any actions in the backend admin panel.

Would it be worth it to permanently exempt the admin section from _any_ customizations?

---

_[View the full topic](https://meta.discourse.org/t/ensure-admin-isnt-messed-up-by-customizations/33747)._