How to install plugins without using a third-party host? — Willy sought a way to deploy plugins locally without relying on GitHub, sparking debate about version control necessity. RGJ and Merefield argued the benefits of source control, while Satonotdead raised concerns about GitHub’s history of takedowns and suggested Codeberg as an alternative. read more
Mail jobs are failing — Josip_Meštrović reported Sidekiq errors with Nokogiri when sending emails. Awesomerobot identified the culprit as an a:visited pseudo-selector in /admin/customize/email_style/css, resolving the four-day headache. read more
Avatars take a long time to load after moving to S3-compatible R2 — David_Ghost faced slow avatar loading after migrating to Cloudflare R2. Lilly guided him through checking Sidekiq queues and the avatar_proxy logs, suspecting a missing CDN remap. read more
#Announcements
Introducing a new “Post Type” Composer actions dropdown — Gormus noted that the “Toggle post voting” option appears even when the category is not an “Ideas” type. Awesomerobot confirmed this is by design but provided a theme component hook to hide it per category. read more
Cut off “Dismiss ⌄” button — Canapin found an empty space between the label and chevron on all themes. Chapoi explained it’s an intentional effect that modernisation changes may have broken and will fix. read more
Problème d’affiche dans le topic depuis la dernière mise à jour — Gilles and Newbit1337 reported broken buttons on Foundation theme after update. Chapoi traced it to a missing modernisation toggle and submitted a fix. read more
Text, in the topic subscription control context menu, is blurred — Rokejulianlockhart observed blurred text in Firefox Nightly but not in safe mode. Awesomerobot suspects a custom font conflict. read more
FIX: Word limit shouldn’t break IME composition — Small-Lovely-Cat bumped a stale PR fixing word limit issues for IME users. Sam prioritised it, and Nat merged the contribution. read more
FIX: Boosts in reviewables should link to posts rather than topics — Small-Lovely-Cat submitted a PR to direct reviewable boost links to specific posts instead of the topic. Zogstrip from the team merged it. read more
#Data & reporting
AI Translation Progress Graph — LotusJeff found the backfill progress graph inaccurate and cached. Falco explained the two‑step translation process and agreed the caching hides locale detection progress, promising improvements. read more
Nested replies broken? — Paul_King reported that enabling nested replies caused replies to vanish or appear in wrong topics. Markvanlan and Falco suggested updating, while Chapoi noted the feature is changing fast. read more
How to make a banner post — Jonathan5 couldn’t find the “make banner topic” option. Awesomerobot revealed the restriction: banner topics cannot be in categories with group permissions. Recategorising restored it. read more
How to use internal AI endpoints? — Satonotdead struggled to connect Discourse AI to a self‑hosted LLM. Falco advised using the domain name in DISCOURSE_ALLOWED_INTERNAL_HOSTS instead of an IP. read more
#Plugin
Dumbcourse – Old‑browser friendly UI at /dumb — Satonotdead revived interest in this accessibility plugin. Ars18 confirmed it’s still active and merged into their master plugin, but the standalone repo remains available. read more
Discourse Translator — Awesomerobot recommended switching to Discourse AI for automatic translation, noting AI models can be cheaper than self‑hosted LibreTranslate. NateDhaliwal suggested self‑hosted models via Ollama for further cost reduction. read more
I’m tracking down the world’s best community builders. Here’s what I’ve learned so far… — Jawestenberg shared a personal blog post about the loneliness of community building and the importance of NPS for ROI. read more
Falco explained the translation progress page caching in AI translation graph, recommended updating Discourse for nested replies in nested replies broken, provided domain‑based internal host configuration in AI endpoints, confirmed Android share target works in PWA sharing, and moved a SEO feature request to feature voting in Googlebot view.
Yesterday’s most heated debate was about plugin installation without GitHub – proving that even Discourse users can’t escape the version control tug‑of‑war!
We’ve curated the most noteworthy discussions from the past day, grouped by category and linked for your browsing pleasure.
#self-hosting
Willy ignited a lively debate by asking how to install plugins without relying on a third-party host like GitHub. Many community members – Chapoi, Merefield, RGJ, Lilly, Satonotdead, Stephen, Heliosurge – chimed in with advice, ranging from using theme components to self-hosted Git alternatives. The thread eventually turned into a broader discussion about the necessity of version control for even the smallest plugins, with RGJ arguing it’s “less than one minute of work” to set up a GitHub repo. Despite the frustration on both sides, the thread remained constructive. read more
Miednr reported a strange bug where anonymous visitors are redirected to the login page when categories is the first entry in top menu. Zogstrip couldn’t reproduce it initially, and Nat asked for HTTP status headers. Miednr confirmed it persists even in safe mode with plugins disabled, but a workaround (putting latest first) works. The team is still investigating. read more
RGJ discovered and reported that the “New Topic” button is not responsive when resizing the browser window – text appears/disappears incorrectly until a refresh. Awesomerobot confirmed the bug and submitted a quick fix that should land soon. read more
Ted pointed out that the “Dismiss ⌄” button on some themes is cut off, which Chapoi acknowledged was an intended design effect that may have been broken by recent modernisation changes. A fix is planned when time allows. read more
Paul_King encountered broken nested replies with emails, and after troubleshooting with Falco and Chapoi, updating his instance resolved the issue. The update process itself briefly broke the site due to an old mysql-dep.template.yml reference – a line that had worked for years suddenly caused a failure, but removing it fixed everything. read more
Gilles asked why Ask Discourse has become less performant lately. Nat responded that the underlying model was recently switched to a new local hosted DeepSeek v4 flash, and they will do a quick check. read more
Small-Lovely-Cat contributed a fix for boosts in reviewables – previously, reported boosts linked to topics rather than the specific post, making them hard to find. Their PR was merged by @zogstrip. read more
RGJ reported that events from unlisted topics still appear on the calendar, visible to everyone even though the topic is hidden. The expected behaviour is that unlisted topics should not show their events. read more
#feature
Jagster wondered how to force English for unsupported languages when the Content Localization setting is used with a non-English default locale. Falco and Nat explained that there is currently no fallback locale option; the site default locale dictates the fallback, so setting the default to en is the only way. read more
#announcements
Davidb announced a new reactions popup in chat, allowing users to see who reacted to a message by hovering (desktop) or long-pressing (mobile). The feature is experimental and can be enabled via the Upcoming changes admin page. read more
#data-reporting
LotusJeff shared SQL queries for building an AI Translation Progress Graph in the Data Explorer, detailing how to count translated vs eligible topics and posts. Nat thanked them and promised to improve the dashboard soon. read more
#site-feedback
The collaborative content gardening hub experiment continues. NateDhaliwal suggested adding #chat and #reactions tags to the new reactions announcement, which Davidb did. The topic is a meta-level discussion about curating meta itself. read more
#plugin
In the Discourse Reactions plugin topic, Jrgong +1’d a request to allow users to click an already-given reaction to “join in” (like Slack/Discord), noting that Discourse UI/UX often deviates from established web standards. read more
Ted reflected on a blog post about community builders feeling lonely, praising the line “People come for the skills and stay for the feeling that they made the best decision of their lives.” He shared that this mirrors his own experience with the Ruby community. read more
(Note: We aimed for 15 topics but included 13 to avoid forcing less relevant ones – quality over quantity!)
The Discourse team was active across many discussions yesterday. Here’s a summary of their contributions, with links to the relevant topics.
Nat engaged in several conversations: he noted that Ask Discourse performance may be due to a model change and promised a check (topic); provided guidance on fallback locales and Content Localization settings (topic); thanked LotusJeff for translation SQL queries and promised improvements (topic); and helped troubleshoot a bug where plugins triggered multiple bot replies in a Chinese-language support topic (topic). He also joined the discussion on multi-language preferences and suggested per-post toggles (topic).
Awesomerobot contributed a fix for the unresponsive “New Topic” button (topic), confirmed the Theme Creator 500 error (topic), and proposed a new UI for content language preferences replacing the old single setting (topic).
Chapoi provided instructions on updating Discourse to fix nested replies (topic) and acknowledged the cut-off dismiss button as a known design issue (topic). He also gently reminded the community to avoid ridiculing users for their preferences in the plugin installation thread (topic).
Davidb announced the new chat reactions popup experimental feature (topic) and updated the tagging for that announcement in the gardening hub (topic).
Zogstrip merged a PR for boosts in reviewables (topic), helped debug the anonymous login redirect bug (topic), and confirmed a fix for a report description bug in another topic (topic).
Sam confirmed that Shared Edits can now be enabled for non-TL4 members, with a related PR linked (topic).
Rishabh helped a site get added back to Discourse Discover after it became public (topic).
Keegan noted a fix for the full name requirement bug that had been merged earlier (topic).
Martin submitted a fix for the unified new view in the topic list (topic).
From heated debates about Git dependency to the arrival of snazzy new chat reactions – yesterday proved that even the smallest plugin can spark a fiery discussion, while a simple popup can brighten everyone’s day.
Is it possible to disable Discourse updates? – Willy raised concerns that his self‑hosted forum “updates automatically without permission,” breaking custom plugins. Falco clarified that Discourse has no automatic update feature, and that running ./launcher rebuild app triggers an update. A deeper discussion ensued about pinning Discourse to a specific commit hash using the version: parameter in app.yml. Moin and Mcwumbly explained that you can use any branch, tag, or commit hash, but warned against pinning in production due to missed security patches. read more
How to install plugins without using a third-party host? – The conversation continued from earlier days. Heliosurge and NateDhaliwal suggested using theme components instead of plugins for simple additions like a homepage button, pointing out that components can be uploaded as ZIP files. Chapoi stepped in to de‑escalate when the thread turned aggressive, reminding everyone to stay constructive. Falco also noted that you can mount a host folder into the container via app.yml volume support. read more
Ask discourse moins performant – French‑speaking user Gilles reported that Ask Discourse has become “less performant” and “turns in circles” with answers. Nat explained that the backend was recently switched to the locally‑hosted DeepSeek v4 flash model for speed and better grounding in Meta’s documentation. Falco added that Ask Discourse is designed for general troubleshooting, not development; for coding tasks he recommended using dv (Discourse Vibe). read more
Why topics translate faster than posts – LotusJeff observed that topic translations cover 7 months while posts only cover 20 days. Falco explained that both translation batches process at similar rates, but topics (typically shorter) finish quicker. He suggested adjusting the max age or backfill rate site settings to let posts catch up. read more
#Feature
Ability to configure where videos uploaded – Prempavee, on a Pro plan, wanted to offload video uploads to an external service like Mux without upgrading. Moin pointed to the Vimeo/YouTube upload theme component and Arkshine detailed ongoing work to secure it (e.g., dealing with Vimeo’s partnership requirements and token safety). Since custom plugins aren’t allowed on the Pro plan, Arkshine promised to explore other solutions. read more
#Announcements
Current Projects – June 2026 – Rishabh published the monthly newsletter. Recently finished items include: bringing the GIFs component into core, the unified new topic list, nested replies, and a new layout/blocks system for themes. Work in progress covers improvements to reporting/analytics, the Events plugin, the Free plan, and a new “Workflows” automation system. read more
New Reactions Popup in Chat – Davidb announced an experimental popup that shows the list of users who reacted to a chat message when hovering (desktop) or long‑pressing (mobile). Admins can enable it via the “Upcoming changes” page. The new feature is designed to replace the limited tooltip with a richer, filterable panel. read more
Bug? Visitors can’t access forum index – Miednr reported that setting categories as the first entry in top menu redirects anonymous visitors to the login page on /, while /categories and /latest work fine. Nat and Zogstrip attempted to reproduce, and after troubleshooting, Miednr discovered the issue correlated with the OpenID Connect plugin. Even after disabling it, the problem reappeared; a temporary fix was to “update” admin settings without changes. read more
Events from unlisted topics show on calendar – RGJ reported that events created in unlisted topics still appear on the calendar. Zogstrip confirmed the bug and provided a fix via PR #41194. The fix was also cross‑linked to an older related topic. read more
#Community Building
Forums that forbid AI content… How’s it going? – Robbie.Morrison shared his harrowing experience on Wikipedia, where strict anti‑AI policies led to false accusations and a “reverse burden of proof.” He linked to an AskHistorians Reddit discussion that also struggles with governance. RGJ provided articles about AI detectors being biased against non‑native English writers, and One1 cautioned that such policies can unfairly penalize careful writers. read more
Upcoming events – unlisted is invisible in category but visible in Upcoming Events – Moin linked this older report to the recently fixed events from unlisted topics bug, noting the same underlying issue. read more
在插件中如何配置数组对象？使用 json_schema? type: objects ？ – Singi2016cn encountered a rendering issue with the type: category JSON schema validator. Awesomerobot confirmed that type: categories works correctly and suggested using validations: { max: 1 } to limit to a single selection. The discussion helped clarify schema usage for plugin developers. read more
Yesterday’s most popular question was “Is it possible to disable Discourse updates?” — turns out you can pin a commit hash, but you’ll also pin yourself to a world of manual security patches. Choose wisely!
In the last 24 hours, the community added 79 new posts across 39 new topics, collecting 138 likes. The most active contributors were: Moin (21 likes, 12 posts), Falco (19 likes, 6 posts), Mcwumbly (15 likes, 10 posts), Rishabh (14 likes, 1 post), Awesomerobot (12 likes, 4 posts), Robbie.Morrison (8 likes, 3 posts), Markvanlan (7 likes, 2 posts), RGJ (7 likes, 1 post), Chapoi (6 likes, 3 posts), One1 (5 likes, 5 posts).
Interesting Topics
#Community Building – A heated discussion about forums banning AI‑generated content took off. Robbie.Morrison shared a painful experience with Wikipedia’s enforcement, where a native‑language author was repeatedly accused of using AI. RGJ linked research showing bias against non‑native speakers, and Awesomerobot confessed that the em dash — once a mark of fine writing — now triggers suspicion. read more
#Announcements – The June 2026 Current Projects newsletter from Rishabh laid out recently finished work (GIFs in core, unified new topic list, nested replies, a new blocks system) and ongoing improvements to analytics, events, the Free plan, and a forthcoming Workflows automation system. read more
#Self-hosting – JackieP asked how to self-host a Business‑level account. Falco clarified that Discourse is GPL v2, so all core features—including SSO and gamification—work on‑premises without any license. Pfaffman offered integration services. read more
#Announcements – The nested replies feature got adjusted defaults: max depth is now 3 and cap is true. Markvanlan made the change, and Mcwumbly suggested per‑category settings for different use cases (voting, AMAs, etc.). read more
#Announcements – Livestream creation got simpler: a new toggle on events replaces the old livestream tag. Awesomerobot documented the change, including new CSS classes and serialization for developers. read more
#Feature – The multi‑language preference UI sparked further debate. Moin argued that removing the whole‑topic toggle made it harder to quickly switch between translated and original content, especially when reading multi‑language threads. Awesomerobot defended the per‑post toggle but acknowledged room for improvement. read more
ux – Moin reported overlapping icons when editing a topic’s metadata — the AI sparkle overlaps the category dropdown arrow. Already flagged in the AI suggestions thread. read more
ux – Another AI‑related visual glitch: the title‑suggest button sits above the topic title input when editing, and offers English suggestions even for German titles. read more
Support – Falcoexplained why topics get translated faster than posts — the backfill batches are similar sizes, but topics with many posts fall behind. Admins can tweak max age or backfill rate to rebalance. read more
Rishabh published the Current Projects – June 2026 newsletter, summarizing recent releases (GIFs in core, unified new view, nested replies, blocks system), ongoing work (analytics, events, free plan improvements), and the upcoming Workflows automation. read more
Chapoi responded to a request for blocks system documentation, noting it will arrive once the API stabilises. He also clarified that the trust‑level guide already states all requirements are “and” conditions. read more
Keegan acknowledged the AI plugin enable bug and confirmed a fix is coming, while also reiterating that the plugin is mandatory on free tiers for spam protection. read more
Yesterday, the community de‑nested replies, debated the soul of authenticity in AI detection, celebrated the em dash’s fall from grace, and proved that even a software forum can’t escape existential questions about writing style.
Nicolsdennis continued development of their native mobile client for iOS and Android, sharing a preview of “Tablet Mode” that splits the feed and post panes like a two-for-one layout. They also demonstrated support for post translations and a cross-forum post navigator. Read moreRead moreRead more
@ばこん reported that HTML comments inside posts are being mistakenly picked up by AI summarization, causing hidden text to appear in summaries. Falco marked this as #wontfix, suggesting users adjust the summary prompt instead. Read moreRead more
Ililaoban found a regression affecting user activity pages: pressing the browser back button after viewing a post no longer restores the scroll position, despite a prior fix for the same issue. Read more
#Site Management
MarkDoerr published Part 2 and Part 3 of the Discourse Moderation Guide series. Part 2 covers managing users (trust levels, warnings, suspensions) read more, and Part 3 details content management (flags, review queue, topic timers, slow mode) read more.
Firedragon reported being unable to see a Starter upgrade option in their account. Chapoi and Ondrej assisted, but the issue appears to be related to recent billing UI changes; a team response is expected Monday. Read moreRead more
One1 sought advice on automatically transferring themes via Rails console, asking for clarification on the correct command syntax. NateDhaliwal confirmed the need to use rails c inside the Docker container. Read moreRead more
Darkpixlz encountered embed URL configuration issues – Discourse created ghost topics with a 404 page. Falco clarified the difference between discourseUrl and discourseEmbedUrl. Read moreRead more
#Feature
Arkshine shared a workaround for video upload destination using a Cloudflare Worker as a broker to handle auth and hide provider credentials – a clever solution for self-hosters who want to upload to CF Stream or Mux. Read more
LotusJeff requested a date picker in AI Translate settings, explaining that topic translations often outpace post translations, leaving users with partially translated threads. A date cutoff would solve this disparity. Read more
#Plugin
Bartv gave feedback on Discourse Reactions, noting that the emoji category scroll bar is not visually discoverable, custom emojis should be pinnable, and “Frequently Used” is stored per browser rather than per account. Moin suggested a workaround for reordering. Read moreRead more
#Site feedback
Moin reported broken avatars in quotes within translated posts – the avatars show broken images for all locales, not just German. The issue appears across translated topics with many quotes. Read more
Heliosurge sparked a discussion on where open-ended product discussions should happen, suggesting Contribute > Feature with AI summaries or a new #discuss tag. Read more
#Announcements
The solved improvements feature (allowing “Me Too” indicators) was discussed further. Noble_Fish asked if admins can see who clicked “Me Too”, and EricGT shared a real-world use case on community.openai.com. Read moreRead more
Rokejulianlockhart clarified that an earlier bug report about blurred text in subscription context menus is actually a Firefox bug (bug 2051078), apologizing for the false alarm. Read more
#Theme component
Bartv pointed out that Homepage Feature images are loaded at 1000x1000px but rendered at ~200px, wasting 83% bandwidth. He suggested adding an option to choose image sizes. Read more
Heliosurge inquired about rich editor support for the Discourse svgbob component and suggested better documentation for the “SVGblob Height” setting. Read more
In the last 24 hours, members of the Team group were active in the following topics:
Falco responded to the HTML comments bug report (#406275), marking it as #wontfix with a clear rationale. Read more
They also helped Darkpixlz with embed URL configuration (#406289), explaining the difference between the two URL settings. Read more
Chapoi assisted Firedragon in the No starter upgrade option thread (#403167), checking account sections and promising a team reply after the weekend. Read moreRead moreRead more
Ondrej also contributed to the same No starter upgrade topic (#403167), confirming the issue by testing the URL path and providing a screenshot. Read more
Yesterday’s most liked moment was Nicolsdennis unveiling tablet mode for the native mobile app – proving that two panes are better than one, especially when they slide like drawers.
In the last 24 hours, the community generated 46 new posts across 21 active topics, proving that the Discourse engine never sleeps. The top contributors by likes were:
Introducing nested replies – The new threaded reply feature continues to spark discussion. NiceOldGuy shared a thoughtful defense of the flat model while acknowledging the use case for issue tracking, linking to Jeff Atwood’s canonical take and the Discourse terminology debate. The team is watching feedback closely. read more
Introducing the unified new view for the topic list – Martin and Sam clarified how the combined New/Unread list bumps the current user’s own topics to the top when marked unread, a behaviour inherited from the old Unread list. Moin raised concerns about DiscourseHub showing only combined counts; Pmusaraj was pinged for a fix. read more
’ in topic titles on oops page – Moin spotted that the oops page (e.g. https://meta.discourse.org/oops) displays raw ’ entities instead of curly apostrophes. Lilly found it funny and linked a related screenshot. Sam confirmed the root cause was a security fix that escaped entities incorrectly and promised a fix. read more
HTML comments are also summarized by AI – Falco marked this as #wontfix, noting that stripping HTML comments from AI preprocessing isn’t worth the trade‑off. Users can adjust agent prompts if it bothers them. read more
Regression: /u/:username/activity loses scroll position after browser Back – Ililaoban reported that the scroll‑restore feature on user activity pages (touted in the 3.0 release notes) is broken again. read more
#Feature
Official warning pm notification feature – LittleD dug into a Glimmer migration oversight: the isWarning property on Post model is missing, causing warning PM first posts to lose their moderator styling. A one‑line getter fix was suggested. read more
#Plugin
Discourse Reactions – Martin continued iterating on reaction UX, discussing a “click to react” pattern from Chat, pinning custom emojis, and making the emoji picker scroll hint more obvious. Chapoi was asked for design feedback. read more
Discourse Bilibili Onebox – Noble_Fish noted that the onebox doesn’t respect the ?p=2 parameter for playing specific parts of a Bilibili video. Scavin confirmed a fix and updated the plugin. read more
#Self-hosting
Commit b4a3389 更新后如何获取用户ip – Iamntz shared a detailed Nginx config snippet for restoring real visitor IPs when Discourse is behind Cloudflare, including the complete Cloudflare IP range list. read more
#Site feedback
Broken avatars in quotes within translated posts – Moin noticed that when a topic is machine‑translated, avatars inside <aside> quotes show broken images. This affects all languages, not just German. read more
No starter upgrade option – Firedragon couldn’t see the Starter plan after the pricing page changes. Chapoi and Ondrej investigated. Rishabh later confirmed that Starter is now a legacy plan and no longer appears as an upgrade option, apologising for the confusion. read more
Fixing a topic timestamp change gone wrong? – Adamengst accidentally redated an entire topic and tried to fix it. Moin pointed him to the Rails console method for editing post dates. read more
Bootstrap mode is legacy? – Tobiaseigen shared how the removal of bootstrap mode is hurting new communities where TL0 users can’t access PMs and get stuck in a low‑engagement loop. Merefield suggested temporarily setting default trust level to 1. read more
Using threads with existing topics – Lew_Grothe asked whether turning on threading for a category reformats existing replies. Falco clarified: no, conversion is manual via topic action. Moving posts from a flat topic into a threaded topic preserves threading accuracy. read more
Right clicking in composer finds image from post behind composer – Seanblue discovered that right‑clicking in the composer (outside the textarea) can trigger browser actions on images beneath the overlay. Chapoi added a pr-welcome tag but noted it’s not a real‑world issue. read more
Sam weighed in on the oops‑page entity bug (post), discussed the unified new view sorting logic (post), and was pinged about deleted‑post placeholders in the nested replies view (topic).
Falco marked HTML‑comment AI summarization as #wontfix (post), helped with embed configuration (post), and clarified threaded topic conversion (post).
Martin engaged deeply with reactions UX feedback (post) and the unified new view implementation (post).
Chapoi assisted with the Starter plan issue (post 25 and post 28) and noted the right‑click composer bug as low priority (post).
Rishabh confirmed that the Starter plan is now a legacy upgrade option and that the “Change Plans” page has been removed temporarily (post).
And in the finest tradition of meta surprises, yesterday we learned that right‑clicking through the composer is basically a magic trick – the forum sees right through your overlay.
Lilly identified a bug where custom emojis loaded from S3/R2 bypass the configured CDN routing. She opened a PR to wrap the emoji URL in Discourse.store.cdn_url() and provided a theme component as an interim fix. Falco noted that standard emojis use one CDN while custom emojis use another, and that a properly configured two-CDN setup should cover both. read more
In a related topic, Lilly and Supermathie helped a user whose IP detection broke after a recent commit. The solution involves switching to a Unix socket or adding custom real_ip directives for the Docker gateway. Supermathie also wrote a dedicated guide for this scenario. read more
#Announcements
Sam announced cost‑based quotas for Discourse AI, allowing admins to set a dollar limit per group for LLM usage. The feature estimates cost across providers and enforces the budget. read more
Mcwumbly discussed the behaviour of Upcoming Changes – specifically that Beta changes are automatically enabled for hosted sites but not for self‑hosters (they wait until Stable). He plans to update the documentation. Moin agreed and noted it clarified why some changes are not moved to Stable. read more
Martin responded to user feedback on the Discourse Reactions plugin, discussing ideas like one‑click reactions, pinning custom emojis to the top, and making frequently used emojis appear directly in the popout. Chapoi was asked for design input. read more
Rishabh clarified that the Starter plan has been made legacy and is no longer an upgrade option from Free. The current pricing tiers are Free, Pro, Business, and Enterprise. The Change Plans page was also removed pending redesign. read more
Chapoi explained the modern way to set a custom homepage using the custom_homepage modifier in a theme, rather than a custom route. NateDhaliwal added that users must set their default home page to (default) in Preferences to see the custom homepage. read more
Tannerabread fixed a long‑standing bug with spoilers inside 13 via PR #41266, and identified a duplicate bug report in the custom wizard plugin category.
Nat shared real‑world experiences with AI translations and warned about a configuration footgun in the SEO payoff topic.
Lilly (likely a staff member) reported and fixed the custom emoji CDN bug, contributed to the IP detection thread, and even posted a PR for the emoji fix. see her bug report
Renato was mentioned as a resource for the Reactions discussion and the cursor jumping issue, though they did not post in the last 24 hours.
Yesterday’s activity saw more than half a dozen AI‑related threads, proving that even robots need a little budgeting now and then – may your costs be low and your placeholders be gone.
Cost based quotas for Discourse AI – Sam announced a new feature that allows administrators to control AI spend by estimated dollar cost per group, making budget management easier. read more
GIFs are moving to Discourse core! – Discussion around the upcoming change to bring GIF support into core. Moin, Mcwumbly, and Davidb clarified that the setting will remain configurable and that the “upcoming changes” wording will be improved. read more
June 2026 monthly release – Loic shared the release notes for v2026.6.0 along with patch versions for previous releases. read more
Introducing Upcoming Changes, a system to manage new features – Mcwumbly and Moin debated moving upcoming changes from “stable” to “beta” for self-hosters, with concerns about theme component breakage and the replacement of the everyone group. read more
Inline integration of AI Suggestions (in Composer) – Chapoi discussed making the AI suggestion UI consistent across the composer and other areas. Nicolsdennis inquired about round-trip latency and suggestion scope. read more
AI translations + crawler indexing = any SEO payoff? – Overgrow asked about SEO benefits of multilingual translation. Nat shared a blog post and fixed a footgun related to set locale from param. Eisammy reported mixed SEO results from translating 140k posts. read more
Discourse Comments on Astro Starlight – Philh showcased a project to embed Discourse comments in Astro Starlight pages, resembling the Coding Horror blog style. NateDhaliwal praised the seamless integration. read more
#Self-hosting
Custom Emojis loaded from S3/R2 bypass CDN routing – Falco and Lilly debugged a CDN configuration issue with Cloudflare R2, discovering that DISCOURSE_CDN_URL seemed incompatible. Lilly reopened a PR that wraps emoji uploads with Discourse.store.cdn_url(). read more
How to install plugins without using a third-party host? – Willy shared a docker-compose approach to mount local plugins into the container via the after_code hook. Pfaffman suggested symlinks, and Nicolsdennis asked about migrations. read more
Proxying new setup with reverse proxy – Tayhansolo experienced sub‑domain verification failures during setup. Darkpixlz recommended using separate LXC containers and Cloudflare Tunnels for residential ISPs. read more
Wana to change username of discourse id on forum community of frappe – Ahsan_Javaid wanted to change their username on the discuss.frappe.io forum. Itsbhanusharma explained that only the community’s admin can make the change via the admin panel. read more
Self Hosted Forum Log In Issues – Apiento reported frequent logout issues. Itsbhanusharma suspected Cloudflare proxy misconfiguration and linked to relevant threads about handling real IP. read more
#Feature
Feature request: Limit topic translation to specific categories – Overgrow proposed an allow‑list setting for AI translation categories to control costs. Pmusaraj noted that most communities benefit from translating all content, but agreed the use case is valid. read more
Show all replies after posting on a topic with simple mode – Moin echoed feedback that users should see all replies after posting in simple mode for doc categories. read more
Nested mouseover notes can be entered but not shown – Dreieck demonstrated that nested footnotes render in the editor but the inner note is not accessible. They suggested either making nesting work or preventing it. read more
#Theme component
Post Views Counter – Awesomerobot modernised the component via a PR. Mbcahyono merged it and handed over maintenance. read more
Homepage Feature – Awesomerobot improved image handling with srcset but inadvertently triggered thousands of thumbnail jobs. Bartv raised a concern, and Awesomerobot reverted the change and provided a console command to clear the queue. read more
#Plugin
Discourse svgbob – Arkshine submitted a PR to update the SVGBob plugin and add new features. read more
Sam announced cost‑based quotas for Discourse AI in topic 406400.
Nat contributed to the AI translations SEO discussion, sharing a blog post and fixing a footgun (topic 406427).
Loic published the June 2026 monthly release notes (topic 406435).
Awesomerobot fixed a staff color bug for warnings (topic 380993), modernised the Post Views Counter theme component (topic 143807), and improved the Homepage Feature component (topic 144264), though later reverted part of the change to avoid excessive thumbnail generation.
Chapoi provided guidance on custom homepage setup (topic 406418) and discussed inline AI suggestions in the composer (topic 405394).
Zogstrip apologised for the theme creator 500 error and linked to a fix PR (topic 406027).
Pmusaraj replied to the translation category limit feature request, noting that most communities prefer to translate all content (topic 392993).
Mcwumbly discussed upcoming changes flow, clarifying that moving features to “beta” will enable them for everyone by default (topic 392894), and acknowledged the Dismiss Admin Noise theme as a useful interim solution (topic 403729).
Davidb confirmed that GIFs will remain configurable after moving to core (topic 404829).
Martin fixed the unified new view in Discourse Hub (topic 404728) by queuing core and mobile updates.
Supermathie explained the chain of trust for real IP handling, noting that Rails does not use X-Real-IP and that X-Forwarded-For processing occurs at the nginx boundary (topic 406372).
And remember, if you find yourself down a rabbit hole of Cloudflare R2 configuration, at least you’ll learn a lot about emojis – and maybe even contribute a pointless PR!
In the last 24 hours, 99 new posts were created across 41 new topics, generating 137 likes. The community was highly engaged, with the following top contributors driving the conversation:
Ed_S questioned the accuracy of security fix comparisons on releases.discourse.org, noting that point releases like 2026.4.2 appear to have the same number of fixes as newer versions. Awesomerobot explained that it’s an artefact of how the release site compares patches forward, not backward, and David confirmed they backport all security fixes to all supported releases. read more
Vitaly_Lukin reported that discourse.theme-creator.io has been down since Monday, showing a generic error page. Moin pointed out that a fix was already merged earlier, and the site should be back soon. read more
A Spanish-language topic by Laguna asked how to hide the floating category and tag breadcrumb menu on a Discourse forum using the Graceful Theme. NateDhaliwal provided CSS to hide the element, and Lilly recommended the Custom Top Navigation Links theme component as a more flexible solution. read more
#Migration
Siamak-Oi inquired about the user account migration experience when moving from Telligent to Discourse under a Business plan. Italo noted that tooling for Telligent likely requires an Enterprise plan, while Cocococosti shared that user accounts migrate successfully and users retain content and stats, though they need to reset passwords on first login. read more
#Announcements
Discussion continued on the GIFs moving to Discourse core topic. One1 struggled to disable the GIF button in the composer, but Moin and Davidb clarified that the upcoming change under a hidden site setting can be turned off, and the wording around permanence was confusing. Mcwumbly acknowledged the labeling issue and suggested improvements. read more
The Introducing Upcoming Changes system saw extensive debate. Moin questioned whether the “reporting improvements” change skipped the “stable” phase, effectively removing opt-out for many admins. Tgxworld admitted it was a mistake and re-added the setting. Martin is working on a fix for the “everyone group” replacement issue in theme components. read more
Moin reported an error when toggling the “reporting improvements” upcoming change, showing a 422 error. Zogstrip quickly submitted a fix confirming the issue was related to the dropdown offering “staff” and “custom groups” but not “everyone”. read more
Lilly detailed a deep dive into a bug where custom emojis loaded from S3/R2 bypass CDN routing. After debugging Cloudflare R2 configuration, she submitted a PR that wraps URL assignments in Discourse.store.cdn_url(), which was merged and fixed the issue. She also updated the R2 documentation accordingly. read more
#Feature
Long-standing feature request Add support for secure uploads in chat saw Mcwumbly confirm no progress has been made yet. He invited users to share anecdotes about how the lack of this feature impacts them, noting that it’s not yet prioritized. read more
#Plugin
In the Resenha – Voice Rooms topic, Itsbhanusharma reported a compatibility issue with ESR Discourse, causing the plugin to fail to load. Falco explained that experimental plugins are not expected to work on ESR, and Mcwumbly enjoyed using the voice rooms, calling them “very cool”. read more
Eisammy shared real-world SEO data from using AI translations. They translated 140k posts and 14k topics into several languages, but organic traffic from those countries dropped slightly. They noted that while LLM translation is useful, they still prefer content written originally in Portuguese. read more
Dreieck discovered a usability bug with nested mouseover notes: they can be entered markdown but the inner note’s popup is not reachable by mouse. They suggested either making nested notes functional or preventing nesting to show the raw markdown. read more
#Self-hosting
Apiento reported persistent login issues on their self-hosted forum, being logged out repeatedly. Itsbhanusharma suspected Cloudflare proxy optimizations and linked to relevant guides on handling real IP addresses. read more
The Discourse team was very active yesterday, addressing bugs, pushing code fixes, and engaging in feature discussions:
Awesomerobot identified a CSS specificity issue in the Foundation theme language toggle, submitted a fix, and cleaned up the tag visibility modal in this PR. Also clarified the comparison methodology in the security fixes topic. read more | read more | read more
Mcwumbly engaged in multiple discussions: explained the GIF setting lifecycle, considered improving the “show original for whole topic” UX in multi-language preferences, acknowledged the need for better composer UI on tablets, and announced the new account review/suspend feature. He also confirmed no progress on secure chat uploads and flipped that request to Contribute > Feature. read more | read more | read more | read more | read more | read more
David confirmed that all security fixes are backported and the release site comparison artefact would be investigated. read more
Davidb clarified that the GIFs upcoming change is under a hidden site setting and will remain off by default unless admins change it. read more
Tgxworld investigated the reporting layout issue, admitted the “reporting improvements” change was mistakenly removed from stable and reverted it. read more | read more
Martin worked on fixing the Discourse Hub app for the unified new view, though decided to let the change breathe internally first. He also engaged on the upcoming changes lifecycle, discussing the need for better theme component solutions. read more | read more
Loic pointed out that CVE numbers in the June release notes linked to different vulnerabilities, likely because the Discourse CVEs haven’t propagated yet. read more
Falco used the Resenha voice rooms plugin and enjoyed chatting with Mcwumbly and Markvanlan. He also explained why experimental plugins aren’t supported on ESR. read more | read more
Nat fixed a footgun in the AI translations documentation where the set locale from param setting was required for crawler indexing. read more
And finally, a fun sentence based on yesterday’s activity: After a whirlwind day of debugging, from custom emojis finding their CDN route home to the theme creator reappearing from the digital void—today’s doghouse is officially a no-puppy-crisis zone!
In the past 24 hours, meta.discourse.org saw 142 new posts and 52 new topics. Community members engaged heavily, with 200 likes distributed across discussions.
Error running remap after changing site URL Tobiaseigen hit a pesky duplicate key violation while running the discourse remap command. Lilly provided a SQL‑based workaround to delete conflicting rows in browser_pageview_referrer_daily_rollups and topic_links, allowing the remap to complete. The thread also serves as a feature request for a built‑in discourse db command. read more
Avatars take a long time to load after moving to S3‑compatible R2 David_Ghost tested four storage/CDN configurations but found avatars consistently slow on first load. Pfaffman and Lilly explained that the issue is likely due to on‑the‑fly avatar generation and suggested running rake avatars:refresh and allowing the edge cache to build. read more
#Feature
Accept paste input during installation Philh reported that the new Discourse installer does not allow pasting long API keys. Falco responded with a fix that will ship with the next installer image. Lilly advised posting further installation issues in the Support > Self-hosting category. read more
Profile spam: Option to delete account and block email but not the IP address Dax announced that a long‑standing feature request has been completed – a new bulk action now allows admins to delete and block by email without also blocking the IP. read more
#Announcements
Review and suspend accounts which are not yet activated Mcwumbly introduced a new ability to filter unactivated accounts in the Admin > Users panel and bulk‑suspend them. This makes it easier to handle spam waves before those users can post. read more
June 2026 monthly release Elmuerte and Loic discussed mislinked CVE numbers in the release notes; the issue was clarified as a propagation delay. The release includes several security fixes. read more
A preview of the redesigned admin dashboard Bartv gave constructive feedback on load times (especially initial load) and wished for graph views for pinned Data Explorer queries. Chapoi acknowledged both points and noted that graph mode is planned after the first version. read more
The prompt message given when upcoming changes are officially added is not clear enough Noble_Fish pointed out that the notification for automatically enabled changes links to the upcoming‑changes page where the setting no longer exists. Moin reproduced and Martin fixed the link target in core; permanent changes now show on the /admin/whats-new page. read more
Can’t regenerate Discourse ID credentials after changing domain name Tobiaseigen found that the “Regenerate credentials” button fails after a domain change. Pmusaraj explained that credential regeneration is handled automatically in Discourse Hosting but not yet exposed in the admin UI for self‑hosted sites. A note has been suggested for the domain‑change guide. read more
Ocultar menú flotante (Hide floating menu) Laguna asked how to hide the category/tag dropdowns. Lilly pointed to the Custom Top Navigation Links component. The Spanish thread was successfully resolved. read more
Schedule site logo changes? One1 wondered about automatically swapping seasonal logos. Chapoi built a theme component (discourse-scheduled-logo-change) that returns seasonal logo URLs based on the current date – contributions are welcome. read more
Nest view, Flag not effect and somelse Cuo_Wu reported that the flag button is unresponsive in nest view and that staff color is missing. NateDhaliwal recommended splitting reports into separate topics for better tracking. read more
Bulk tag edits not creating new revision Moin noted that bulk tag changes do not generate a revision in the topic history. Tgxworld confirmed a fix was already committed by Zogstrip. read more
#Plugin
Resenha – Add Discord‑style Voice Rooms to Your Community Falco shared a summary of two weeks of intense work on the Resenha plugin, including persistent in‑room chat, screen‑share audio, a voice settings modal, and a resizable docked widget. Feedback is welcome. read more
Tannerabread fixed the NoMethodError after merging topics in 8.
From remapping databases to scheduling logo changes, it was a productive day of making Discourse even better – just remember to backup before you remap!
In the past 24 hours, the community generated 105 new posts across 53 new topics, with a total of 125 likes awarded. The top contributors by engagement were:
A preview of the redesigned admin dashboard continued with performance feedback. Bartvreported that the dashboard loads too slowly to use regularly, even on shorter date ranges. Chapoiacknowledged known issues with larger ranges but asked if 7‑day views also lag. Bartvconfirmed the initial load is notably slower, and also provided cosmetic feedback on the date selector and Data Explorer pinned queries, suggesting a graph view toggle. Chapoireplied that graph view is planned but not yet implemented.
Introducing a new “Post Type” Composer actions dropdown had a fix merged. Tynautidentified a z‑index issue on touch devices and provided a CSS workaround; the fix was merged into core. Moin later noted that the dropdown now works correctly on a tablet after the update.
Simpler email subject lines sparked discussion about preserving the [PM] tag. Bonderowelcomed the shorter subjects but wanted the category to remain in the subject. Mikesouthopposed any change, emphasising the importance of [PM]. Bondero later confirmed that the category is now included in an X-Discourse-Category header.
Introducing a docked composer for AI bot conversations was briefly hidden but restored. Keeganexplained that it was accidentally toggled off and has been bumped to beta. Nicolsdennisasked about configurable reply length limits for the AI bot.
Livestream is now part of the Events plugin received questions about front‑page embedding and breakout groups. Lindseyclarified that the video currently exists only in the topic. Stromfeldtasked about future breakout group support, and Nicolsdennisrequested a usage guide.
Discourse Discover: How Top Tech Brands Run Their Communities was published as a blog post by System, highlighting inspiring community examples.
Schedule site logo changes? sparked a quick solution. One1asked for a way to swap logos periodically. Chapoisuggested using a value transformer, then built a theme component and shared it. One1requested the ability to change only the small logo, noting a naming confusion.
Changes to pricing structure and what features are in the free plan? had Rishabhclarify that Solved and Topic Voting were always Pro/Business features, now surfaced earlier in the category creation UI. Also noted the Starter plan is discontinued.
Confused about security fixes as reported at releases.discourse.org involved Davidexplaining version numbering and why 2026.6.0-latest is vulnerable. Ed_Ssought a per‑fix changelog to selectively update.
Import data into Discourse from wpforo was asked by Arya_Tavanawho needed to import with existing users. Chapoisuggested hiring help via Marketplace or following an existing guide.
Is it possible to unban ip banned by discourse?Webmaster_Webmasterreported being blocked from a forum, and Awesomerobotremoved the public IP to protect privacy, explaining no IP checker exists.
How do I properly configure the AWS SNS topic ARN allowlist?Deeniustried various endpoints, and later self‑solved using https://forum.example.com/webhooks/aws.
Bootstrap mode is legacy?Pmusarajfixed first‑day limits to use created_at instead of first post date, improving fairness for TL1 users.
#Theme component
Post Score – Display engagement metrics on posts was released by Donwho described a theme component showing a weighted engagement score (likes, replies, links, bookmarks, reads) on each post. NateDhaliwalsuggested including settings in the announcement.
YouTube PiP & Topic Playlist Player was another Donrelease, adding a header‑docked YouTube player with a progress ring and automatic topic playlist queuing. Nicolsdennisasked about livestream integration.
Homepage Feature continued development. Awesomerobotprovided a Rails console script to clean up unneeded thumbnails and merged a change to fall back to existing thumbnails. Bartvrequested sorting by tagging date, and Awesomerobotnoted that’s not directly possible – Bartvdescribed a workaround using Data Explorer and an external script.
Versatile Banner got an update. Awesomerobotfixed the background image to be served from the theme instead of an external host (which had over 1.5 million views on imgur), and added optional upload settings.
Quote Callouts had a caching mystery. Stephtarareported it not working after installation, but Arkshineconfirmed it actually displayed fine. After reloads it appeared – likely a browser caching issue.
Gated Topics in Category received a fix. Awesomerobotmerged a modernisation update that also fixed the avatar position.
Tag Style Tool had a URL change issue. Arkshineidentified that the admin link now redirects to /customize/themes/ and provided a manual workaround. Jdc20181accepted a PR to fix it.
Nested replies, flagging and staff color has no effect was partially confirmed. Pmusarajreproduced the missing staff colour and official notice, but could not reproduce the flagging issue on second posts. Cuo_Wupointed out it fails on the first post, which Pmusarajthen confirmed.
RTE removes quotation marks within wrap syntax was fixed. Renatopushed a PR to prevent the rich text editor from stripping quotes inside [wrap] syntax.
Category description truncates to first paragraph for primary language but not for Localizations panel languages was reported by Osanwho provided detailed reproduction steps showing the banner behaviour is inconsistent across languages.
User card opens when clicking link on upcoming events card might have resolved itself. Ethsim2reported the issue did not reappear after updating to 2026.6.0-latest +675.
#Feature
Improve convenience in setting of auto-grid less than 3 images was proposed by Ethsim2with a full feature specification: a new site setting auto_grid_images_minimum_count to replace the hardcoded threshold of 3, and an experimental branch.
Configure number of different reactions visible below a posting got a follow-up. Dreiecksuggested showing an ellipsis (…) when there are more reactions than displayed.
Add setting to not show flag notification to admins who are not moderators received support from Gormuswho wants to dismiss all moderation notifications as a non‑moderator admin.
#Community Building
Sharing approaches to using automation to send messages to members saw Stephtarachecking on the promised Workflows feature. Chapoiteased that it’s imminent and “worth the wait”.
#Self-hosting
Rebuild failure – possibly related to rolldown was addressed by Davidwho warned against rm -rf on core plugins and posted an asset‑processor fix. Merefieldasked about overriding templates in core plugins, and Davidstated it’s unsupported but possible at your own risk.
WP Discourse SSO does not synchronize local avatars provided by Advanced Site Enhancements was posted by Miednrwho explained that the wpdc_sso_avatar_url filter appears ineffective with a local avatar stored in user meta. No solution yet.
Group members last visited and last posted date of hidden profilesMoinreported that dates for hidden profiles are barely visible in the Team group list, likely due to missing fallback styling.
Awesomerobot (7 posts) provided a console script to clean up unused thumbnails, fixed fallback thumbnail selection, updated the Versatile Banner to serve images internally, merged a fix for gated topics, removed a publicly posted IP address, explained the origin of the term “Onebox”, and attempted to reproduce an invite bug.
Pmusaraj (4 posts) investigated nested replies bugs (flagging and staff colour), improved first‑day limits for TL1 users, looked into Discourse ID credential regeneration after domain changes, and confirmed that toggling ID re‑creates credentials.
Martin (2 posts) fixed a notification link bug with permanent upcoming changes, and updated the upcoming changes documentation to note that permanent changes appear on /whats-new.
David (3 posts) warned against removing core plugins, committed a build improvement, explained security fix versioning, and stated that overriding core templates is unsupported.
Stephtara (6 posts) tested Quote Callouts (initially thinking it didn’t work), enquired about Workflows, and was involved in the Homepage Feature discussion.
NateDhaliwal (3 posts) suggested including settings in the Post Score announcement, pointed out the privacy risk of posting an IP, and provided a link to WSL setup instructions.
Zogstrip (mentioned as having pushed a fix for bulk tag edit revisions).
Markvanlan was cc’d regarding the nested replies staff colour issue.
From scheduling logos to scoring posts, yesterday was a whirlwind of creative coding and thoughtful feedback – the community’s endless tinkering never ceases to amaze!
Dannii reported frequent 502 and 503 errors on their self-hosted forum, linking high CPU usage to unicorn worker and postgres processes, and a wave of incoming spam via the mail receiver. NateDhaliwal and Ed_S both advised increasing RAM, with Ed_S suggesting to double it. [read more]
Boubou needed help modifying the Nginx configuration inside the Discourse Docker container to pass real IPs from HAProxy. Ethsim2 provided a detailed guide on using X-Forwarded-For or PROXY protocol via app.yml, warning against direct edits inside the container. [read more]
In the same topic, Dannii later asked about the new aws_sns_topic_arn_allowlist setting after updating to 2026.1.5, noting a site advice about rejecting SNS bounce notifications. [read more]
Miednr experienced a transient issue where visitors couldn’t access the forum index, which later resolved itself. Lilly speculated a connection to WP Discourse SSO and avatar sync problems. [read more]
LaugeSvan encountered a certificate loading error (nginx: [emerg] cannot load certificate... PEM_read_bio_X509_AUX() failed) during a first-time Discourse install, likely due to Let’s Encrypt rate limits after repeated attempts. NateDhaliwal pointed to a prior solution. [read more]
#Announcements
The GIF feature moving to Discourse core continues to be discussed. Lilly initially struggled with switching from Klipy to Giphy, but with Moin's help discovered she needed to uninstall the GIF theme component, disable the upcoming change, then reinstall and reconfigure. [read more]
The docked composer for AI bot conversations (topic 403327) saw Nicolsdennis ask whether the maximum reply length can be set. [read more]
The new “Post Type” composer actions dropdown (topic 403635) received a suggestion from Moin about not bumping topics on last-post edits. [read more]
Simple mode for Discourse Doc Categories (topic 403366) – Moin missed seeing subcategory information when browsing Documentation, making it harder to distinguish between guides for hosted customers vs. self-hosting. [read more]
Granular group-based permissions (topic 402273) – Noble_Fish confessed they had misunderstood @everyone to include anonymous users, and now must re-check all group settings after the feature enabled. [read more]
#Plugin
Resenha (Discord-style voice rooms) – Nicolsdennis asked about integrating voice rooms with the Events plugin and using them without a sidebar. Falco confirmed that a popup widget and full-page view already exist, and a future integration with events could trigger notifications five minutes before a scheduled room. [read more]
The allow-pm-to-staff plugin broke after a recent Discourse update, causing private messages to fail. Roi posted the error log, and Pfaffman acknowledged the issue, inviting a pull request. [read more]
Moin reported a display bug in group member lists for users with hidden profiles: the last visited/last posted dates made names nearly invisible. [read more]
Bird asked how to view Qwen AI audit logs after getting a 500 error. Falco advised removing the WHERE clause and suggested triggering a title suggestion to get fresh logs. [read more]
M_Terenui noticed periodic Gemini AI API calls every five minutes even when idle, and confirmed with Falco that Discourse calls AI APIs in the background for backfill tasks like summaries, embeddings, and sentiment, depending on enabled features. [read more]
#Feature
42aross submitted a PR (#41446) to add {username} as a template param in AI persona system prompts, enabling personas to know which user is interacting without relying on the LLM to parse metadata. [read more]
Overgrow reported that dragging to extend text selection in the composer is broken on iOS/iPadOS 18.x – both in the legacy and WYSIWYG editors. The selection freezes on the initially tapped word. [read more]
Miednr opened a topic about WP Discourse SSO not synchronizing local avatars from the Advanced Site Enhancements plugin, even after using the wpdc_sso_avatar_url filter. [read more]
#Theme component
Nicolsdennis inquired about the YouTube PiP & Topic Playlist Player component and whether it could work with the Events plugin’s livestream feature to allow playback while users browse. [read more]
eisammy reported that the Gated Topics in Category component doesn’t hide content from HTML when JavaScript is disabled, contrary to earlier behavior. [read more]
Team members were active in several discussions over the past 24 hours:
Falco helped Bird troubleshoot Qwen AI audit logs and provided guidance on Resenha voice rooms and background AI API calls.
Lilly contributed to the GIF migration topic, visitor access issue, and wp-discourse SSO speculation.
Moin reported the group member hidden profile bug, gave tips on moving respond_instructions in email templates, and commented on the Doc Categories simple mode and Post Type dropdown.
Pfaffman acknowledged the allow-pm-to-staff plugin breakage and invited a PR.
Yesterday, the forum survived a barrage of 502s, a GIF identity crisis, and a Gemini API sleuthing mission — proving that even the most technical communities can’t resist a good drama with a side of code.
Gilles proposed improving the chat user search to make starting conversations more intuitive, especially on mobile and for less tech-savvy users. Chapoi pointed out the cmd+k shortcut but agreed a more visual approach could help newcomers.
Boubou sought help modifying Nginx behind HAProxy to pass real IPs. Ethsim2 provided detailed instructions on using X-Forwarded-For vs PROXY protocol, and Boubou confirmed success with a custom app.yml replacement and by disabling Let’s Encrypt.
Dannii reported frequent 502/503 errors along with high CPU usage from Postgres during backups and spam waves. NateDhaliwal suggested adding more RAM, while Dannii noted the mail receiver is hit by waves of spam.
Dannii also queried the new 4 setting after upgrading to 2026.1.5, seeking documentation for the required ARN allowlist.
#Announcements
Martin shared progress on granular group-based permissions, including an AI-generated table of group-based settings and how everyone previously included anonymous users. Multiple PRs are now open to refine the system.
David helped a user understand security fix changelogs by pointing to the advanced search with specific commit links and the new admin dashboard changelog links for self-hosted sites.
Lou continued work on Discourse Calendar and Events, building a custom tag filter after discovering expired events are not included in the .ics export.
Gilles kicked off a discussion on chat user search and later defended the broader UX perspective, arguing that keyboard shortcuts are not enough for mobile or less technical users.
David helped a self-hoster navigate security fix changelogs by pointing to the advanced search with commit links and the new admin dashboard changelog links.
Between tweaking Nginx behind HAProxy, automating Halloween logos, and debating the existential question of “one click or two,” yesterday’s activity proves that even on a quiet Sunday, the Discourse community never sleeps—and certainly never runs out of creative ideas!
In the last 24 hours, the community was busy with 103 new posts across 35 new topics, receiving 108 likes in the process. The top contributors by post and like count were:
Small-Lovely-Catproposed adding a “Delete” button on the /activity/pending page so users can remove their own pending topics without contacting staff. Darkpixlz and Moin debated whether a confirmation prompt is needed, with Chapoi explaining that Discourse prefers minimal friction for recoverable actions. Read more
Gillessuggested improving the chat user search for less‑tech‑savvy users, especially on mobile. Chapoi pointed out the cmd+k shortcut, while Satonotdead prefers to disable keyboard shortcuts entirely. Read more
Mireille_Coilhacasked how to set category‑specific moderators. Moin replied with clear instructions to enable enable_category_group_moderation and assign groups in the category settings. Read more
Gidinquired about integrating Discourse with a Wix site. Chapoi clarified the difference between free hosting and self‑hosting, and NateDhaliwal detailed the realities of self‑hosting costs and provided links to embedding and Zapier integrations. Read more
Ed_Scontinued a discussion about security fix changelogs. David fixed a bug that prevented unsupported‑release comparisons from showing all security issues, and Ed_S gave feedback on the page layout. Read more
Mononymsought advice on using Ollama for Discourse AI translation. Falco recommended modern models like Qwen 3.5 or Gemma 4, and explained why the old LibreTranslate plugin still works if preferred. Read more
#Announcements
Lindseyannounced the removal of the special “Uncategorized” category, migrating it to a standard default category for consistency. The change is available as an upcoming feature toggle. Read more
The discussion about moving GIF support into core continued. Shauny raised the need for provider attribution (Klipy), and Martin and Davidb confirmed it was accidentally missed and fixed with PR #41501. Read more
Martinprovided a comprehensive, AI‑generated table of group‑based settings and how they treat anonymous users, following the granular‑permissions upcoming change. Work continues with two new PRs. Read more
#Theme component
Chapoireleased a new theme component, Schedule Logo Change, which automatically swaps site logos on a recurring calendar schedule—perfect for seasonal events. NateDhaliwal asked about fallback behaviour. Read more
Nicolsdennisshowcased a native macOS desktop app for Discourse, featuring multi‑forum support, offline browsing, a “cinema widget” for video, and a forum explorer. Feedback from the community was positive, with many curious about the advantages over the browser. Read more
#Community Building
Urdu-Nigaar423asked for best practices on custom fonts in themes. NateDhaliwal warned against monospace fonts for general audiences, and Awesomerobot recommended self‑hosting fonts and keeping variant counts low for performance and accessibility. Read more
#Self-hosting
Tanya_Byrneresolved a rebuild failure caused by removing plugins from the filesystem instead of disabling them. David confirmed that disabling via admin UI is the supported approach, and Merefield argued for better modularity. Read more
#Plugin
Babylaiintroduced a new plugin that bridges Discourse Chat with Telegram, including support for Telegram forum topics, file uploads, and edits. The detailed documentation covers setup, mapping, and known limitations. Read more
Aliarjmandireported a puzzling bug where admin users get a 500 timeout in GitUtils.has_commit? while normal users work fine. The issue seems related to DiscourseUpdates.new_features. Read more
Awesomerobotconfirmed a UI bug where group member “last visited” and “last posted” dates were hidden for hidden profiles, and shared a fix PR #41467. Read more
Miednrcontinued troubleshooting WP Discourse SSO avatar sync with Advanced Site Enhancements. Angus guided them through debugging the wpdc_sso_avatar_url filter, but the filter never fired, indicating a configuration issue. Read more
Yesterday the community proved that even pending topics can be deleted with a single click—though some still prefer a safety net for those fat‑finger moments.
Over the last 24 hours, the community generated 72 new posts across 33 topics, accumulating 94 likes. The most active and appreciated contributors were:
Mireille_Coilhac asked how to assign moderators per category rather than site‑wide. Moin quickly explained the enable_category_group_moderation site setting and showed where to add groups in the category settings. The solution was well received and marked as solved. read more
A new user Tom_Nook_360 wanted to manually grant a badge. Satonotdead pointed them to the existing guide on granting individual badges. read more
Mireille_Coilhac returned with a follow‑up question about disabling automatic topic closure after marking a topic as solved. Moin, Asa, and others helped identify that the category‑level setting for “Auto close solved topics” overrides the global site setting, requiring manual adjustment per category. This led to a separate UX suggestion. read more
#Announcements
Lindsey announced the removal of the special Uncategorized category, migrating it to a standard category to eliminate bugs and inconsistencies. Admins can opt in early via the “Upcoming changes” admin page. Communities relying on tags‑only setups are advised to use a theme component and set a default composer category. read more
Davidb confirmed that a missing condition for showing the GIPHY button when porting the GIFs feature to core has been fixed in a PR. Sites still using the old theme component are urged to migrate, as the component will be archived soon. read more
J.Jaffeux reported that work is in progress to allow pinning chat messages for increased visibility, with Renato working on it. read more
#Feature
Matthewruzzi reported receiving “too similar” and “too quick” error messages when interacting with the Ask Discourse AI bot. HAWK and Awesomerobot clarified these are standard Discourse rate‑limiting messages, not specific to the AI feature. read more
#Plugin
Babylai introduced a new Discourse‑Telegram chat bridge plugin that provides real‑time, two‑way messaging between Discourse Chat and Telegram, with full support for Telegram forum topics, attachments, edits, and more. The detailed documentation covers setup, rate limiting, and known limitations. read more
Falco confirmed that the Resenha voice rooms plugin works correctly on mobile after a recent Discourse update, responding to a user’s report of issues on Android. read more
#Theme component
Merefield announced that Topic List Previews now renders masonry views in native CSS for supported browsers (Safari), with a fallback option for others, greatly improving rendering efficiency and battery life. read more
Lilly updated the Dismiss Admin Noise theme component with a new setting to auto‑dismiss pending flag notifications for admins who are not moderators, reducing notification clutter while still showing the review queue count in the sidebar. read more
Tradegood reported that double like buttons are appearing again on sites with reactions disabled. Davidb attributed this to the upcoming change enabling reactions by default and suggested opting out via the “Upcoming changes” admin page. Chapoi confirmed this is a regression when reactions are off. read more
Putty noted that German AI‑generated translations sometimes include raw JSON markup or unwanted translation metadata. Falco proposed a fix to the translation prompt and advised users with customised agents to update their prompt accordingly. read more
Awesomerobot confirmed a bug where translated category descriptions are not truncated to the first paragraph (unlike primary language descriptions) and pushed a fix that will apply the correct behaviour after the next Discourse update. read more
Moin suggested that the site setting solved topics auto close hours should be used as the default for the category‑level “Auto close solved topics” setting, so admins don’t have to manually change it for every new category. read more
Several Team members were active across the forum, providing support, announcing changes, and fixing bugs.
Lindsey posted the official announcement about removing the Uncategorized category, explaining the rationale and migration steps. read more
Davidb contributed to two discussions: confirming the fix for the GIPHY button in the GIFs core migration, and explaining the cause of the double‑likes bug (due to the upcoming reactions default change). read more and read more
J.Jaffeux updated the community on work in progress for pinning chat messages and replied to a question about the local storage approach for Discourse Reactions. read more and read more
Awesomerobot helped troubleshoot the Ask Discourse error reports and fixed the category description truncation bug for translated languages. read more and read more
Chapoi weighed in on the double‑likes regression and provided guidance on the Schedule Logo Change theme component and on preventing proprietary vocabulary from being translated by AI. read more, read more, and read more
Pmusaraj confirmed that a site submitted to Discourse Discover has been approved and is now visible. read more
Martin provided a detailed update on the granular group‑based permissions upcoming change, explaining how to use resolve_group_membership in themes and plugins, and noting that a database migration for the “everyone” group is planned. read more
Angus continued debugging a WordPress Discourse SSO avatar synchronisation issue, guiding the user through filter logging and checking plugin logs. read more
Falco fixed a translation prompt bug for German localisations and verified the mobile functionality of the Resenha voice rooms plugin. read more and read more
Yesterday, while some were busy rescuing puppies from a double‑like button invasion, the team tamed wild translations and turned uncategorized topics into model citizens — all without breaking a single leash.
Over the past 24 hours, the community has been buzzing with 115 new posts across 40 topics, accumulating 139 likes. Here are the top contributors by likes and posts:
Add setting to not show flag notification to admins who are not moderators — Lillydeveloped a theme component to silence flag notifications for non‑moderator admins, then opened a PR to make the change core (only notify Moderators). Mcwumblyweighed in on design choices, and Moinraised the issue of category moderators being left out. read more
Make it possible to translate custom sidebar links and sections — Southpawrevived an old request for translating admin‑added sidebar content. Natpromised it’s coming “soon™” with the content-localization system. read more
Use solved auto close site setting as default for category setting — Moinproposed that the global solved topics auto close hours setting should be inherited by new categories, reducing manual per‑category configuration. read more
Feature request: Limit topic translation to specific categories — Natshared a new PR that allows selecting category scopes (all, public, or inclusion/exclusion lists) for AI translations. read more
Allow customizing when posts are marked as read — Matthewruzzisuggested making the read‑marking threshold configurable, as the current implementation can mark unseen posts as read. Mcwumblypreferred tweaking the default or improving the “mark unread” feature. read more
This Meta Branded theme is special. Can I use it on my forum too? — Gidpraised the Meta branded theme’s design, but Moinnoted it’s not publicly available; you’d need to custom‑build or hire someone from Marketplace. read more
User‑agent: lfc‑discourse‑public‑crawler — Orionireported an aggressive AI scraper hitting their forum’s .json endpoints from Singapore. Awesomerobotsuggested it might be a fork of the archival tool, and Jagsterreminded that robots.txt is a polite suggestion. read more
Double Likes showing up for reactions‑disabled sites — Tradegoodreported a regression where a second like (heart) icon appeared. Chapoiflagged it as unintended for sites without reactions, and Davidbadvised opting out of the upcoming default‑enabled reactions via the Enable Discourse reactions by default setting. read more
How to prevent proprietary vocabulary from being translated by AI? — Zard_Wasked how to stop AI from translating product names. Chapoiexplained manual overrides, and Falcosuggested customizing the translation agent’s prompt to keep terms untranslated. read more
Désactiver la fermeture automatique d’un sujet après qu’il ait été résolu — Mireille_Coilhacasked how to disable the auto‑close timer on solved topics. Moin and Asaguided her to the category‑level setting, and Moinsuggested using the site‑setting as a global default. read more
Tags are not returned in api call — Irfandiwondered why tags were empty for regular users in the API. Supermathieconfirmed that hidden tags won’t be shown, and explained that by default tags are visible to everyone. read more
Emails failing to send, images not working, onebox issues after updating — Richiedescribed multiple failures after a rebuild, including image baking and email timeouts. After another ./launcher rebuild appeverything resolved, suggesting a transient sidekiq or service hiccup. read more
#Site feedback
Are you allowed to use the RSS feeds on Discourse Meta? — Matthewruzziasked if RSS feed usage violates the ToS automation clause. HAWKclarified that RSS is welcome and the ToS is aimed at abusive scraping, promising a future wording update. read more
Feedback on Discobot discoveries results on meta — Matthewruzzishared a hallucination by Discobot Discoveries (confusing RFC 5005 with WebSocket). Mcwumblyasked for concrete examples and is treating the topic as a feedback hub. read more
Improve convenience in setting of auto‑grid less than 3 images — Ethsim2requested a configurable threshold for auto‑gridding images. Mcwumblysuggested separating image‑group recognition from layout (list/grid/carousel) for a richer solution. read more
The Discourse team has been very active across many areas:
Awesomerobotexplained the update‑notification banner behaviour, fixed slug validation, linked a scraper to a known archival tool, and noted the touch‑vs‑no‑touch detail on the new composer dropdown.
Natconfirmed sidebar translation is coming, and opened a PR allowing category scoping for AI translation.
Martinupdated the granular‑permissions topic with documentation and plugin fixes, and noted that resolve_group_membership doesn’t yet apply to object‑setting groups type.
Davidbadvised opting out of the upcoming default‑reactions change.
Chapoiflagged the double‑likes regression, helped explain AI translation overrides, and noted a possible bug in the schedule‑logo component.
Falcosuggested customising the translation agent’s prompt and diagnosed the missing JSON response format in the German translation issue.
Yesterday, a scraper called lfc-discourse-public-crawler was blocked by a user‑agent rule, but given that Markdown bold text doesn’t work right after punctuation without a space, maybe the crawler should also avoid trailing full stops!
Over the last 24 hours, 121 new posts were created across 51 new topics, earning 134 likes in the returned dataset. The most active contributors by likes and posts were:
A curated selection of the most noteworthy discussions from the past day, grouped by category.
#Feature
Add setting to not show flag notification to admins who are not moderators – Mcwumbly opened the floor with three possible approaches (a _groups setting, simply notifying only moderators, or personal notification preferences). Lilly promptly submitted a PR for option B, only to close it after Awesomerobot raised concerns about forums with zero moderators. Moin pointed out the impact on category moderators, and Mcwumbly later expressed support for a more general user‑facing notification preferences interface, which Awesomerobot also advocated for with a mock‑up. Read more
Make it possible to translate custom sidebar links and sections – Nat gave a succinct “soon” on this long‑standing request, hinting that a solution may be arriving shortly. Read more
Integrate shared DataExplorer reports into the UI – One1 requested a dedicated page (or a link under “Reports”) for non‑admins to view DataExplorer queries shared with their group. Nat proposed a new entry in the user menu and also suggested group‑scoped sidebar sections as an alternative, while Moin pointed to an existing theme component that implements the latter. Read more
Configure number of different reactions visible below a posting – Mcwumbly mentioned that Davidb has been exploring options for letting users “join in” on existing reactions, mirroring what Chat already does—changes in this area may be coming soon. Read more
Improve convenience in setting of auto-grid less than 3 images – Ethsim2 wanted a configurable threshold for when image grids are applied. Mcwumbly proposed a richer model with list, grid, and carousel modes, and Chapoi favoured keeping the current threshold but adding a site setting. The conversation is still evolving. Read more
Add RFC 5005 support to Discourse RSS feeds – Matthewruzzi pointed out that currently only the latest 25 items are accessible via RSS and asked for RFC 5005 (Feed Paging and Archiving) to enable older posts through feed links. Read more
Emoticon to emoji conversion should be a user preference, not site‑wide – 0cjs argued that administrators shouldn’t force conversion on everyone. Moin raised technical challenges with quoting and wiki edits, but the discussion remained open. Read more
Feature request: Limit topic translation to specific categories – Nat merged a PR that adds a new setting type allowing admins to select which categories (all, public, or inclusion/exclusion lists) are translated, giving the best of both worlds. Read more
Update default FAQ language – Mireille_Coilhac asked how to make the guidelines appear in French. Moin explained the “Replace Text” button in the site text admin area, and Patrickemin was delighted to discover that button after years of use. Read more
Discourse AI: Need to Remove JSON Response to get Anthropic Sonnet 5 working – RGJ reported that they were using a version of Discourse (2026.1.5 ESR) that lacks the Disable native structured output option. Falco confirmed that newer models require up‑to‑date Discourse builds, and that the installer’s ACME handling is also being improved. Read more
#Self‑hosting
New installer works well, but one hostname gave me fits – Philh detailed a frustrating experience with a Let’s Encrypt rate limit (429) that silently prevented the site from coming online. He traced the failure chain from ACME to zero‑byte certs to nginx refusing to start, and requested that future installer builds surface such rate‑limit errors. Falco acknowledged the issue and pointed to a pending move to nginx native ACME support. Read more
#Site Feedback
Feedback on Discobot discoveries results on meta – Matthewruzzi found that searching for “RFC 5005” produced a hallucinated answer (claiming it was about WebSockets) and requested feedback buttons similar to those on Ask Discourse. Mcwumbly suggested improving the prompt to handle zero‑result cases better, and the topic now serves as a collection point for such examples. Read more
Are you allowed to use the RSS feeds on Discourse Meta? – HAWK clarified that the ToS language is aimed at abusive scraping, not reasonable use of RSS, and offered to update the wording to be clearer. Read more
Introducing the new Starter Plan! – Mkeys asked if the Starter Plan still exists. Mcwumbly confirmed it is now a legacy plan, and that the Free plan has taken its place as the entry point. Read more
#Theme Component
Move Language Selector to Sidebar Footer – Don published a new theme component that relocates the language selector from the header to the sidebar footer for logged‑in users, keeping the header uncluttered. Read more
Disabled Uncategorized shows in category dropdowns – Per1234 verified that the upcoming “Remove and replace Uncategorized” feature (controlled by a feature flag) resolves this bug. Instructions were given to enable the flag, delete the old Uncategorized category, and the dropdown issue disappears. Read more
The Discourse team has been actively engaged across many topics in the past 24 hours. Here is a summary of their contributions:
Mcwumbly launched the discussion on flag notifications for non‑moderator admins, refined options, and linked to broader notification preference work. He also responded to the Discobot feedback with a suggestion to improve prompts, clarified the Starter Plan’s status, engaged in the reactions‑visibility thread, and contributed ideas to the auto‑grid threshold conversation. Flag notification | Discobot feedback | Starter Plan | Reactions visibility | Auto‑grid
Lilly submitted a PR for option B of the flag notification feature (later closed after team discussion), provided technical feedback on the custom sidebar fields bug, and weighed in on the emoticon‑to‑emoji preference topic. Flag notification PR | Sidebar fields | Emoticon conversion
Awesomerobot argued against excluding admins from flag notifications by default, proposed a detailed user‑preferences UI mock‑up, and also updated the Beginner’s Guide to Themes with fresh screenshots. Flag notification opinion | Beginner’s guide
Falco acknowledged the installer ACME rate‑limit issue, pointed to an upcoming nginx native fix, and advised RGJ that using new AI models on old Discourse versions will cause problems. Installer response | AI Sonnet 5
Nat confirmed that translating custom sidebar links is coming “soon”, merged the PR allowing translation to be scoped to specific categories, and proposed UI changes for the DataExplorer reports integration. Sidebar links | Translation scope | DataExplorer UI
Davidb has been exploring options for allowing users to click existing reactions (referred to in the reactions‑visibility thread), fixed the likes pop‑up bug that stayed on screen after clicking an avatar, and corrected the messaging around simpler email subject lines. Reactions | Likes pop‑up fix | Email subjects
Martin engaged in the granular group‑based permissions for anonymous users topic, discussing how to handle disallowed groups in theme settings and plugin settings. Group permissions
Chapoi gave his opinion on the auto‑grid threshold feature, preferring the simpler site‑setting approach over a complex heuristic. Auto‑grid
Yesterday’s most dramatic moment was undoubtedly Philh finding himself in Let’s Encrypt rate‑limit jail, but like a true Discourse hero, he emerged with a detailed post‑mortem and a feature request that will save future self‑hosters from the same fate.
” on this long‑standing request, hinting that a solution may be arriving shortly.