Today on meta.discourse.org…
Daily digest covering activity from 2026-03-25 → 2026-03-26.
Key Stats
- New posts (last 24h): 92
- New topics (last 24h): 14
Top contributors (posts + likes in the last 24h)
| User | Posts | Likes | Notable recent post |
|---|---|---|---|
| Falco | 5 | 18 | Release visibility + security fixes discussion — read more |
| david | 3 | 17 | Follow-up + backfilled release announcements — read more |
| Moin | 8 | 17 | Tips & context on version/dashboard notices — read more |
| nathank | 10 | 11 | /about-page group hiding strategies — read more |
| Ed_S | 4 | 10 | “Stealth release” concern + feedback loop — read more |
| tobiaseigen | 2 | 6 | 2FA input alignment report — read more |
| meave | 1 | 6 | Emoji alias quirk (“champagne”) — read more |
| merefield | 2 | 5 | Security-fix commentary — read more |
| awesomerobot | 2 | 4 | Pinpointed 2FA layout difference + fix link — read more |
| Heliosurge | 2 | 3 | Deletion/attachment cleanup pointers — read more |
Interesting Topics
Support
-
Ed_S raised concerns that v2026.3.0-latest.1 (with “33 security fixes”) felt like a stealth release, and asked for release posts to return to Announcements; david acknowledged the feedback and backfilled pointers to the new release flow in the follow-up release topics (stealth-release discussion, plus the backfilled pointers: February 2026 monthly release and March 19th 2026 intermediate releases). The thread also resurfaced older “dashboard advice” notification confusion (reference) and related version-display oddities (reference).
-
one1 asked for a built-in way to remove the default @moderators group from /about, aiming to show only “Active Mods”; nathank explained how
about_page_hidden_groupscan suppress certain members (or dynamically populate “not-active” groups), and suggested using the Discourse Dynamic Groups plugin to manage trainees cleanly (read more, plugin ref: Discourse Dynamic Groups). -
A Chinese-language support thread dug into whether permanently deleting posts also deletes uploads/attachments; the discussion pointed to existing cleanup settings and cautioned that reliably purging uploads may require tooling like the Legal Compliance plugin, with additional background from upload-purge docs and older auto-purge threads (read more; refs: Legal Compliance plugin, Cleaning up uploads / purging from S3, Auto-purge uploads from old deleted posts, and the feature intro: Permanently delete posts).
-
On the free hosted plan, Naoshi wanted an “Announcements” category that’s read-only for topic creation but allows replies; Moin suggested a practical moderation workflow: require approval for new topics in that category, then simply don’t approve non-staff topics (read more).
-
A Marketplace request appeared from James_Bridges seeking a developer to integrate Discourse with Kajabi (membership tier syncing, migration, Disqus comment replacement, and “Facebook-simple” UX goals) (read more).
ux
-
tobiaseigen noticed 2FA code inputs left-aligned when logging into Meta via an email login flow; awesomerobot identified the path-specific layout difference and linked an in-flight fix (read more).
-
meave spotted that typing
:champagnedoesn’t surface an emoji even though the rendered label says “Champagne”; Falco traced it to an alias/constant mismatch in the emoji mapping and suggested removing the conflicting constant entry (read more). -
A Horizon theme/mobile UX issue: category descriptions can remain “sticky” and crowd topic lists on small screens; this was raised in a new UX thread (read more) and echoed as an older Horizon-theme behavior discussion where tradeoffs were debated (related).
#Feature
- A feature request proposed adding .ics iCalendar attachments (or
text/calendarparts) to event notification emails, so recipients can accept invitations directly in email clients; Falco pointed to newly improved calendar subscription syncing as a partial workaround, including the recent addition of event links in the feed (read more, related: Calendar subscription URLs).
#Self-Hosting
- darkpixlz reported being unable to enable DiscourseID without
force_https, due to redirect URIs requiring https; supermathie explained that DiscourseID expects correct proxy headers (orforce_https) so Discourse consistently recognizes https requests (read more). This aligns with earlier DiscourseID fixes around key/redirect handling (related solved topic).
bug
-
A CSS rendering issue was reported where tables without
<thead>still render a “header divider”, making a<th>in<tbody>look like a header row; the reporter argued this contradicts expected HTML/CommonMark assumptions (read more). -
A self-hosted report flagged the Chat plugin failing to compile under the newer rollup plugin compiler, throwing
_assert is not a functionduring asset build (read more). -
Another (Chinese-language) UI bug report described the welcome banner text color picker saving an invalid value unless the
#prefix is manually added, suggesting inconsistent color handling in the admin UI (read more).
Dev
- Devs discussed improvements to icon configuration: there is now an icon-type SiteSetting (reducing foot-guns when configuring icons), with follow-on implications for places like reactions and icon discovery/documentation (read more, related: Reactions + free icon prefixes, and icon-link/placeholder ergonomics discussion: FontAwesome placeholders in setting descriptions).
#Plugin
- The Discourse Challenges plugin v1.2.0 shipped changes like daily/weekly intervals and moderator access, but a user reported 500 errors when creating challenges; the maintainer requested logs and version details to triage (release + troubleshooting thread).
Activity by the @team Group
-
david engaged directly on release visibility and communication, acknowledged the long-missed email issue, and linked the two backfilled release pointer topics in the “stealth release” discussion (release feedback thread, plus the follow-up with links to February 2026 monthly release and March 19th 2026 intermediate releases). He also promoted a talk related to the new plugin build system (plugin build system topic update).
-
Falco participated across UX and feature threads: he responded to the security-fix/release discussion (reply), proposed a fix for the
:champagneemoji alias issue (emoji mapping note), and guided the calendar.icsemail request toward subscription URLs and recent improvements (calendar feature discussion, follow-up: event link now included). He also hit a blocker while working on the Patreon API v2 upgrade due to Patreon’s client form not enabling submission (Patreon plugin upgrade thread). -
awesomerobot investigated a Meta login-flow-specific 2FA layout bug, identified it as tied to email login, and pointed to an upstream fix (2FA alignment thread).
-
supermathie clarified that DiscourseID redirect URIs must be https, and that correct proxy/https signaling is required (not just “it works in the browser”), responding with concrete evidence from the reporter’s config screenshots (DiscourseID + force_https thread).
-
pmusaraj left two DiscourseID-related touchpoints: confirming a fix for “redirect URI already exists” behavior going forward (solved DiscourseID redirect URI thread) and requesting reproduction details/screenshots for an alternate-email recognition report (SSO/DiscourseID alternate email thread).
-
martin posted an update on planned refinements to admin reporting visibility options (“Staff only” / “No one” in places where “Everyone” doesn’t fit) (Admin Reporting & Analysis update).
-
chapoi weighed in on the Horizon theme’s sticky category header container behavior, noting it was a side-effect of keeping navigation visible and inviting contributions if someone can untangle the container relationship (Horizon sticky header thread).
If yesterday taught us anything, it’s: announce your security releases loudly (read more), keep your 2FA boxes centered (read more), and never make people type :cork: when they really mean :champagne: (read more).