Moin noticed tag pages suddenly looked “empty” because tags weren’t appearing in tag banners; awesomerobot confirmed it was caused by a data-availability change and shipped a quick plugin-side fix—already restored on Meta. read more
A Category Experts plugin crash during CLI user merges was traced to a validation failure; zogstrip linked the PR that fixes the plugin so merges won’t require disabling it first. read more
Self-hosters reported Cloudflare R2 backups failing on multipart upload with aws-sdk-s3 1.182.0 (undefined method 'downcase' for nil); pfaffman shared a proven pinning workaround, and the OP confirmed it solved the issue. read more
An intermittent but nasty iPad Safari composer jump-to-top (breaking upload buttons and resizing) was reported; after a bit of testing, the issue stopped reproducing for the reporter—still a useful breadcrumb if others see similar behavior. read more
A report flagged German translations injecting “AI commentary” / thought-process-like text into UI and even cross-language post viewing, raising concerns about translation quality and tone. read more
Enforcing 2fa can lock users onto security preferences without access to “how-to” guidance; supermathie pointed to customizing the relevant site text, and awesomerobot provided a theme-component approach to inject richer HTML/help content above the enforcement UI. read more
A site with an all-numeric tag found old-style /tag/6309 URLs returning a 500 instead of a clean 404/redirect—bad for crawlers and user experience; discussion centered on falling back more gracefully (or detecting numeric tag names). read more
The long-running question of what the “homepage” should be for doc categories got new traction: nickrsan explored adding a redirect-to-index option, but found a larger plugin rework underway and suggested integrating the idea there. read more
In the ongoing “let users control AI” thread, paco argued for a per-user discourse_ai_enabled equivalent so people can opt out of AI features even when site-wide AI is enabled. read more
#Announcements
lindsey announced a quality-of-life improvement for solved workflows: users Tracking/Watching topics in support categories now get notified when the topic is marked solved, with a preference toggle for those who want it off. read more
Feedback continued on embedding Discourse as a full comment system (embedding): Tris20 highlighted discoverability issues (the scrollbar and “reply” affordances), and mcmcclur worried some UI elements may now be too subtle (including missing timeline context). read more
The calendar-and-event subscription announcement thread surfaced a potential regression: an existing install no longer shows events in posts, suggesting a plugin-migration-related issue rather than the subscription URLs feature itself. read more
#Feature
A long-requested i18n nicety landed: emoji search now supports English and localized aliases, and in the process a bug fix trimmed the emojis.json payload by ~160KB. read more
More content-localization + tag UI polish: Moin asked for tag icons to appear correctly for translated tags in tag/category banners, after noticing parity gaps between English and translated tag displays. read more
Continuing the localization + tag UX theme, discussion on the tag icon component asked to support translated tags more completely, including in dropdown menus where some translated variants still don’t render as expected. read more
Support / Dev / #Theme_component (worth a quick look)
A hosted-support question: category-level moderation isn’t triggering the post_needs_approval email, even though posts correctly land in the review queue—admins are looking for a per-category solution without enabling global moderation emails. read more
Design/dev enablement: a user asked where to find Discourse design resources, and the accepted answer pointed them to enabling the built-in styleguide on their instance (plus a nudge toward Documentation > Developer Guides). read more
awesomerobot responded quickly to the missing-tag-banner regression, identified the upstream change that affected available data, and confirmed the fix was merged and visible again on Meta. read more
awesomerobot also provided a practical, copy/paste-ready solution for improving the locked-down 2fa enforcement experience via a theme component and renderBeforeWrapperOutlet, enabling admins to add links and richer guidance. read more
lindsey published the announcement that Tracking/Watching users now receive solved notifications in support categories using the solved plugin, including the “Want to turn it off?” preference guidance. read more
supermathie helped unblock MFA-enforcement messaging by pointing admins to the exact site-text customization path to tweak the “required to enable” copy. read more
Falco closed the loop on localized emoji aliases, linking the implementation PRs and noting the performance win (smaller emoji payload) that came along for the ride. read more
Falco also chimed in on a self-hosting migration collision story with some levity (and confirmation they’d recently re-done a failing migration), keeping the solved thread moving. read more
nat followed up in the localization/tag-icons conversation, clarifying a translation shown was intentionally manual/wordplay on their own instance—useful context when evaluating translated-label behavior. read more
davidb pointed to the core change that resolves group dropdowns not refreshing properly after new groups are created, effectively closing the loop on that bug report. read more
zogstrip acknowledged the Category Experts merge crash report and linked the plugin PR that addresses it so admins won’t need to disable the plugin during merges. read more
Sign-off: Between tag banners vanishing and reappearing (read more), emoji payloads going on a 160KB diet (read more), and at least one migration “buddy” showing a surprising amount of personality (read more), Meta had one of those delightfully chaotic-yet-productive days.
“Boosts” reactions-with-text experiment landed on Meta.lindsey introduced the new boosts interaction layer (read more), with follow-up discussion digging into naming confusion, moderation/flagging behavior, and whether boosts should merge into reactions long-term (read more).
Related: ActivityPub confusion got clarified (read more) and “convert too-short replies into boosts” was debated (read more).
Embedding Discourse as a full comment system: practical UX questions keep rolling in. People discussed how embedded pages map back into Discourse categories and reporting flows (read more), plus feedback that infinite scroll can hide the reply affordance in constrained embed heights (read more).
Related: example reference to tag strategy from “It’s time we talked about tags” (read more).
#Site feedback
ask.discourse.com outage report → confirmed + fixed. A quick heads-up that Ask was unreachable led to a team acknowledgement and resolution (read more, then read more).
Related: UX polish request on Ask’s “Back to Forum” link placement (read more).
Meta “content gardening hub” thread: more process-oriented tooling ideas. The ongoing experiment thread continued with suggestions for surfacing topics that likely need a fixed tag (via a staff/PR-linked topic filter pattern) (read more).
Related: discussion that prompted the filter referenced Contribute workflows in bug/#UX contexts (read more).
Looking for Discourse communities about public transit / urban design. A member asked for a directory of transit-focused forums running Discourse, and got pointed to discover.discourse.org and a couple known examples (read more).
Related: discovery as an ongoing need connects well with the broader “directory” idea mentioned in the same thread (read more).
Mistral embeddings compatibility issue: “dimensions” vs “output_dimension”.RGJ reported that Mistral’s embeddings endpoint rejects the OpenAI-style dimensions parameter and that Discourse currently requires it for saving (read more).
Related: prior how-to context for Mistral embeddings configuration (read more).
Numeric-tag URLs throwing 500s at legacy paths (crawl/SEO impact). A report highlighted 500 errors when old-style numeric tag URLs get crawled, with confirmation that a fix is planned while keeping /tag/name resolution stable (read more).
Related: broader tag discussions often come back to URL stability and discoverability (read more).
Ask UI: hide “Back to Forum” on the homepage. A small but sensible UX tweak request noted that the “Back to Forum” link is redundant on Ask’s homepage and should only appear when actually “in” a conversation flow (read more).
Related: Ask’s availability incident from earlier the same day (read more).
AI-generated German translation pages had “Thinking/Translate”-style artifacts; cleanup + agent update deployed. The issue was investigated, a formatting-tightening update shipped, and affected titles/posts were cleaned up (read more).
Related: the referenced prompt/feature change that may have contributed (read more) and the deployed fix PR link cited in-thread (read more).
Hidden comments “reappearing” after user edits: clarification of intended moderation behavior. A moderator reported that hidden posts re-entered the timeline after edits, expecting an approval gate; replies clarified that once posted, edits can reinstate visibility unless the post is deleted or “request revision” is used pre-approval (read more).
Related: moderation workflow differences between approval queue vs public timeline were central (read more).
Featured Topics via API: where to fetch them. A question about a native endpoint for “featured topics” was answered with a pointer to /categories.json when category pages are configured to include featured topics (read more).
Related: this fits into broader REST API usage patterns for topic discovery (read more).
Mail receiver trouble with self-hosted email: SPF rejection example. A “me too” update on a long-running mail receiver thread shared a bounce log showing SPF fail/rejection after migrating away from Gmail to self-hosted mail (read more).
Related: email deliverability pitfalls continue to be a common ops theme (read more).
Filtering topic lists: yes, you can include plain text search terms in the “topic filter” UI. A question about filtering by arbitrary text (without jumping into full search UI) was answered: just type the words after other filters to constrain the topic list (read more).
Related: examples in the reference thread show mixed filter + text patterns (read more).
Bitnami + polls error (“NoMethodError”): install path matters. A report in Chinese showed a stack trace hitting the poll serializer; replies quickly suspected Bitnami packaging (long unsupported/deprecated) as a root cause (read more).
Related: “Bitnami installations are unsupported” doc (read more) and the Bitnami container deprecation notice (read more).
iOS home-screen push notifications for self-hosted: behavior, fragility, and security tradeoffs. The push-notifications thread confirmed iOS 16.4+ “add to home screen” push can work, but uncovered a surprising “wipe keys on logout” line and the privacy rationale behind it (read more, plus read more).
Related: the code line discussion referenced in-thread (read more).
#Plugin
Discourse Daily Challenges: repo access weirdness (404 for some users) led to moving to GitLab. In the daily challenges plugin thread, a GitHub “account flagged/held” scenario caused intermittent 404s for others, prompting a migration to GitLab and updated links (read more, then read more).
Related: another similar “repo disappeared” anecdote referenced QR shareables (read more).
Pushover plugin got modernized for current Discourse versions. A long-running notifications plugin topic received an update: the plugin was updated/modernized to work again on recent releases (read more).
Related: notification ecosystem overlaps with other push-notification discussions (read more).
New guide: auto-provision users when SSO is enabled (skip the signup interstitial). A documentation topic explains how to enable auth skip create confirm to silently create accounts on first external login, plus optional overrides depending on identity provider behavior (read more).
Related: foundational SSO setup via DiscourseConnect (read more), plus common auth plugins like OIDC (read more) and OAuth2 Basic (read more).
lindsey introduced the Boosts experiment and invited feedback on positioning, notifications, and use-cases (read more).
zogstrip clarified boosts are not meant to reorder posts (just “reaction-like” metadata) (read more), joined the naming discussion (read more), and flagged likely install-path issues in the Bitnami/polls error report (read more).
j.jaffeux explained the intended “interaction hierarchy” and hinted at a longer-term unification path for boosts/reactions/likes so communities can choose the right layer(s) (read more).
awesomerobot elaborated on the intent (“morale boost” style), confirmed boosts will be optional, and shared moderation notes (watched words apply; AI scanning is possible but not on yet) (read more, read more). They also responded to a public-transit community directory question (read more) and agreed to adjust Ask’s custom “Back to Forum” link behavior on the homepage (read more).
Bas acknowledged the Ask outage report and followed up with confirmation that service was restored (read more, read more).
nat confirmed the team had eyes on the numeric-tag URL 500 issue and reiterated the commitment to /tag/name compatibility (read more). They also shipped/confirmed an AI agent formatting fix and cleanup for German localization artifacts (read more).
Falco confirmed iOS home-screen push support expectations and pointed to a problematic implementation detail that may be causing fragility (especially around admin impersonation/logouts) (read more, read more).
featheredtoast added important context on why “wipe push keys on logout” exists (preventing notification previews on logged-out devices), and proposed exploring better session/user binding for push subscriptions (read more). They also modernized the Pushover plugin for current Discourse versions (read more).
Yesterday’s theme: Meta got a “boost” of its own—between rockets, restored Ask uptime, and revived notifications plumbing, the site spent the day leveling up how it pings and praises people.
RGJ, Ed_S, ToddZ and Canapin continued debating what “boost-worthy” content is—and how Boosts interact with character limits and reply-clarity—in Testing Boosts on Meta (including UI clarity concerns about “reply-to-the-post-above” behavior: read more)
A new anti-abuse integration plugin landed, using an external API to detect/block VPN & proxy traffic at registration/login (with caching + fail-open options) in ProxyTracer: VPN & Proxy Blocker
RGJ flagged confusing wording when abandoning an edit (button says “Discard”, modal asks “discard your post?” even with no changes), proposing “Cancel edit / discard edits” clarity in “do you want to discard your post ?”
A question about “turning off the composer panel” turned into guidance about rich-text vs Markdown mode and preview toggles in Toggling off the composer panel, with a pointer back to the rich-text/Markdown switch UX shown in the composer toggle topic
Falco also confirmed a straightforward localization improvement for Meta itself: Ukrainian and Russian are planned to be added to Meta’s language switcher in Please add the Ukrainian or Russian languages.
mcwumbly engaged with new plugin experimentation and asked the “is it used in production yet?” question on a multi-team workspace concept in Workspace groups.
If yesterday was any indication, today’s Meta vibe is: keep it minimal… unless you’re adding Boosts, workspaces, and VP9 detection—then buckle up.
In the last 24 hours (2026-04-05 → 2026-04-06), Meta saw 37 new posts across 6 new topics. Source range: topics and replies in this report (e.g. read more).
(Per-post highlights include Moin’s guidance on TL3 tuning in Support (read more) and elmuerte’s new Ko‑fi plugin announcement in #Plugin (read more).)
Ed_S asked how to data-drivetrust-levels tuning so TL3 promotion matches the community’s size, and Moin pointed to user-level requirement breakdowns plus Data Explorer queries for identifying “almost TL3” users (read more, read more, plus the referenced query thread: read more).
Meta’s own TL3 thresholds came up as a real-world example: mcwumbly shared that Meta reduced TL3 cap requirements (topics viewed cap and posts read cap) after analyzing query results, and discussed upcoming work to roll out future default-setting changes more transparently (read more, referenced analysis context: read more, and the quoted settings-change topic: read more).
In an automation / ai support question, RGJ confirmed that enabling “Include personal messages” means AI triage can scan DMs between regular users too—and asked how the reporter verified DMs weren’t being scanned (read more, original question: read more).
A French-language calendar-and-event support question asked for a “cancel event” workflow that notifies all registrants without manually addressing each user in a message (read more).
Following up on structured-data / SEO work, Richie reported Google Search Console still flagging a missing text field under mainEntity.suggestedAnswer even after updating to the latest build, referencing prior investigation and fixes (read more, prior bug thread: read more).
A Chinese-language thread continued troubleshooting why all traffic appears to come from Cloudflare instead of end-user IPs—discussion centered on constraints introduced by a control panel setup and whether simplifying the stack would help (read more, continuation: read more).
#Plugin
A new plugin drop: Discourse Ko‑fi integration by elmuerte adds donation/subscription syncing via Ko‑fi webhooks, with rewards like badges and group membership; follow-ups covered currency limitations and anonymization behavior (read more, caveats: read more, maintenance/PR discussion: read more, maintainer response: read more).
In the experimental Discourse Suggested Edits plugin topic, sam confirmed a requested capability is “not implemented yet” but will be added; discussion immediately continued into category selection expectations (read more, follow-up question: read more).
The long-running Locations Plugin support thread saw a report that category maps stopped rendering after updates; merefield responded by inviting sponsorship and offering to investigate (read more, response: read more).
In ProxyTracer: VPN & Proxy Blocker, Moin cautioned that Safe Mode won’t help with Ruby-only behavior and raised skepticism about plugin packaging choices; the plugin author updated docs with server-side disable steps and removed redundant theme metadata (read more, author follow-up: read more, Safe Mode reference: read more, related admin recovery reference: read more).
A “mystery overlay” report turned out to be a rendering artifact: wuyuan saw gray dots/lines in the bottom-left; after initial UI guesses, bryce explained it’s likely the sidebar fade gradient and provided CSS to disable it via --d-sidebar-footer-fade (read more, clarification: read more, staff solution: read more, related component reference: read more).
“Clearing advice doesn’t actually clear it”: ted shared a PR concept to make specific dashboard problem-check notices ignorable (with an overview/undo surface), so admins can manage checks more deliberately (read more, original UX complaint context: read more).
A regression tied to the “simplified category creation” upcoming change: Moin reported that re-parenting categories/subcategories can silently reset category security permissions (re-opening posting to everyone); mcwumbly confirmed it looked familiar and that the team would dig in (read more, response: read more, referenced upcoming change: read more).
#Announcements
The ongoing “Testing Boosts on Meta” discussion continued with feedback about how boosts vs likes/reactions should communicate community value—Canapin argued boosts may be more “guestbook” than “signal,” and suggested visibility differences for authors vs readers (read more, Canapin’s perspective: read more, topic root: read more).
#Site feedback
In the “collaborative content gardening hub” experiment thread, Moin noticed category descriptions and/or restrictions no longer matched reality for plugin/theme posting, and mcwumbly connected it to category re-parenting permission loss—linking it directly to the new security-reset bug report (read more, staff reply linking bug: read more, cross-link to bug: read more).
A localization request thread about adding Ukrainian or Russian languages continued, with Denis_Kovalenko asking which translation model might be used as the request progressed (read more, thread root: read more).
#Self-hosting
In a solved “plugins not functioning due to CORS” thread, TomoftheFog added a new symptom: some users can’t see avatar images when the Preformatted Text markdown button tries to load highlight.js and hits a CORS failure—flagging it for others in case it’s related (read more, thread root: read more).
In “How minimal is your forum?”, Ed_S reflected on tag value (SEO vs maintenance burden) and how permissive tag creation at TL2 may contribute to tag sprawl—then spun that into a deeper TL3 threshold question (read more, follow-on TL3 tuning topic: read more).
A previously opened support topic about “official components” breaking after an update was confirmed resolved by Stephane_Roy, serving as a quick “good news” datapoint amid other upgrade-side effects (read more).
mcwumbly engaged in Support to share Meta’s real TL3 requirement adjustments (notably reduced cap values) and to discuss improving how Discourse communicates/rolls out default site-setting changes (read more). He also acknowledged and connected reports of category permission loss after re-parenting, both directly in the bug report (read more) and while replying in the content-gardening experiment thread (read more).
bryce jumped into ux to diagnose the “bottom-left overlay” as a sidebar fade gradient artifact and provided a targeted CSS workaround using --d-sidebar-footer-fade (read more).
sam replied in the #Plugin area on the experimental suggested-edits effort, confirming a requested feature isn’t built yet but is planned (“will add”) (read more).
If yesterday proved anything, it’s that Meta can debate boosts vs likes while simultaneously chasing down mysterious gradient dots—peak Discourse multitasking.
A new theme component announcement promises rich hover previews for internal topic links, with chapoi immediately requesting a clearer preview (screenshots / demo) in Topic Hover Cards
Troubleshooting the official sidebar theme toggle: awesomerobot helped narrow down why the sidebar wasn’t showing (including confirming user-selectable themes are enabled) in Sidebar Theme Toggle (officialsidebar)
#Plugin
A new “lightweight moderation” concept landed as a plugin: “mini-mods” can manage categories/tags/topics without full moderator power, described in Discourse MiniMod
The long-running ratings plugin thread resurfaced after functionality “vanished” due to widget/component changes; a fix PR was proposed and RGJ noted a modernized fork underway in Topic Ratings Plugin (pavilion)
Meta’s own information architecture is under review: mcwumbly asked what “community-building” discussions should look like (and whether category restructuring is helping or hurting), kicking off a broader direction-setting thread in Encouraging discussion about building and managing communities
chapoi requested better previews for a newly-published theme component in Topic Hover Cards, and clarified Horizon’s current compatibility priorities (and constraints) in Horizon Theme.
manuel continued the ongoing icon set housekeeping conversation, pointing folks to the official lucide set and suggesting documentation/first-post updates in Alternative icons.
Yesterday’s vibe: may your semicolons stay safely inside quotes, your RSS feeds actually honor exclude_tag, and your nested replies keep their shiny new Pin button.
Provided detailed theme/icon UX feedback in Meta Branded theme rebuild (icon mapping, small glyphs, click targets).
A visible through-line today: UI polish (icons + theme), “findability” improvements (bookmarks), and the perennial balancing act between platform evolution and downstream stability (deprecations). See: Meta theme rebuild, Easier access to bookmarks, and Deprecating .hbs.
Interesting Topics
#Site feedback
manuel shared a deep dive on the second iteration of the rebuilt Meta theme—new implementation, Lucide icon adoption, palette restrictions, and early direction-setting around customization (and “Blocks”) in Rebuilding the Meta Branded theme. Follow-up feedback covered icon mapping gaps, tiny list icons, and a desktop click-target overlay issue for the logo in post 8 and post 9.
#Theme component
The icon work spun out into a dedicated, installable component: manuel published the repo + install guide for Discourse Lucide Icons, while early testers flagged confusing glyph metaphors (e.g. reply/back-jump reading like “share”) in post 4. Related context: the older “where to find icon sets” discussion in Alternative icons.
Boosts feedback kept rolling in, with concerns about visual noise and UI density in Testing Boosts on Meta and even “reactions to boosts” as a half-joking extension idea in post 65. (Related feature UX suggestions appear in the standalone request below: Some ideas about discourse-boost plugin.)
#Feature
A practical mobile UX request for Boosts: fold/compact long boost lists and consider adding easier “quote/reply” affordances, discussed in Some ideas about discourse-boost plugin with chapoi suggesting consolidating into the main boosts feedback thread in post 5 (tying back to Testing Boosts on Meta).
Bookmark indicators on mobile sparked an unusually nuanced semantics debate: should the topic-level bookmark glyph change if only some posts are bookmarked? See the UX back-and-forth in Unable to tell bookmarks exist in footer on mobile, including sam’s “users don’t care about the nuance” framing in post 17 and chapoi’s preference to keep topic-bookmark meaning strict in post 10. (The overall feature announcement context is in Easier access to bookmarks.)
Deprecations hit a nerve: LeoDavidson described the maintenance burden and intent to stop maintaining plugins in Deprecating .hbs file extension in themes and plugins, with david outlining “deprecations + upgrade paths” rationale and a responsible archival approach in post 14. The parallel thread for JS filenames includes david’s justification focused on tooling and education in Deprecating .js.es6.
Localization surfaced two separate issues: anonymous users seeing mixed-language title/body behavior when using ?tl= in Localisation bug for anonymous users with ?tl=, and logged-in users frustrated that translation-disable doesn’t persist across devices/time in User disables translations, but they keep coming back (with nat clarifying current “local storage for 30 days” behavior and proposing persistence in user settings in post 2).
POP3 polling reliability: a site operator considered daily restarts as a workaround for sporadic inbound email pickup, but the thread ultimately pointed to the POP3 server error and recommended direct delivery instead in Auto-restarting once a day via cron? with the direct-delivery guide linked in post 2. Related earlier context was referenced from Discourse stopped polling my pop3 server (read more).
Falco jumped into calendar subscription UX limitations with the key question—“how can we do that programmatically?”—in The webcal URL is incorrectly passed…, helping steer the discussion toward what’s actually feasible in ICS generation.
Sign-off: Between Lucide strokes, bookmark hopscotch, and Boost-related “visual noise” debates, Meta spent the day doing what it does best—turning tiny UI details into tomorrow’s improvements.
Event creation flow continues to be a friction point; the team acknowledged active work (but no ETA) toward simplifying the event creation pathway in Single click activation of the Create Event modal.
Split-topic “small action” posts display link text based on a title snapshot, prompting discussion about whether those action posts should auto-update when titles change in Link in “Split this topic” mini post.
A self-hosted admin-facing failure tied to Git operations (“Gitutils.try_git”) appeared for a China-hosted install, with discussion focusing on templates/versioning/rebuilds in Gitutils.try_git报错.
#Site feedback
Meta’s official plugin topics may be showing outdated hosting-tier availability banners (and even outdated tier names), prompting a needed audit of the boilerplate across plugin topics in Inaccurate plugin availability notes on meta.
If yesterday had a theme, it was “tiny UI cues, big usability wins”—may your bookmark icons be legible, your calendars properly named, and your ampersands forever unescaped.
In the last 24 hours, Meta saw 79 new posts across 11 new topics, with conversations spread across active threads like Boosts feedback and a deep-dive infrastructure write-up on backups and uploads (read more).
Self-hosters continued chasing tricky edge-cases like S3/CDN interactions and broken codeblock bundles (read more).
Plugin authors discussed performance tradeoffs for IP allowlisting in Geo Blocking (read more).
Mobile UI papercuts kept coming: hamburger menu behavior (read more) and tag truncation/blank lines (read more).
Localization enthusiasm continued, including appreciation for new language options (read more).
Interesting Topics
#Announcements
Discourse’s “Boosts” experiment continued to spark strong opinions: hellekin worried it could encourage low-signal reactions (read more), while mcwumbly argued for experimentation and team autonomy (read more), and jordan.vidrine emphasized moderation controls and “fun is okay” framing (read more).
Calendar subscription URLs are landing well, but discoverability and “corporate link/logo” concerns remain: feedback suggested moving subscription closer to the calendar UI instead of burying it in preferences (read more).
#Site feedback
Meta’s plugin availability notes may be misleading, and the thread explored ways to avoid keeping multiple sources in sync—potentially linking directly into the pricing comparison table (read more), with follow-ups about edge cases for plugins not on discourse.org (read more) and a small scroll-margin improvement shipping quickly (read more).
Work on the Meta branded theme redesign (meta-redesign-2026) rolled forward, including a clearer explanation of how the Blocks API differs from plugin outlets—framing Blocks as “layout frames” for more predictable customization (read more).
A small UX inconsistency was spotted in category listings: muted categories appear without descriptions, and folks questioned whether that’s intentional or an oversight (read more).
The collaborative “content gardening hub” experiment sparked workflow questions, including reopening/adjusting who can post in documentation-related index threads; the team temporarily unlocked a thread to keep progress moving (read more).
A new technical blog companion topic told the story of how massive uploads (and a certain sitcom-related dataset) ballooned backups and broke assumptions about ext4 hardlinks—prompting appreciative “more of these technical posts” feedback (read more).
A Ticket System incident turned into a great “settings interaction” postmortem: RGJ traced unexpected TL0 visibility to the Private Topics plugin + permitted-groups configuration, and confirmed the fix (read more).
A concerning moderation queue oddity: multiple old posts (including PMs) were suddenly flagged as spam by the system, with one entry showing Is this post or undefined?—a thread to watch if others see similar log-timeouts + flag anomalies (read more).
The backup progress UI occasionally shows “no logs yet” even when backups succeed; switching tabs makes logs appear, suggesting a front-end refresh/race condition (read more).
On mobile, long category/tag lines can cut off tags without ellipsis and even create awkward blank-line punctuation; examples were collected for tricky long-topic metadata cases (read more).
Structured data / rich results work continued: one remaining schema validation issue was reported around missing fields under mainEntity.suggestedAnswer, and davidb stepped in to investigate further (read more).
#Theme component
A new theme component provides a clean, configurable “Print to PDF” button with controls for where it appears, what it includes, and optional table-of-contents behavior (read more).
The official “Customize new topic button text” component briefly showed both the old and new button; a fix PR was opened and confirmed working for reporters (read more).
#Self-hosting
A migration-heavy self-hosting question: how to default “Watching” for an Announcements category via trust-level groups without staged users inheriting it—seeking a sane pattern for imported (not-yet-activated) accounts (read more).
mcwumbly weighed in on product direction and team autonomy around the Boosts experiment—supporting decentralized exploration even when a feature isn’t universally appealing (read more); they also engaged on how to reduce sync burdens in plugin availability documentation (read more).
jordan.vidrine clarified how Boosts can be moderated (including deletion/admin controls) and argued that not every feature must be purely pragmatic if it’s optional and fun (read more).
ducks published the companion discussion for a new Discourse blog entry on backup generation, large uploads, and ext4 hardlink pitfalls (read more).
manuel explained how the Blocks API changes customization ergonomics compared to PluginOutlets, emphasizing predictable layouts and reusable conditional logic handling (read more).
gerhard resolved a translation regression where emoji/icon handling in Crowdin-to-GitHub locale updates caused issues; the fix landed in updated PRs (read more).
zogstrip helped route the translation/onebox issue to the right eyes by looping in gerhard for a quick diagnosis (read more).
chapoi answered a permissions question about who can create chat channels, confirming it’s restricted to admins/staff (read more).
davidb acknowledged an open structured-data bug report and committed to follow up with investigation notes before closing the loop (read more).
david tracked down a self-hosting edge case: highlight.js bundles weren’t handled properly under certain S3/CDN configurations, and a core PR was linked as the fix (read more).
derek confirmed a UI improvement (scroll margin) related to anchor-linking into long pages, smoothing the experience discussed in the plugin availability notes thread (read more).
Yesterday’s moral: whether you’re debating Boosts, chasing phantom backup logs, or hardlinking 377GB of “Friends,” Meta always finds a way to keep things lively.
The Meta redesign feedback thread picked up more mobile layout critique: Canapin argued the new Meta-branded theme’s spacing “crushes” horizontal content on narrow screens and called out small visual details (like the slightly oblate top-left icon) (Rebuilding the Meta Branded theme…).
Legacy Windows support expectations surfaced again: Andro asked for a clear list of supported Windows versions, and the thread converged on “Discourse supports what modern browsers support,” with Falco emphasizing that unsupported-by-Microsoft Windows versions aren’t supported by Discourse either (What versions of Windows are supported?). The discussion also referenced the “dropping old browsers” announcement (read more) and the general legacy browser policy context (About support for legacy browsers).
An authentication outage affected the OpenAI developer forum: EricGT reported failing logins with an OIDC authorization error, Lilly confirmed the same symptom, and sam escalated it to internal contacts (OIDC Error for OpenAI Discourse forum).
Category moderation permissions were clarified: haydenjames asked whether adding a group as category moderators applies to every member; Moin confirmed it does, and recommended a dedicated moderator group (Single category moderation). The question was rooted in older guidance around group review/moderation patterns (read more).
The Quote Callouts component had a locale-specific JS error: nesges reported an issue that only occurred under German translation, and Arkshine shipped a quick fix via a PR and follow-up guidance (Quote Callouts). The thread also included a neat “zero-width space” workaround to create icon-only/no-title callouts (read more).
Versatile Banner ran into a real-world dependency problem: pacharanero warned that the component’s default background image is hosted on Imgur, which is now inaccessible in the UK, making first-time installs look broken and prompting a suggestion to switch defaults to a non-blocked host (Versatile Banner).
Maintenance realities for older theme components showed up again: in the Left side hamburger menu on mobile thread, Lilly shared a CSS approach (noting the deprecation of /mobile theme paths), and featheredtoast acknowledged the component’s assumptions were impacted by the move away from mobile/desktop view separation (read more). That change itself was recently celebrated elsewhere as a big win (Improving automatic switching of mobile/desktop modes).
The Modernizing the Foundation theme project got a status update: after questions from Lilly and Canapin about timelines and selector scoping, jordan.vidrine explained the plan to merge smaller items into core while keeping bigger changes (buttons/header/font rendering) behind a feature flag for now (read more).
#Site-Feedback
Release communication/traceability came up: jrgong requested that feature/bugfix announcement topics include a version number (especially helpful for managed hosting with slower update cadences), and RGJ pushed back on the “just run tests-passed” expectation for plugin/theme-heavy sites (Feature/Bugfix announcement topics should include version number). The request used a recent chat pinning announcement as an example (read more).
#Feature
Topic merges and user expectations: ganncamp asked what notification a user receives when their topic is merged into another, and how to avoid disorienting people (or cluttering incident threads). Moin confirmed there is a “post moved” notification and suggested an official notice to explain context (What merge topic notification does the user get?). This ties into a broader request for merge “breadcrumbs” in the target topic (Request: add breadcrumb to merge target topic).
awesomerobot engaged directly on mobile composer complexity, asking the community for concrete, actionable proposals to simplify the default UI (toolbar toggle, close vs delete affordances, tag input collapsing) in the main thread (read more). They also acknowledged and followed up on a theme-related draft issue report in the “reddit-ish” theme thread (A reddit-ish theme for Discourse), and confirmed a translation string issue in Solved would be fixed via PR (Noch ein nicht übersetzbarer Text: “Solved”).
Falco clarified the practical stance on old Windows support (and tested alternative browser forks that still work) in the Windows support topic (read more). They also flagged a self-host performance/upgrade situation as rooted in a deprecated plugin that should be removed (Forum lagging after reboot + upgrade…), and answered calendar/event feature context earlier in the month (referenced again in discussion) (Add to Calendar .ics request).
sam escalated the OpenAI developer forum login/OIDC error to internal contacts, signaling active investigation on the hosted-support side (read more). The thread itself includes corroboration that the issue affected multiple users (read more).
jordan.vidrine contributed both product/process guidance (how to frame actionable UX feedback) in the mobile composer discussion (read more) and provided a concrete project status update for the Foundation modernization effort, including what will remain feature-flagged (read more).
featheredtoast acknowledged that the Left side hamburger menu on mobile theme component is behind on updates and that the move away from /mobile//desktop assumptions broke parts of it, while pointing toward a CSS grid approach for reordering items (read more).
supermathie dug into why Windows 7 users might fail to load Discourse even with “supported-ish” browsers, suggesting it could be down to modern TLS defaults and recommending an SSL Labs client test for diagnosis (read more).
Yesterday’s vibe: if your mobile tag selector won’t close, your composer keeps freezing, and your Windows 7 users are emailing “it doesn’t work,” at least you’re having the same day as everyone else on Meta.
A new-site creation flow hung at “Almost there…”, with NateDhaliwal reproducing and pmusaraj later confirming a fix in “Stuck on creating new account” (free-plan). The original reporter referenced a similar past thread while troubleshooting — read more, status update, related
bondero highlighted a tricky notifications problem: staged users can’t easily unsubscribe, raising the question of whether staged users should receive “Watching” emails in “Exclude staged users from Watching?” (staged-users) — read more
Banner workflow friction after upgrades continued: hellekin described losing a banner topic and difficulties keeping staff-only discussion alongside public banners, tying it to restricted-category banners; Moin suggested mitigations like splitting posts or hiding revisions and pointed to scheduling as an alternative — read more, restricted banners context, scheduling reference
rogerreed offered practical guidance for incoming email on cPanel—filter by “To” address, use a dedicated address like replies@…, then forward appropriately—in “How to configure c panel email server to work with incoming emails” (emailhosting) — read more
NateDhaliwal reported Meta intermittently loading older topics first (then showing a “new/unread topics” prompt), plus “New replies” counts that linger and later vanish, in “Opening forum goes to topics 1 day ago, not recent topics” — read more
A potential cache-key mixup was documented where /favicon/proxied appears to return the same image for different URLs, with concrete reproduction URLs provided in “Bug: /favicon/proxied returns the same image for different URLs (cache key issue?)” — read more
In a French-language report on category settings, NateDhaliwal suggested tagging to clarify whether it’s actually a calendar/events-related problem in “Problème dans les paramètres avancés des categories” (calendar-and-eventcategories) — read more
A styling/placement nit: Moin questioned whether the expand/collapse control for the accepted-answer block belongs below the content rather than in the header (and compared it to quote controls) in “Move expand/collapse arrow of accepted post in OP below” (solved) — read more
Canapin spotted what looks like inverted tooltip logic for the translation toggle (original vs machine-translated states), and Moin noted it’s a known bug that can sometimes be “fixed” by refreshing in “Logic flip in post translation button tooltips?” (content-localization) — read more, workaround note
Localization detail: Moin flagged that “Key” and “Value” strings inside the Wrap modal aren’t translatable, and included direct code pointers in “‘Key’ und ‘Value’ aus dem Wrap Modal sind nicht übersetzbar” — read more
#Site feedback
Release communications consistency came up again: jrgong argued that announcement topics (features/bugfixes) should more explicitly include version numbers, and suggested better linkage between the releases page and announcement topics in “Feature/Bugfix announcement topics should include version number” — read more
#Feature
In “Allow category moderators to create subcategories” (category-moderators), alanr asked whether this exists, whether it can be sponsored, and what options are available; NateDhaliwal pointed to Marketplace hiring or (for Enterprise hosting customers) paid Discourse build services, and ars18 suggested an existing related tool — read more, options, related tool
Plugin/core behavior boundaries were discussed in “Discourse llms.txt Generator Plugin” (ai): kaktak said they’ll ship an update so core doesn’t override the plugin’s intended behavior, reinforcing the “plugins should be able to override” philosophy — read more
A filtering feature request for WP Discourse: angus asked clarifying questions about whether there’s a post-level signal that matches “exclude comments with a specific tag,” contrasting it with the existing inclusive “Only Import Moderator-Liked” setting in “Wp-discourse feature request - do not show comments with specific tag?” (wp-discourse) — read more
pmusaraj responded quickly to a signup outage, acknowledging technical issues and later confirming resolution in “Stuck on creating new account” — initial response, fix confirmed
mcwumbly chimed in on theme component compatibility, noting the Kanban component should work well with Horizon in “Kanban Board” — read more
If yesterday was any indication, today’s going to be smoother: fewer “Almost there…” signups, and more logins that just work.
61 new posts across 6 new topics in the last 24 hours, with lots of hands-on troubleshooting and polish discussions (e.g. new theme components like Highlight to Search and UX tweaks like the share modal copy button).
renato — 1 post / 2 likes (debugging the composer “jumping cursor” report) read more
sam — 2 posts / 0 likes (driving an RTL title-field fix forward) read more
Interesting Topics
#theme-component
NateDhaliwal published “Highlight to Search”, a theme component that lets users highlight text inside a post and instantly search for it (either via Discourse search or an external engine) — a neat “micro-productivity” win for readers and moderators alike read more. For setup references, see theme/component install instructions and the themes beginner guide.
nathank released “Upcoming Events Extra Buttons”, adding configurable Subscribe and (optionally) Create event buttons to /upcoming-events, aimed at reducing friction for event-heavy communities read more. Related background: discussion around event UX expectations continues in calendar threads like closed events visibility and broader event workflow ideas read more.
The long-running Kanban Board component got another round of “is it broken on Horizon?” testing: Lew_Grothe reported it not working, Arkshine suggested basic checks (component attachment + console errors), and nathank shared CSS to widen the Kanban layout under Horizon’s tighter center column read more.
In Discourse Lucide Icons, cuo_wu hit an issue where the calendar-heart icon wouldn’t render even after adding it to custom SVGs, and nathank clarified that the “extra icons” mechanism is Font Awesome 6-oriented—Lucide additions should follow the custom SVG replacement approach read more, with the canonical how-to here: Replace default SVG icons in a theme.
User Field Prompt got a documentation/UI mismatch callout: Moin noted the first-post screenshot is now misleading because the field title/description display differs from what admins see in preferences, suggesting an update for less surprise read more.
Banner Featured Links support continued in French: gilles wanted the buttons shown beyond the homepage, and Arkshine pointed to selecting the right plugin outlet (and checking “URL must contain”), recommending the Developer Toolbar to discover outlet placement read more. The referenced helper tool: Introducing Discourse Developer Toolbar.
A fresh RTL regression report: topic title input stays LTR on RTL sites. Nima1 described how dir="auto" causes empty inputs to render LTR (cursor/selection/placeholder feel wrong), and sam confirmed it’s not solvable with CSS alone—proposing a markup behavior change (default RTL until typing begins, then switch to auto) with a linked PR read more. Cross-reference: sam noted this also covers older reports like “Titles placeholder in New topic is not RTL”read more.
The composer cursor “jumping around” thread resurfaced with a video showing the editor snapping position during longer edits; renato suspected it was actually the Markdown split-preview composer (not ProseMirror) and asked for cross-instance reproduction steps to narrow it down read more.
Cooked error after translate: cuo_wu reported that translating content (with SC language enabled) seemed to trigger cooked/format issues; Moin traced at least one culprit to malformed table pipes—tweaking the English source fixed the German translation output too, suggesting translation pipelines can be less forgiving than the main renderer read more.
On mobile, Canapin suggested the share modal should place the Copy button on the same line as the URL input (better thumb reach, less wasted vertical space) read more. This fits neatly alongside other Meta-mobile layout nits being tracked in the ongoing theme work (e.g. leaderboard overflow on mobile) read more.
Closed events don’t display in the upcoming-events calendar: Ethsim2 argued that “Close event” has become a practical way to hide items without BBCode hacks, and asked that closed events remain visible—or alternatively that Discourse add a separate “Delete event” (or rebrand “Close” to “Hide”) to clarify intent read more. Adjacent calendar discussions keep circling back to workflow and visibility: recurring-event topic creation expectations read more and “Add to calendar” integration requests read more.
Notification count persistence: sixty4bit described the current behavior (count clears after opening the avatar menu) as actively harmful for low-volume-but-critical PM workflows (e.g. support inboxes), arguing it causes missed follow-ups and extra clicks read more.
A new Discourse ID login problem report (Chinese): users saw a “redirect uri is malformed or doesn’t match client redirect URI” error; NateDhaliwal pointed to regenerating credentials and the known domain-change fix path, then continued troubleshooting when only admins could log in read more. Related reference topic: Changing domain names prevents Discourse ID from working.
#plugin
Topic Ratings Plugin got a practical compatibility win: Arkshine explained a merged PR that removes legacy widget references so the plugin works again, and confirmed updating the plugin should resolve the errors for affected sites read more.
In Telegram Notifications Plugin, scavin asked the key maintenance question—whether the plugin is still actively supported—flagging an evergreen concern for production admins weighing long-lived integrations read more.
sam focused on fixing RTL title-field directionality by explaining why HTML dir="auto" yields LTR when the input is empty, proposing a behavior change (default RTL until the first character, then switch to auto), and linking an implementation PR for review read more. sam also connected the fix to prior RTL UX reports so it lands as a comprehensive improvement rather than a one-off patch read more.
renato investigated a renewed report of the composer/editor “jumping” issue, noting the captured behavior appeared to be in the Markdown split-preview composer (not ProseMirror) and requesting reproduction confirmation across multiple Discourse instances to isolate scope and cause read more.
If today’s Meta had a theme, it’d be: highlight it, copy it, and make sure it doesn’t accidentally turn LTR while you weren’t looking.
Lilly flagged that admin post menu hover-tooltips are missing/mismatched (including incorrect labels like “unhide” showing up for unrelated actions), with a core fix quickly spun up by awesomerobotread more.
A mobile/UX refinement request asked for the share-link modal “copy” button to sit on the same line as the URL input, and awesomerobot followed up with a PR that also addresses adjacent layout issues read more.
In a localization UX snag, the “Key” and “Value” strings in the Wrap modal were reported as not translatable; awesomerobot confirmed it as an oversight and linked a core fix PR read more.
Calendar UX expectations came up again: a user argued that closed events should still display in the upcoming-events calendar, and the thread continues to tease apart whether “Close” should behave more like “Hide” (and how much retrospective visibility matters) read more.
The ongoing transition away from legacy theme/plugin templates got more nuance: manuel weighed in on deprecating the .hbs extension, arguing that Discourse is closer to an evolving platform ecosystem than a “stable OS API” model—so versioning + clear deprecation windows matters most read more.
#Self-hosting
A post-upgrade outage (“Failed to initialize site default”) ended up being caused by a known landmine: a broken discourse-multilingual plugin. The fix was to remove it and rebuild, with a direct pointer to the plugin topic read more (related plugin thread: read more).
#Theme component
A new component proposes a workflow tweak: make “Shared Draft” the default New Topic action, replacing the button text and preloading the composer for staff collaboration workflows (shared-drafts) read more.
In “Highlight to Search” (search), support questions turned into a mini guide: external search can be switched by changing the configured search URL (e.g., to Bing), and the thread also surfaced other search-related components people may want to combine read more (see also Baidu search and DuckDuckGo search suggestions).
The “Discourse Lucide Icons” component thread had a meta problem of its own: it’s hard to “respond to a Boost,” and the discussion also highlighted gaps in how changes/features are documented/discoverable via search read more.
A long-standing, currently broken theme component (“Video Upload to YouTube and Vimeo”) got a pulse check: work has restarted and Vimeo is reportedly already functioning again—next steps are to get the full pipeline back into shape read more.
A puzzling navigation issue: some users report that opening the forum shows topics from 1–3 days ago instead of recent, with unread counts that don’t align with what they’ve actually read—possibly related to state restoration when tabs go inactive read more (potentially related: read more).
Another composer-adjacent bug report: hashtag autocomplete triggers browser console errors in safe mode (“generateIconHTML” undefined) and behaves differently when plugins are enabled (“dataSource is not a function”), suggesting a core JS edge case or an integration mismatch (hashtag-autocomplete) read more.
A smaller follow-up confirmed resolution of a translation/rendering issue: a “cooked” error after translate was reported and then marked fixed by the reporter (ai, dynaloc) read more.
Incoming-email topic creation hit a common snag: HTML emails being trimmed/treated as quoted content, resulting in only the first lines appearing in the created topic. The thread is moving toward debugging with a full raw email + post source to see what Discourse is detecting read more.
A Discourse ID login support thread (in Chinese) wrapped up after troubleshooting: the poster ultimately reinstalled and confirmed the issue resolved, after configuration checks around login settings (discourse-id) read more.
Multilingual admin customization got a pragmatic solution: a user shared a small plugin approach to localize badges and groups by adding strings under config/locales and naming badges using translation keys (badges, groups, translation) read more.
For sites that create lots of staged users, one admin outlined how they stopped staged users turning the site into a “spamming machine”: force staged users to TL0, set new users to TL1, and use TL1+ category watching (staged-users) read more.
#Announcements
The “Testing Boosts on Meta” thread continued, with a reminder to keep feature discussion focused: product feedback can stay fun without drifting into unrelated heavy topics, and there’s interest in giving communities more expressive options over time read more.
“Upcoming Changes” clarity improved: auto-grids for image uploads are now “Stable” for most sites, but staff emphasized that Stable doesn’t always mean “setting will be removed”—opt-out remains and “Permanent” status won’t be applied in this case read more (background on the system: read more).
#Plugin
The Telegram notifications plugin had a quick maintenance win: a .hbs deprecation warning was addressed, with a maintainer confirming the deprecation should now be resolved (ties back to the broader .hbs deprecation announcement) read more and read more.
The Landing Pages plugin (pavilion) received a compatibility update for current stable (2026.1), with follow-up review comments already landing in the thread read more.
A plugin vendor/support thread noted an integration issue: ProxyTracer + Cloudflare WARP returning “unknown error” instead of a blocked message, suggesting either detection gaps or error handling needing refinement read more.
#Feature
AI agent behavior design remains a hot spot: one request asked for AI personas/agents to respond only to @mentions, not to replies to their posts (ai, ai-bot), and discussion pointed to workaround tactics read more (related workaround thread: read more).
In “New AI Persona Editor for Discourse,” there’s renewed interest in configuring a persona to act like a “standard chat AI” (i.e., not searching Discourse content or being aware it’s embedded in a forum context) read more.
awesomerobot moved several UX fixes forward: they opened a fix for the admin post-menu hover-tip mismatchesread more, confirmed and patched the Wrap modal translation gapread more, and posted a PR-driven fix for the share modal copy-button layoutread more.
manuel added strategic context to the .hbs deprecation conversation, emphasizing clear versioning + deprecation notices + migration windows as the sustainable model for a live ecosystem read more.
Falco unblocked a broken self-hosting upgrade by identifying the culprit as a broken customization plugin and recommending removal + rebuild, which resolved the boot issue read more.
david confirmed a maintenance fix in the Telegram notifications plugin ecosystem, noting the .hbs deprecation warning should now be resolvedread more.
jordan.vidrine helped steer the “Boosts” discussion back toward productive product feedback, discouraging unrelated real-world digressions so the feature conversation stays useful for communitiesread more.
martin clarified how “Upcoming Changes” statuses work in practice, noting that Stable ≠ forced permanent, and that “enable auto grid images” is expected to remain opt-outread more.
supermathie jumped into email-in support, explaining that missing content is often due to Discourse detecting parts of the email as quoted/previous-email content, and requested a raw email + post source for accurate diagnosis read more.
That’s a wrap—may your tooltips stay accurate, your boosts stay on-topic, and your hashtag autocomplete stop yelling at your browser console.
What drove the day (threads with lots of “gravity”): mobile composing pain points (see read more), review queue / moderation workflow questions (see read more), and a cluster of reviewable/insights bugs (see read more).
Ed_S highlighted how cramped mobile composing can get (down to one visible line), and the discussion expanded into discoverability and defaults for the toolbar—now being actively reviewed by staff in the ongoing thread about the “2026 Discourse experience” (composermobile) read more.
A small-but-daily-friction point: the sharing modal UI and how the copy button aligns alongside the URL (especially when sharing posts vs topics), with clarification about what changed and what didn’t (mobile) read more.
#Feature
The long-running request to show all likes/reactions (instead of a truncated panel) resurfaced strongly; staff noted the UX change was partly about shared components/consistency, but also that the community signal here is loud and it’s getting more priority (Contribute > Feature) read more.
A previously-requested improvement appears to have quietly landed: the composer toolbar is now behaving more like mobile (horizontal overflow/scroll), and people are noticing it “just works” in practice (composerux) read more.
A French-language support thread dug into “search within only two specific categories by default,” balancing user simplicity vs powerful filters; the accepted direction pointed toward tuning category search priority (and possibly a theme component for a more guided UX) (search) read more.
Email-in workflows struck another edge case: an incoming-email-created topic was missing most content because the HTML got split at a <section …> boundary. The most maintainable workaround suggested moving away from “HTML email parsing” to a markdown template + API post creation approach (email) read more.
Several “reviewable/insights” issues continue to be sharp edges: IP info not refreshing correctly when switching reviewables, alongside reports of incorrect join date + post count in insights. The cluster suggests a broader “stale/incorrect insights panel state” problem (review-queue) — see read more and read more.
A composer console error around hashtag autocomplete (generateIconHTML undefined) got a clear pointer to the fix, while a second autocomplete error remains harder to reproduce (hashtag-autocomplete) read more.
Embedded comments are still showing English-formatted dates even when the embed UI is otherwise localized; the report includes expected Finnish locale behavior and highlights that the “classic” embed approach is preferred for the site in question (embedding) read more.
AI translation: Portuguese (pt) is being skipped even when many other locales translate automatically; the report includes environment details (Discourse/AI plugin versions and model selection) and clear repro steps (aidynaloc) read more.
Creating a topic from a tag page can prefill a disallowed tag into the composer (server-side still blocks submission, but the UI flow is confusing); this looks like a “composer prefill bypasses tag-group restriction rules” footgun (composertagstag-groups) read more.
#Sysadmins
Two closely-related “make everything go to www” how-tos (apex → www, and wildcard/random subdomains → www) also sparked a practical ops aside: when sudo is (and isn’t) necessary depending on how you run your server and whether root logins are allowed (#www) — see read more and read more.
#Announcements
The “upcoming changes”/impact-labeling conversation continues to evolve: discussion clarified how defaults and warnings should behave going forward (especially on Stable), prompted by a previously-announced default around image grids. Context: the original announcement read more plus the broader “Upcoming Changes” feature thread read more.
The “full comment system embed” announcement thread got additional confirmation of UX improvements like floating controls (reply access and timeline invocation), addressing early feedback about long iframe scroll experiences (embedding) read more.
#Theme component
A new official theme component, Whisper Warning, adds an explicit composer toggle/indicator so staff don’t accidentally post publicly when they meant to whisper (officialwhispers). It was also pointed to as a practical answer for “where did whisper go?” confusion in the broader UX discussion read more (related context: read more).
awesomerobot covered multiple “why did this change?” questions:
Explained the rationale behind the likes/reactions UI shift and confirmed increased priority due to user demand read more.
Confirmed the flag score UI was intentionally removed (to reduce confusion), and invited concrete use-cases for why people want it back read more.
Followed up on reviewable/insights navigation issues and linked to a fix that resets state appropriately when moving between flags read more.
Chimed in on iPad/iOS behavior where scrolling is locked while the keyboard is up, pointing to an exception for iPads when content is still visible read more.
Clarified a small UX detail in the share modal discussion (what content was reorganized and when the date appears) read more.
Falco focused on clarifying current behavior and pointing to fixes/ship-ready changes:
Joined the “search across categories” discussion with screenshots and interpretation of what the user was asking for read more.
Dropped an implementation pointer for self-hosted mobile push notifications (pointing to the relevant fix/PR) read more.
Updated the “full comment system embed” thread with confirmation of floating controls (reply + timeline access) read more.
renato acknowledged and acted on mobile composer feedback: confirmed the toolbar default change isn’t the whole story for the cramped 375px case, merged duplicate discussion into the main thread, and noted improvements are actively being discussed internally read more.
zogstrip stayed close to bug triage and plugin constraints:
Identified the fix path for a hashtag autocomplete console error, while noting a secondary error is still elusive to reproduce read more.
Set expectations on the calendar/event plugin’s limitations (why automatic “going” reset on expiry is non-trivial and currently not scheduled) read more.
supermathie advised on replacing fragile email-parsing pipelines with a more reliable “template to markdown + API post” integration for consistent formatting read more.
martin clarified how “upcoming changes” impact types should behave going forward, especially for migrated/legacy default-setting changes and what should (not) show warnings on Stable read more.
If yesterday had a theme, it was: may your composer show more than one line, your flags be less mysterious, and every rogue subdomain politely redirect to www (see read more and read more).
Thiago_Mobilon shared real-world, high-traffic feedback on the new full-app embedding experience—covering 10x request spikes, caching headers, analytics duplication, and dynamic height needs—prompting Falco to point to fixes and ongoing work in the same thread (read more)
Lilly suggested improving staff UX in the review queue by letting admins truly replace the built-in moderation help link (instead of just adding another link on top), to avoid staff confusion and reduce reliance on outdated Meta docs (read more)
A long-running request to keep push subscriptions on logoff was marked implemented, with Falco linking the completion back to the original request thread (read more)
The disappearance of the “you’re replying to an old topic” warning led to a values discussion: simonk referenced the rationale that Discourse prefers revivals over duplicates, while haydenjames argued for keeping the notice but with better, configurable messaging (read more)
See also the linked background discussion about necroposting safeguards: read more
A report that Discourse “double-encodes” already-encoded URLs when inserted via the composer link tool couldn’t be reproduced; the thread quickly turned into upgrade guidance (moving from 3.5.3 toward current releases) and validating behavior on try.discourse (read more)
A hosted customer reported remote images suddenly being downloaded and locally re-hosted despite attempting to disable it and add domain exceptions; Moin noted the exception setting works on their hosted site and encouraged checking recent changes and staff logs (read more)
A German post wasn’t being translated because language detection was confused by mixed-language context; Falco confirmed the manual language selector forces the post language, and follow-ups pointed to possible issues around translation editing/title handling (read more)
Related active localization threads referenced alongside this include tooltip logic and topic list language behavior (read more) and the ?tl= anonymous localization issue (read more)
A new composer/tagging hint system appears inconsistent: the same tag sometimes shows as allowed vs disallowed depending on the search term; zogstrip confirmed the feature needed to be smarter around tag limits and linked a fix (read more)
The discourse-calendar event widget lost its chat-channel link after the Rollup build changes; klappradla identified the regression window and provided a PR, with david encouraging the contribution (read more)
Plugin-defined category settings stopped saving after 2026.4.0: admins can change plugin fields but never get the “unsaved changes” save prompt; awesomerobot explained this is tied to FormKit + enable_simplified_category_creation, and plugins must migrate to the new form structure (read more)
The issue was raised as a continuation of the long-running Custom Wizard topic (read more)
A self-hosted site reported MessageBus-style live updates no longer delivering new replies in an open topic (manual refresh required); the first troubleshooting question from sam was whether a proxy (e.g., Cloudflare) is involved (read more)
A small but telling UI regression: on the admin backups screen, an arrow/tab indicator intermittently fails to render until navigating away and back, and the reporter suspects it’s part of a broader “log/output only updates after navigation” class of issues (read more)
A free-plan site shutdown email appeared to promise time to “create activity,” but the site was already placed in read-only mode shortly after—raising concerns that the timeline messaging is misleading (read more)
A translation UI rendering issue on Debian/Firefox shows translated text overflowing into the right column before wrapping, suggesting a platform/font/layout edge case in the translated-post presentation (read more)
#Plugin
In the official livestream workflow, users who RSVP “going” still couldn’t access chat; nat adjusted a setting to Trust Level 0 and noted the “everyone” group edge case isn’t a real group for the plugin’s checks (read more)
Falco drove several embed-related follow-ups: diagnosing caching headers (double cache-control) and performance implications in Tecnoblog’s embed report (read more), discussing analytics-in-iframe concerns (read more), and confirming dynamic embed height work landed (read more). He also clarified manual language selection behavior in the AI translation thread (read more) and closed the loop on push subscriptions on logoff (read more).
nat handled multiple product-support touchpoints: unblocking chat permissions for the livestream plugin by changing access to TL0 (read more), progressing a docs reindexing fix with a linked PR in the restore issue (read more), and acknowledging/triaging localization bugs (including the translation tooltip logic) (read more) plus the ?tl= anonymous localization thread (read more). He also challenged a suspected cause in the German-translation debugging thread and asked about model deprecations (read more).
pmusaraj linked an upcoming fix for Google One Tap behavior inside embedded Discourse (iframe refresh/login flow) in the embed feedback thread (read more), and requested clearer problem details in the WeChat mini program integration discussion (read more).
zogstrip confirmed the new tag permission messaging needed smarter logic around tag limits, pointing to a fix in the bug thread (read more).
awesomerobot explained why plugin category settings stopped saving under the simplified category creation experience, and outlined the FormKit migration path (with an example branch pattern) (read more).
david encouraged a community PR to fix the missing chat link in the calendar event widget, giving a quick green light to proceed (read more).
featheredtoast followed up on the long-running mobile left hamburger menu theme component, noting Lilly’s cleanup work and that the changes were merged (read more).
tgxworld documented that category moderation trust-level behavior and “approvals tied to groups” effectively landed (linking the implementation) and closed out the older feature request accordingly (read more) and (read more).
sam kicked off troubleshooting for missing real-time topic updates by asking whether a proxy like Cloudflare is in the mix (read more).
Yesterday’s vibe: cache headers got a stern talking-to, old-topic warnings sparked philosophy, and even the backups page tried to play hide-and-seek—may your embeds be lazy-loaded and your UI arrows always show up on the first try.
sam addressed ecosystem concerns head-on, reiterating Discourse’s commitment to open source in the wake of other SaaS projects closing their codebases: read more
#Announcements
lindsey announced a streamlined way to create “Ideas” categories using the Topic Voting plugin (topic-voting), baking common settings into category creation so admins don’t have to wire everything manually: read more
#Feature
In a detailed embed-field report from a high-traffic site, Thiago_Mobilon and Falco iterated quickly on Discourse Comments (embedding) — fixing dynamic height and discussing sane limits to avoid “infinite-scroll-meets-giant-iframe” UX traps: read more
#Plugin
pmusaraj shared an experimental Buffer sharing plugin (experimental) that lets staff queue a topic to Buffer from the share modal or wrench menu, including a server-generated preview of title/excerpt/image before posting: read more
A breaking change to category settings UI impacted multiple plugins; staff clarified the rollout and pointed admins to disabling enabled_simplified_category_creation in Upcoming Changes while fixes landed: read more
AI translation (ai, dynaloc) appeared to skip Portuguese when many locales were enabled; narrowing enabled languages made PT translations start working again, suggesting a scaling/limits issue worth further logging: read more
A real-time sync gap was reported: moving a post between topics didn’t update already-open clients viewing the destination topic, raising questions about the pathway for move events vs. standard “new post” updates: read more
Invite detail tabs were invisible to non-staff due to a client-side route/controller mismatch; a one-line fix was proposed and quickly accepted: read more
A moderation workflow pain point: noahl suggested the review queue (review-queue) should visually group items by user (or at least warn about related queue items) to reduce “delete first, discover legitimate content later” outcomes: read more
Proposed guardrail: show “This user has created X topics, Y posts…” before destructive actions: read more
Theme work surfaced UI polish issues: vote display sizing in the new Foundation theme (topic-voting) and additional dark-theme state contrast problems were raised in the broader modernization thread: read more and read more
#Theme_component
Lilly published Discourse Dynamic Sidebar Icon (sidebar), a lightweight component that swaps the sidebar toggle icon based on open/closed state, with optional mobile behavior for icon consistency: read more
Whisper UX got attention from both angles: the Whisper Warning component’s settings interactions were clarified, while core UI work-in-progress was hinted to make whisper toggling more obvious in the composer flow (whispers): read more and read more
The long-standing “Force Mobile Homepage” component (broken) got a practical successor: a new Mobile Latest Homepage component avoids deprecated APIs and uses viewport detection + router redirects, with session memory of “Latest vs Categories”: read more and read more
A locale-switching error that only affected admins in Chrome was resolved by removing a stale ?preview_theme_id= parameter that “stuck” in the URL, triggering a misleading theme-preview error across topics: read more
A usability question turned into a product/setting discussion: can admins change the default landing tab for Groups (Members vs Activity vs Messages), ideally per-group, to emphasize what’s happening instead of who’s listed: read more
sam published a clear public stance that Discourse is not going closed source, framing the post as a response to broader industry anxiety and AI-era risks: read more
Falco pushed multiple embed improvements based on real-world testing, including adopting native lazy-loading via loading="lazy" and iterating on dynamic height behavior for Discourse Comments (embedding): read more and read more
david contributed to the embed conversation by suggesting the browser-native lazy iframe approach (reducing the need for custom JS/observers), helping drive the quick follow-up changes: read more
pmusaraj debugged multiple support/bug reports, including identifying that an admin-only locale-switch error was actually caused by a stale preview_theme_id parameter: read more
pmusaraj also investigated a tricky AI translation edge case where Portuguese translations were skipped when many locales were enabled, then looped in teammates and suggested using verbose logs for diagnosis (ai, dynaloc): read more
nat weighed in on the “Portuguese skipped” translation mystery and pointed to /logs plus a hidden verbose logging setting ai_translation_verbose_logs for deeper investigation: read more
awesomerobot acknowledged and provided immediate mitigation for plugin breakage caused by simplified category creation, including pointing admins at toggling the upcoming change setting while fixes rolled out: read more
martin clarified the notification/rollout expectations around the simplified category setup change, then followed up with confirmation that fixes were merged (with extra spec coverage) for affected official plugins: read more and read more
awesomerobot quickly accepted a code-level bug report about invite detail visibility and linked the fix PR back to the report thread (invites): read more
lindsey announced improvements to create “Ideas” categories powered by Topic Voting, and cross-referenced it from the ongoing “Current Projects” roundup to keep the roadmap thread tidy: read more and read more
supermathie explained a scary-looking 429 after split/move operations as non-critical (a timings update request), giving admins confidence that the move itself succeeded and the error can be ignored: read more
manuel resurfaced interest in a Discourse static archive generator and shared a community prototype that outputs browsable categories/tags/users with working search, as a reference point for future tooling: read more
May your sidebar icons stay perfectly in sync, and may none of your embeds decide they need 9,000 pixels of breathing room overnight.
Discourse reaffirmed its long-term commitment to open source, sparking discussion about trust, security, and community reciprocity in Discourse is Not Going Closed Source (with pointed reactions like elmuerte’s take on security-by-obscurity and community trust — read more).
Questions about Discourse MCP transport options came up again, and Falco clarified that HTTP transport is already supported in Discourse MCP is here!.
A Free Plan site got “stuck” in read-only mode, where the “Disable read-only” button wouldn’t persist; rishabh identified a system-side flag incorrectly forcing read-only in Cannot disable read-only mode on Free Plan (original report: read more).
Admin category settings + plugins collision: plugin-provided settings weren’t saving cleanly, and the discussion continued around the admin UI changes and what could have better protected plugin authors in Unable to save category settings made by plugins (related context: Simplified category setup).
Discourse ID, OAuth2, and 2FA expectations got untangled: jomaxro clarified that when using external logins, 2FA enforcement must live at the identity provider (and local enforcement isn’t supported without local logins) in Discourse ID and 2FA (solution post: read more).
“Diff is too complex to display” explained: zogstrip broke down the diff “comparison budget” and the hard ceiling that prevents runaway compute in Diff is too complex to display.
Redis FLUSHALL as a troubleshooting tool (with warnings): a host shared that flushing Redis cleared a stuck “Updating” admin state in Redis Flushall, and RGJ cautioned it logs users out and wipes Sidekiq jobs in their follow-up.
Login-required sites and the “landing page” before /login: discussion revisited why the homepage may show a screen with a Login button first, with pmusaraj explaining the rationale and the narrow skip-case setting in Disable initial page that re-directs to /login (and zogstrip noting the homepage edge-case — read more).
pmusaraj provided product rationale for keeping a login landing screen (community context, signup/login affordances) and pointed out the “single external login method” exception in Disable initial page that re-directs to /login.
Yesterday’s moral: keep your sites out of read-only, your login copy customizable, and your diffs under budget — and you’ll have a surprisingly peaceful day on Meta.
elmuerte and RGJ pushed back strongly on the idea that open source is “dead,” arguing that Discourse (and its dependencies) benefit from open ecosystems, and that security by obscurity doesn’t work in practice—especially given that vulnerabilities in upstream components are still publicly disclosed (read more, read more).
Related: a side discussion touched on automated update workflows and why “just turn on auto-updates” can be risky for self-hosting (read more, read more).
A Chinese-language thread asked why there isn’t a widely-used open source Android app for Discourse; replies noted that Discourse’s PWA support (including notifications on iOS/Android) has reduced the need for a native wrapper, and pointed to earlier discussions about app conversion and Play Store presence (read more, read more, read more).
#Site feedback
Confusion surfaced around why some topics have Post Voting enabled and others don’t; NateDhaliwal spotted inconsistent behavior between two topics, Moin suggested it might have been manually selected during topic creation, and mcwumbly confirmed the team will investigate (read more, read more) post-voting.
In ongoing work on the Meta theme redesign, cuo_wu asked how Meta resolved the “filled heart icon on like” behavior and wanted to replicate it on their own site—another small but telling example of how design details affect perceived polish (read more) meta-theme-feedbackmeta-redesign-2026.
A deep dive into AI Translation intermittently skipping locales continued: Denis_Kovalenko reported “randomly skipped” languages (not only Portuguese), plus inconsistent title/body translation; nat suggested checking LLM context window limits and cautioned against “GPT mini” translation quality, while RGJ surfaced backend 503 errors and questioned retry behavior on translation jobs (read more, read more, read more) aidynaloc.
Related: enabling hidden verbose logs required knowing about hidden site settings (read more, read more).
A mobile UI regression/quirk was reported where the “add user” dropdown modal can jump above the visible viewport, making it hard to complete actions like adding users to groups or inviting users to PMs—especially frustrating because swiping tends to dismiss the modal instead of bringing it back into view (read more) mobile.
A thread on Redis FLUSHALL turned into a practical discussion about troubleshooting “stuck updates” and the difference between Redis restart vs destructive flush; Ed_S clarified Redis persistence, RGJ corrected the “in-memory only” misconception, and Lilly noted that UI-based updating has been improving (even from a phone), though CLI remains more reliable for many admins (read more, read more, read more).
A Chinese-language question asked for a “better global Chinese plugin” because some admin setting names remain English; Moin explained why keeping setting keys consistent across languages helps support/debugging, and linked ongoing ideas to add translated subtitles rather than fully translating setting names (read more, read more, read more, read more).
A new support question asked whether Discourse supports a “variable” or macro to avoid repeating the same large image markup thousands of times in wiki tables—highlighting real-world post length/maintenance constraints when content gets very large (read more).
Another support thread (Chinese) reported a plugin replacement that “didn’t succeed,” shared with a screenshot—early signal of a potentially common deployment/configuration pitfall to be diagnosed next (read more).
Email configuration came up again: someone needing to move from SMTP basic auth to OAuth learned that some providers (like MailEnable) don’t support OAuth for SMTP in the same way as Google/Microsoft, implying a switch to a compatible relay/provider may be required (read more).
#Feature
Chat feature feedback: gilles requested the ability to create polls in chat channels, plus better defaults and permissions; Lilly asked to split the default-channel-configuration request into its own topic for clearer tracking and prioritization (read more, read more) pollschat.
Following up, gilles posted a dedicated request for default settings when creating new chat channels (pre-configuring threads, etc.) and questioned why channel creation is restricted to mods/admins; replies suggested the restriction may help prevent channel spam (read more, read more) chat.
#Theme component
A long-running theme component thread on forcing a mobile homepage got fresh commentary: merefield argued the problem is increasingly layout-based rather than route-based, and described experimenting with a sidebar “Categories column” that naturally disappears on mobile—same URL, adaptive layout (read more).
The Wikipedia Lookup theme component got a useful configuration tip: setting the wikipedia base url can point not only to language-specific Wikipedia subdomains, but even to alternative wiki hosts (e.g., a Miraheze wiki), making the component more flexible than it first appears (read more).
A customization gotcha: changing the “New Topic” button label via a component also changed the “Reply” label, suggesting shared i18n keys or unintended coupling in the component’s implementation (read more).
WP Discourse publishing edge case: an Italian-language report described a WordPress post containing only a large gallery failing to mirror correctly into Discourse, instead pulling GDPR/footer text—suggesting the excerpting/parsing logic may be grabbing the wrong content when there’s no traditional body text (read more).
Related: another WP Discourse feature thread continued about filtering which comments sync back, and the limitations of post-level tagging signals today (read more).
#Plugin
“Discourse Category Lockdown” saw renewed interest in allowing teaser visibility (e.g., show first posts in locked categories to motivate subscriptions), a recurring monetization/course-delivery use case (read more) pavilion.
#Announcements
Boosts feedback kept rolling in: Andrew_Rowe shared that boosts turned out to be surprisingly useful as a lightweight “this matters” signal when a like feels too small but a reply feels too noisy, while others suggested better ways to locate and manage your own boosts in long lists (read more, read more).
#Site Management
A practical admin note landed in the evergreen moderation guide thread: Lilly reminded admins that the moderation guide link is included in the automated “welcome staff” message, and that sites with custom guides should update system_messages.welcome_staff.text_body_template to point moderators to the right place (read more) moderationexplanation.
Mobile composer ergonomics remain a pain point: a self-hosting admin shared that editing on a phone can feel cramped, comparing Discourse’s composer space to their phone’s native notes UI as inspiration for better mobile composition patterns (read more) composermobile.
mcwumbly acknowledged confusing behavior around Post Voting being enabled inconsistently across topics and confirmed the team is investigating what’s going on (read more).
nat weighed in on the AI Translation locale-skipping investigation, proposing checks around context window constraints and noting that some smaller/cheaper models perform poorly for translation workloads—useful guidance for anyone tuning #discourse-ai translation quality (read more).
That’s a wrap—yesterday’s Meta was basically a three-course meal of boosts, bots, and Redis buttons daring admins to press them.
WP Discourse “Publish” + image galleries ran into a core limitation: angus explained that the embed pipeline relies on Mozilla’s Readability-style extraction and is optimized for text, so image-heavy “gallery-only” posts can scrape poorly in “Pubblicazione post con galleria WordPress su Discourse”; the discussion also touched on selector settings in this follow-up and the reality that true 1:1 gallery syncing may require custom plugins in the latest reply. read more
Translation/customization limits were clarified: Moin explained that the “Globally replace translations” plugin affects frontend locale strings, not arbitrary/untranslatable setting labels, in “Globally replace translations”, with adjacent guidance pointing toward editing translatable text via “Customize text in Discourse” and a related explanation referenced in this linked post. read more
Federated login and MFA assurance: supermathie asked whether an IdP can pass along proof/attestation of MFA completion to the service provider (and what to do if not) in “Discourse ID and 2FA”. read more
supermathie dug into identity-provider MFA semantics—specifically whether IdPs can pass along an “MFA performed” signal/attestation to relying parties—in “Discourse ID and 2FA”.
Yesterday’s theme: if Readability can’t find your gallery and Rails won’t let you exit, at least meta will still help you untangle it all by morning.
Topic Gallery
Discourse llms.txt Generator Plugin
Fehler in der Deutschen Übersetzung? Hier melden!
chat-channel link after the Rollup build changes;