Hey everyone! As the final step of our effort to move away from the legacy “widget” rendering system, we’re deprecating the use of widgets in Discourse and will soon deactivate it entirely. Timeline These are estimates and subject to change July 2025: :white_check_mark: Add deprecation warnings in core and an experimental site setting to deactivate them :white_check_mark: Publish announcement on Meta August 2025 :white_check_mark: Upgrade the official plugins and theme components to use Glimmer Components. :white_check_mark: Run Meta with widgets deactivated. :white_check_mark: Enable deprecation messages with an admin warning banner. Q3 2025: Third-party plugins and themes need to be upgraded. Q4 2025: :white_check_mark: Widget rendering system will be disabled by default using deactivate_widgets_rendering: true. There will be a short period of time where it can be re-enabled manually. :white_check_mark: Remove the legacy code and deactivate the widget rendering system :police_car_light: Non-compatible plugins and themes will stop working properly after this. What does this mean for you? If any of your plugins or themes use ‘widget’ APIs, you’ll need to update them to use newer APIs or Glimmer Components before the Q4 2025 deadline. I have custom plugins or themes installed. Do I need to update them? You’ll need to update your plugins or themes if they use any of the following: createWidget decorateWidget, changeWidgetSetting, reopenWidget, or attachWidgetAction The MountWidget component :bulb: Pro tip: If you have extensions that use any of these customizations, you’ll see a warning in the console identifying which plugin or component needs to be upgraded. :warning: Important: If you use more than one theme in your instance, be sure to check all of them since the warnings will only appear for active plugins and currently used themes and theme-components. The deprecation ID is: discourse.widgets-end-of-life How does this relate to the recent post-stream modernization? The post-stream was the last major part of Discourse to still use the widget rendering system. With its modernization, we can now move ahead with the full retirement of the widget system. Take a look at the upgrade guide for more details about those changes. How do I upgrade? If you use a third-party plugin or theme: Check if the author has released an upgraded version that’s compatible with the new system. If you’re a plugin/theme author: Replace your custom widgets with Glimmer Components Use plugin-outlet connectors to insert them into the UI Check our Developer Guides for more information on making these updates.

https://github.com/discourse/discourse/pull/35504 When you next update your Discourse installation, the widget rendering system will now be disabled, and any widget-based customization won’t be rendered anymore. For now, on incompatible sites, the admin can re-enable the old behavior by modifying the values of the following setting: deactivate_widgets_rendering This is the final phase before removing the old code from the Discourse code base, which is expected to happen in about a month. Subsequently, it won’t be possible to re-enable widgets anymore.

The PR removing the widget system from Discourse was merged yesterday. https://github.com/discourse/discourse/pull/36109

Maybe a silly question, but do you think it would be possible for Discourse to offer an .md file with a guide/helpers that one could feed to their CLI code tool of choice to help with the migration of a plugin component? Just a thought :smiley:

We tried to provide migration instructions for the most common customization patterns, like the ones that modified the post-stream. It’s harder to write a more comprehensive guide because pretty much anything could be done using widgets, so the remaining customization needs to be converted to components on a case-by-case basis. I’m watching these topics and we’ll try to answer questions posted here to aid those that still need to migrate. I’ve looked briefly at the code that looks like it’s triggering the deprecation in your forum using the browser console, and it seems like it’s the following line: const { iconNode } = require("discourse-common/lib/icon-library"); let iconsjira = iconNode('icons-jira'); iconNode was used only by widgets, and now it’s a noop function. In your code it doesn’t appear this variable is being used, so it should be safe to just remove these lines. Let me know, if you need more help.

Próximo EOL para el sistema de renderizado de widgets

Desarrollador

saquetim (Sérgio Saquetim) 27 Noviembre, 2025 19:27 5

El PR que elimina el sistema de widgets de Discourse fue fusionado ayer.

Tema		Respuestas	Vistas
Upcoming post stream changes - How to prepare themes and plugins Development dev-news	12	2047	27 Noviembre 2025
Upcoming Header Changes - Preparing Themes and Plugins Development dev-news	36	4784	8 Septiembre 2024
Upcoming post menu changes - How to prepare themes and plugins Development dev-news	12	1356	1 Abril 2025
Upgrading Discourse to Ember 4 Development ember	19	3529	19 Diciembre 2024
Widgets, the Widget API and their roadmap? Development	2	731	23 Enero 2024

Próximo EOL para el sistema de renderizado de widgets

Temas relacionados