Discourse 2.5.0.beta6 introduces key updates including the end of IE11 support (disabled by default, fully removed in 2.6.0.beta1) and a visual refresh of menu styling across the platform. Security updates address three community-reported issues via HackerOne, including fixes for topic slugs, embed redirects, and missing security checks. Numerous plugin improvements are included — notably for Onebox (Instagram), Encrypt, Graphviz, Knowledge Explorer, Subscriptions, Patreon, WP Discourse (with metadata and auto-publish fixes), User Notes, Solved (color fixes), Calendar (launch of Discourse Event), and Font Awesome Pro. The release also delivers a wide array of additional features, bug fixes, and UX enhancements — such as new plugin outlets, better 404 handling, improved image handling, and refined UI elements like button alignment and popover arrows. Performance gains include more efficient queries. jomaxro and jomaxro detail these changes in depth, encouraging users to review the full changelog for complete coverage.
In preparation for the release of Discourse 2.5 later this month, support for IE11 has been disabled by default as of this beta. Support for IE11 will be completely removed in Discourse 2.6.0.beta1.
Update and Homogenize Menu Styling
We’ve gone through all the various menus in Discourse and updated their styling, removing the older, grey “button-like” style used in the past.
But wait, there’s more! We do our best to highlight new features and changes for you, but there’s always too many changes to detail. For a full list of new features, bug fixes, UX improvements, and more, be sure to review the Additional Features and Fixes listed below.
Update wpdc_auto_publish_overridden post metadata when a post is unlinked from Discourse to prevent the plugin from attempting
to publish updates to the post to Discourse
Fix issue with the Auto Publish setting for posts that were unlinked from Discourse prior to WP Discourse version 2.0.3
Add static get_discourse_comments function to allow comments to be displayed without loading the comments template