Component template resolving pink banner

[patrickemin]

Hi, after updating today to the latest release I have the dreaded pink banner:

With that page of explanation: Component Template Resolving | Ember.js - Deprecations

I could not understand those explanations… Could someone explain to a rather non technician?

Thanks

Oh I realize the banner might not be pink for everyone…

[Lilly]

it’s because you are using 2 unofficial theme components that need to be modernized for templates and js api:

Discourse Category Headers theme component

This theme component provides a number of enhancements for the Discourse category header. The ‘standard’ Discourse category header is displayed at the top of each category page, above the navigation links and list of topics. It is normally only visible if a category logo image has been uploaded in the category settings. The header displays the logo and a short description of the category, taken from the first paragraph of the ‘About the… category’ topic. This theme component provides the foll…

Buttons for Scrolling to the Top/Bottom of Topics

Background Navigating my forum requires a lot of jumping between the top and bottom of topics. This theme component makes that easier by placing visible jump buttons on topic pages. How to install Summary Adds buttons that enable efficient jumping to the beginning/end of topics. Repository GitHub - ScottMastro/discourse-scroll-buttons Install Guide How to install a theme or theme component New to Discourse Theme…

you should disable them until they are fixed. see here:

@david

Using <script type='text/discourse-plugin> or <script type='text/x-handlebars'> in themes is now deprecated.

edit: keep in mind these are admin warnings - the components are not actually broken yet, but will inevitably break in a few months unless updated appropriately.

[Richie (Richie Rich)]

I’m getting the same warning banner after updating this morning too.

Much like @patrickemin screen shot, mine isn’t telling me the cause of the issue either

How can I find out which component / or components are causing this banner to appear?

[Moin]

Lilly shared a screenshot of the browser console. You can open it, for example, with Command+Option+J (Mac) or Control+Shift+J (Windows).

Your list seems quite long, but most of it is the same component:

• Category Previews
• Cookie Consent Banner
• Light

[merefield (Robert)]

or just F12 (Windows)

[Richie (Richie Rich)]

@Moin

the browser console

Ah-ha, thanks

I’m a bit worried by the Light warning.

If I think back to around seven years ago, isn’t Light the main core theme that was installed with my Discourse on day one?

[Moin]

Did you add any custom code to it?

[Richie (Richie Rich)]

Ignore that, I get the same warning on Dark too.

I’m guessing that could be caused by some additional CSS or JS that I’ve added

[Richie (Richie Rich)]

@Moin

Did you add any custom code to it?

Sorry, overlapping posts.

Yes - lots, it must be caused by that, I’ll check it out thanks

[david (David Taylor)]

I’ve just posted a dedicated topic for this deprecation, and I’ll update the warning banner to link there instead of taking people directly to Ember’s docs.

Handling the 'component-template-resolving' deprecation

As part of our preparation for the Ember 6 upgrade, we have now enabled warning banners for the “component template resolving” deprecation. [SCR-20250613-iunc] To find more information about the issue, open up the browser developer console (F12), and look for a message including [deprecation id: component-template-resolving] [SCR-20250613-iutc] This message will include the name of the affected component (in this case components/my-component), which should help you to isolate the problem t…

@Lilly

you should disable them until they are fixed. see here:

To expand on this: disabling them will remove the error banner, so that’s fine if you really need to hide it.

But it’s worth noting that deprecation notices don’t mean something is broken. It means that it will be broken in future, and we’re giving developers some advanced warning of that. It’s fine to keep using these things in the meantime.

On the <script> tag deprecation, we have a timeline here - everything will keep working until September.

[Lilly]

yea sorry about that, I should have been more clear that folks have a couple of months or so to fix these before they actually break.

[patrickemin]

Thanks everyone, that’s very clear!