In the past, you could override the .hbs template for and Discourse Route or Component by adding an identically named file in the templates/ directory of your theme and plugin. This was very powerful, but also came with significant maintainability issues. Therefore, we’ve been recommending against …

Is there a way to easily see which theme/plugin is triggering this admin notice? I looked through all of my themes and plugins and don’t see a templates/ directory in the root of their Git repositories for any of them.

[afbeelding] Jonah Aragon: don’t see a templates/ directory in the root It’s in /assets/javascripts/discourse or in /javascripts/discourse, not in the root.

The warning banner should show the name of the theme/plugin. It’ll also be printed in the browser developer console. If not, perhaps we have a problem with the deprecation - would you be able to share a link to an affected site?

Thank you. It did not show in the warning banner but it did show in the developer console, although not very clearly. [2025-03-05 at 10.00.40] Turned out to be this component. [afbeelding] DuckDuckGo Search Suggestions Theme component https://github.com/notriddle/disco…

Thanks @JonahAragon1 . The theme identification should be much clearer than that, so I’ll get that fixed up :eyes:

This change will fix the warning banner so it identifies themes more clearly: [SCR-20250306-otnz]

Have you find a solution to get back DDG as search suggestion? I’ve disabled the component for now.

No, I just decided to disable the form entirely. I don’t think anyone in my community uses it and I don’t really see the usefulness. I saw the component author proposed an update that requires a core change, so it’ll probably be working again soon. common/common.scss 940ae61c4 …

does it mean that the experimental user card will be introduced into core before this fully deprecates? I currently get this warning for this component GitHub - discourse/experimental-usercard

We’ve archived the experimental-usercard repository, and don’t intend to update the theme component any further. So I’m afraid you will need to disable it before template overrides are blocked in June 2025. We do hope to incorporate some of the experiment into core at some point, but don’t have a s…

Ondersteuning voor "template overrides" en mobiel-specifieke templates verwijderen

Ontwikkelaar

david (David Taylor) 6 juni 2025 om 13:45 16

Support for template overrides and mobile-specific templates has now been dropped.

Topic		Antwoorden	Weergaven
(not recommended) Overriding Discourse templates from a Theme or Plugin Developer Guides how-to	11	2598	26 juli 2024
Component template resolving pink banner Support	13	302	16 juli 2025
Modernizing inline script tags for templates & JS API Development dev-news	47	4388	25 maart 2026
How to track down `(id:discourse.component-template-resolving)` Support	6	127	22 oktober 2025
How to identify which theme/component/plugin needs an update? Support	1	134	15 juni 2025

Ondersteuning voor "template overrides" en mobiel-specifieke templates verwijderen

Gerelateerde topics