How to track down `(id:discourse.component-template-resolving)`

AI-generated summary

The discussion revolves around tracking down the source of a deprecation warning related to component-template-resolving in a hosted Discourse site. ganncamp seeks help identifying which theme or plugin is causing the warning. jahan_gagan explains that this is a deprecation issue, not an update problem, and provides steps to identify the culprit using safe mode. Moin suggests the issue might be related to the Unanswered Filter component and shares how to find the component name in the browser console. ganncamp confirms this and thanks Moin for the clue. Moin clarifies how they identified the component name, and ganncamp expresses gratitude for the guidance.

We’re on a hosted site and have been seeing

[Admin Notice] One of your themes or plugins contains code which needs updating. (id:discourse.component-template-resolving) (learn more)

For a week or so now.

How do I track down which theme or plugin this is from? Most of our plugins are preinstalled, the rest from Discourse itself.

Nowhere in Themes, Components or Plugins do I see an indication that any single thing needs updating

The answer to this notice is explained in the “Learn more” link included in the message — it leads to the official Meta topic on handling the component-template-resolving deprecation.

In short, this isn’t an update problem but a deprecation warning. It means one of your themes or plugins still uses old component-template code. The article explains how to identify which one.

You can also use safe mode to narrow it down:

  1. Go to /safe-mode.
  2. Disable all theme components, then reload the site.
  • If the notice disappears, one of those components is the cause.
  1. If it stays, re-enable themes and instead disable all plugins to test those.
  2. Re-enable items one by one until the notice returns — that’s your culprit.

Once you know which plugin or theme causes it, you can update or temporarily disable it until the author releases a fix.

I think the warning is related to a version of the Unanswered Filter component.
image
Do you use a custom version of that component, or did you install a different branch?

Thanks @Moin! That was the clue I needed. My partner in crime has a very vague memory of not being able to install the vanilla component when he did it several years ago and having to do something special around this.

But could you share what about the message pointed you to the Unanswered filter? Because I’m still at a loss for that.

I am not sure I understood your question

The topic linked in the admin notice you shared says that the component name can be found in the browser console

And that’s where I found the name

So that’s where I was supposed to be looking. Thanks!