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…

I have this on my theme, what do I need to do to get the error to go away? <script type="text/discourse-plugin" version="0.5"> api.decorateWidget('post-meta-data:after', dec => { if (dec.attrs.post_number === 1) { const topic = dec.getModel().get('topic'); return dec.rawHtml(`<div class="…

You’ll have to move the api.decorateWidget(); part to the ‘JS’ tab under ‘Edit CSS/HTML’ in a theme. But do note that widgets are now deprecated ; you’ll want to use plugin outlets .

I moved it to JS like so: import { apiInitializer } from "discourse/lib/api"; export default apiInitializer((api) => { // Your code here api.decorateWidget('post-meta-data:after', dec => { if (dec.attrs.post_number === 1) { const topic = dec.getModel().get('topic'); return dec.rawHtm…

if someone doesn’t post here sufficiently quickly you might consider Marketplace to find someone to help you.

I moved it back to <head> for now. I’m okay with the warning until it gets solved. If it dies, it’s not the end of the world, it’s just a nice workaround for what I was really looking for. [Bild] Topic ID as a variable? Development Is there a way to get…

Is there an error in the browser console?

“Deprecation notice: Adding JS code using is deprecated. Move this code to a dedicated JavaScript file. [deprecation id: discourse.script-tag-discourse-plugin] [info: Modernizing inline script tags for templates & JS API ]” “Deprecation notice: The post-meta-data widget has been deprecated and a…

I think you can replace this with outlets. Where in the topic are you adding this?

If you’re asking where the output is in production, then it’s here. [post-number] I’d much rather have it somewhere that makes it searchable though.

Modernisierung von Inline-Script-Tags für Templates & JS API

Entwickler

tknospdr (David Muszynski) 5. August 2025 um 15:47 28

Ich habe es vorerst zurück in <head> verschoben.
Ich kann mit der Warnung leben, bis sie gelöst ist.
Wenn es abstürzt, ist das nicht das Ende der Welt, es ist nur eine nette Übergangslösung für das, was ich wirklich gesucht habe.

Thema		Antworten	Aufrufe
Upcoming Header Changes - Preparing Themes and Plugins Development dev-news	36	4180	8. September 2024
Templating of my "component" broke. How do I fix it? Development	14	309	17. März 2026
Using the JS API Developer Guides plugin-api , explanation , code	18	12241	30. Januar 2026
A versioned API for client side plugins Development rest-api	33	20189	21. Juni 2024
Developing Discourse Plugins - Part 2 - Connect to a plugin outlet Developer Guides plugin-guides , tutorial	38	30346	23. November 2025

Modernisierung von Inline-Script-Tags für Templates & JS API

Verwandte Themen