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.
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.
I think the warning is related to a version of the Unanswered Filter component.
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.