Looking at toolbar.module
, the toolbar is added to the page via hook_page_top()
and the page_top area is output via html.html.twig
.
The following snippet is taken from html.html.twig
in core's stable9 theme:
...
<body{{ attributes }}>
{#
Keyboard navigation/accessibility link to main content section in
page.html.twig.
#}
<a href="#main-content" class="visually-hidden focusable">
{{ 'Skip to main content'|t }}
</a>
{# PAGE TOP IS OUTPUT HERE #}
{{ page_top }}
{{ page }}
{{ page_bottom }}
<js-bottom-placeholder token="{{ placeholder_token|raw }}">
</body>
...
Assuming you have the toolbar module enabled AND your theme (or base theme) is outputting page_top
in its html.html.twig
, then you should:
- Check the HTML source content for the toolbar div: per the twig above, it'll likely be directly below the
#main-content
link.
- Check for any errors in console: the contents of the toolbar are loaded via JS so it may be that toolbar is on the page, but a JS error is preventing it from rendering its contents.
- Check that the toolbar isn't simply being rendered underneath other content: i.e. a z-index issue.
- Check for any theme code that may be tampering with the contents of page_top: Make sure anything implementing
hook_page_top()
isn't overriding the contents of $page_top
, specifically $page_top['toolbar']
, make sure it's not doing something like $page_top = [etc...]