# 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:** 5

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [4월 10, 2017, 1:29오후 UTC](https://meta.discourse.org/t/inconsistent-body-class-for-admin-paths-disabling-top-navigation/60694/5 "2017-04-10T13:29:31Z")

</div>

> [@tophee](#):
>
> when I access /admin directly (without having loaded the forum previously in the same tab) the top-navigation bar doesn’t load so that I see only the default discourse header like here on meta.

For a very very long time, we disabled all customizations on first load for `/admin` path. Now that we have `safe-mode` route I am not sure this is as required. We may change this.

The problem is that people would mess up a customization and then have no idea how to bring site back into operation.

---

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