# Inconsistent body class for /admin paths? (disabling top navigation)

**URL:** <https://meta.discourse.org/t/inconsistent-body-class-for-admin-paths-disabling-top-navigation/60694>\
**Category:** Product Support\
**Created:** [4월 9, 2017, 10:44오후 UTC](https://meta.discourse.org/t/inconsistent-body-class-for-admin-paths-disabling-top-navigation/60694 "2017-04-09T22:44:22Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)\
**Post date:** [4월 10, 2017, 3:16오후 UTC](https://meta.discourse.org/t/inconsistent-body-class-for-admin-paths-disabling-top-navigation/60694/6 "2017-04-10T15:16:13Z")

</div>

> [@sam](#):
>
> The problem is that people would mess up a customization and then have no idea how to bring site back into operation.

Makes complete sense. What I would suggest, though is to make this behaviour transparent so that admins understand that they must look at the front end to verify their customizations and don’t waste their time trying to figure out what is going wrong with their code. Here would be a good place for this:

 ![](https://global.discourse-cdn.com/meta/original/3X/8/8/8873d13b84cebf71001f4f81987261dc3f086ce8.png)  
Add something like "For security reasons, most customizations are not applied to the admin section of the site.

---

_[View the full topic](https://meta.discourse.org/t/inconsistent-body-class-for-admin-paths-disabling-top-navigation/60694)._