Using <script type='text/discourse-plugin> or <script type='text/x-handlebars'> in themes is now deprecated. Any use of these tags in themes should be updated according to the instructions below. Regular <script> and <script type='text/javascript'> are unaffected by this change. Timeline These are…

Maybe a very dumb question, but I have a very very simple theme component that I put directly into the admin console under <head>: <script type="text/x-handlebars" data-template-name="/connectors/top-notices/whos-online-below-site-header"> {{whos-online}} </script> If I’m following this post corre…

There is the JS tab now, so you can probably use api.renderInOutlet now.

[이미지] NateDhaliwal: here is the JS tab now, so you can probably use api.renderInOutlet now. [이미지] david: If you develop your theme via the admin panel interface, copy the code out of the <script>, and move it into the JS tab (where it says // your code here). Ah, I didn’t see that this…

Thank you for this post! May be a very basic question I believe: Since we do not have a sandbox, I need to be sure before I proceed. I have to update a theme affected so am I correct if say that all the code related to “Script” from “head” tab need to be moved into the JS tab as illustrated below…

Almost, but not quite. You’d want to remove the script tags, and change the imports to something like: import { ajax } from "discourse/lib/ajax"; Then, paste all this in the JS tab, inside: [이미지] david: export default apiInitializer((api) => { // Your code here });

Our Discourse site (hosted by Discourse) is currently generating the following error bar (which is what led me to this thread): [Screenshot 2025-07-14 at 10.40.31 AM] I’m not aware that we’ve done any cutomization of the ‘Light’ theme of our own, and looking at its admin page, am not seeing anyth…

You will need to take action to resolve this - it won’t go away on its own. I took a quick look at your site in chrome dev tools, and it looks like the relevent code is related to adding the ‘chapel’ language to highlightjs. [SCR-20250714-qmbq] If you visit your ‘Light’ theme, and hit ‘edit code…

Thanks @david ! I’d forgotten that we’d done some customizations to get Chapel highlighting and am not sure I would’ve gotten there on my own from the error banner, so appreciate the assistance and pointers. -Brad

I have a simple .html file: <script type='text/x-handlebars' data-template-name='/connectors/below-site-header/oprs-top-container'> <div id='WW_T_D_1' class='oprs-top-leaderboard'></div> </script> I’m kind of confused with different ways to do this migration. Appreciate if someone explains wha…

Just renderInOutlet to the connector import { apiInitializer } from "discourse/lib/api"; export default apiInitializer((api) => { api.renderInOutlet("below-site-header", <template> <div id='WW_T_D_1' class='oprs-top-leaderboard'></div> </template>); });

템플릿 및 JS API를 위한 인라인 스크립트 태그 현대화

개발

NateDhaliwal (Nate Dhaliwal) 6월 28, 2025, 11:52오전 3

이제 JS 탭이 있으므로, 아마도 api.renderInOutlet을(를) 사용할 수 있을 것입니다.

글		댓글	조회수
Upcoming Header Changes - Preparing Themes and Plugins Development dev-news	36	4288	9월 8, 2024
Templating of my "component" broke. How do I fix it? Development	14	417	3월 17, 2026
A versioned API for client side plugins Development rest-api	33	20274	6월 21, 2024
Using the JS API Developer Guides plugin-api , explanation , code	18	12410	1월 30, 2026
Developing Discourse Plugins - Part 2 - Connect to a plugin outlet Developer Guides plugin-guides , tutorial	38	30561	11월 23, 2025

템플릿 및 JS API를 위한 인라인 스크립트 태그 현대화

Related topics