“템플릿 오버라이드” 및 모바일 전용 템플릿 지원 제거

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 template overrides over the last few years, and officially deprecated them in November 2024. Nowadays, the better solution is to use Wrapper Plugin Outlets to render content in place of core content.

This month (March 2025) we will be introducing an admin warning banner for template overrides, and plan to fully remove support before the end of Q2.

Timeline

(estimated dates - subject to change)

  • :white_check_mark: November 2024 - deprecation introduced

  • :white_check_mark: March 2025 - admin warning banner enabled

  • :white_check_mark: June 2025 - removal of functionality (targetting w/c 2nd June)

Upgrading themes / plugins

Theme and plugin developers should refer to the Plugin Outlet guide to learn more about wrapper plugin outlets. Feel free to open PRs or Development topics if you’d like to request a new extension point for your use-case.

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.

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.

Turned out to be this component.

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:

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.

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 · GitHub

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 specific timeline on that. The user-card is a very heavily-customized part of the UI, so landing large changes to it will require careful planning and changes across the ecosystem.

Everything is on-track for this goal, so we intend to drop support for template overrides in the week-commencing 2nd June.

Since this will happen before the 3.5 stable release, we have backported the admin warning banner to stable 3.4, so that communities on stable get a decent amount of warning before their update to 3.5.

(cc @RGJ, since I know you host many forums on stable)

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

나도 지금 이 모호한 오류(기본 테마를 가리키는 것)가 나옵니다. 콘솔을 확인하라는 힌트가 도움이 되었어요. 이건 우리 커스텀 CSS에 있는 것 같은데, 이 포럼을 맡은 지 얼마 안 되어서 좀 더 파봐야 할 것 같아요. 언제부터 이게 깨지나요? 미리 준비할 수 있도록 시간 계획을 세우고 싶어서요.


Screenshot 2025-07-26 at 16.16.52

Discourse 코어의 최신 버전에서 템플릿 오버라이드가 제거되었으므로, 아마도 구버전을 실행하고 계신 것 같습니다. 다음에 최신 버전으로 업데이트하면 오버라이드가 더 이상 작동하지 않을 것입니다.

기본 테마에 <script type="text/x/handlebars">와 같은 코드가 포함되어 있을 가능성이 높으며, 이를 제거해야 합니다.

음. 재밌네. 우리 데브옵스 팀이 3.4.6으로 업데이트한 후에야 이 배너가 보이기 시작했어. 커스텀 오버라이드는 여전히 렌더링되고 있고 (위치와 외관에 대한 네 말은 맞아). chatgpt가 이 오버라이드가 하는 일을 오해하고 있는 건가 봐. 아직 이 모든 걸 파악하는 중이지

다 해결됐어. 경고 메시지는 사라졌고 스타일은 그대로 유지됐어. 와~