# chromeNavControls not working with v7.0.0

**URL:** <https://discuss.elastic.co/t/chromenavcontrols-not-working-with-v7-0-0/180452>\
**Category:** Kibana\
**Created:** [May 9, 2019, 11:23pm UTC](https://discuss.elastic.co/t/chromenavcontrols-not-working-with-v7-0-0/180452 "2019-05-09T23:23:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joey\_Andres](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joey_andres/32/44982_2.png) [@Joey\_Andres](https://discuss.elastic.co/u/Joey_Andres)\
**Post date:** [May 9, 2019, 11:23pm UTC](https://discuss.elastic.co/t/chromenavcontrols-not-working-with-v7-0-0/180452/1 "2019-05-09T23:23:02Z")

</div>

I'm currently in the process of upgrading our custom Kibana from v6.2.4 to v7.0.0. It is a giant leap. I've already made most of our custom plugins except for a few things. One of which is the **chromeNavControls** of our plugins are all NOT showing up anymore on the sidebar. Our **uiExports** looks like:

```
uiExports: {
      styleSheetPaths: resolve(__dirname, 'public/theme/index.scss'),
      chromeNavControls: ['plugins/sonark/ui/nav_control'],
      hacks: ['plugins/sonark/ui/services'],
      savedObjectSchemas: {
        space: {
          isNamespaceAgnostic: true,
        },
      }
    }

```

Our **chromeNavControls** path points to:

```
import { chromeNavControlsRegistry } from 'ui/registry/chrome_nav_controls';

import '../../../common/polyfill';
import './../../management';

import '../decorator/response_handlers';
import '../decorator/response_error_handlers';

import '../directives/logout_button_sidebar/logout_button_sidebar';
import '../directives/kill_current_op_button_sidebar/kill_current_op_button_sidebar';

// Add button to the sidebar.
chromeNavControlsRegistry.register(function () {
  return {
    name: 'logout',
    order: 1000,
    template: '<logout-button-sidebar></logout-button-sidebar>'
  };
});

chromeNavControlsRegistry.register(function () {
  return {
    name: 'kill all user operation',
    order: 1000,
    template: '<kill-current-op-button-sidebar all-kibana-user-op="true"></kill-current-op-button-sidebar>'
  };
});

chromeNavControlsRegistry.register(function () {
  return {
    name: 'kill operation',
    order: 1000,
    template: '<kill-current-op-button-sidebar></kill-current-op-button-sidebar>'
  };
});

```

What could I possibly be doing wrong? I've been googling and looking for code usage, but I seem to be doing what is required. There is something I am missing.

---

<div class="post-metadata">

**Author:** ![joshdover](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joshdover/32/42020_2.png) [@joshdover](https://discuss.elastic.co/u/joshdover)\
**Post date:** [May 24, 2019, 6:01pm UTC](https://discuss.elastic.co/t/chromenavcontrols-not-working-with-v7-0-0/180452/2 "2019-05-24T18:01:30Z")

</div>

Hi there!

The new navigation uses a new registry for rendering nav controls which is a bit different. You'll now need to import the `chromeHeaderNavControlsRegistry` from `ui/registry/chrome_header_nav_controls`.

When you call register on this registry, instead of providing a template string, you'll actually need to provide a `render` function which will receive a HTMLElement to render into. You can use any rendering framework you'd like, here's an example of how to use React: [https://github.com/elastic/kibana/blob/master/x-pack/plugins/spaces/public/views/nav\_control/nav\_control.tsx#L97](https://github.com/elastic/kibana/blob/master/x-pack/plugins/spaces/public/views/nav_control/nav_control.tsx#L97)

You'll also need to provide a `side` property to tell the nav to render your control either on the left or right side of the screen. Let me know if that helps!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 21, 2019, 6:01pm UTC](https://discuss.elastic.co/t/chromenavcontrols-not-working-with-v7-0-0/180452/3 "2019-06-21T18:01:44Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.