Topic toolbar popup menu does not show

AI-generated summary

A user reports that the toolbar popup menu in their Discourse instance is not displaying, showing a loading bar instead, with a console error. After troubleshooting, the issue is identified as being caused by the deprecated “scrollable-post-content” theme component, which is no longer maintained. The user confirms this is the root cause, and another user acknowledges the issue and plans to update the component. Magie initially raised the problem, pfaffman suggested the theme component, and Arkshine confirmed and addressed the issue.

Dear Discourse community,
for an unknown reason we can not use the toolbar popup menu in our Discourse instance. I hope that maybe anybody has an idea what could be wrong.

I am talking about this menu when you create a new topic. This is a screenshot from meta.discourse.org:

However in our instance it now looks like this:
(This bar is also loading like the loading bar on top of the page.)

bug toolbar

Also there is an error in the console:

When I put a breakpoint on the first error in the console I get this:

Here is the code in the dev tools of my browser:


Things I tried already, but did not change anything:

  • Disable all Plugins
  • Disable all Theme Components
  • Remove all custom CSS
  • I tried to google and find if anybody has this problem.

The version of Discourse is 3.3.0.beta2-dev.

Any hints are appreciated!

IN one of your screenshots “scrollable post content” is causing problems. And it’s github repo says “This repository has been archived by the owner on Nov 16, 2021. It is now read-only.”

So maybe you didn’t really disable all of the theme components?

Hello, welcome to Meta :wave:

You can use safe mode to properly test whether the issue is from a theme component or a plugin.

As Jay suggests, the Scrollable Post Content might be the cause of this issue.

EDIT:

I confirm this is the cause. I tested on my local dev instance.


I will mark the component as broken. It requires some update!

Yes, you were right. This theme-component caused the issue. I must have missed it. I am sorry to have bothered you.

Thank you so much for the quick reply and extra sharp eyes!!! :yellow_heart: (I was already quite desperate after many hours of trouble shooting.)

No worry. I will see If I can update it later. :+1: