Hi, after updating today to the latest release I have the dreaded :face_with_raised_eyebrow: pink banner: [The image contains a warning about themes, topics, or extensions that might violate community guidelines or terms of use in Element, with a link to further information. (Captioned by AI)] 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? :grin: Thanks Oh I realize the banner might not be pink for everyone… :upside_down_face:

it’s because you are using 2 unofficial theme components that need to be modernized for templates and js api: [Screenshot 2025-06-12 at 8.38.59 PM] [image] Discourse Category Headers theme component 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… [image] Buttons for Scrolling to the Top/Bottom of Topics Theme component 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 information_source Summary Adds buttons that enable efficient jumping to the beginning/end of topics. hammer_and_wrench Repository GitHub - ScottMastro/discourse-jump-buttons · GitHub question Install Guide How to install a theme or theme component open_book New to Discourse … you should disable them until they are fixed. see here: [image]Modernizing inline script tags for templates & JS API Using or 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.

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 :confused: [Screenshot 2025-06-13 at 08.05.14] How can I find out which component / or components are causing this banner to appear? :thinking:

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 [The image contains deprecation notices from Meta Discourse regarding specific JavaScript code changes, highlighting the use of deprecated methods and instructing to move the code to dedicated JavaScript files with provided deprecation IDs. (Captioned by AI)]

[image] Moin: the browser console Ah-ha, thanks :smiley: 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? :thinking: [Screenshot 2025-06-13 at 08.34.28]

Did you add any custom code to it?

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 :grimacing:

[image] 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 :smiley:

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. [image] Handling the 'component-template-resolving' deprecation Development 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… [image] 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 tag deprecation, we have a timeline here - everything will keep working until September.

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.

Component template resolving pink banner

Product Support

patrickemin (Patrick EMIN) June 13, 2025, 2:00pm 12

Thanks everyone, that’s very clear!

Topic		Replies	Views
How to find item needing update? Product Support	3	281	June 16, 2025
How to identify which theme/component/plugin needs an update? Product Support	1	243	June 15, 2025
How to track down `(id:discourse.component-template-resolving)` Product Support	5	279	October 22, 2025
Handling the 'component-template-resolving' deprecation Development dev-news	2	1187	June 13, 2025
Theme component update issue Development	7	448	June 7, 2024

Component template resolving pink banner

Related topics