Today on meta.discourse.org…
Key Stats
- New posts (last 24h): 41 — spanning active support + UX threads like “All plugins not functioning” and “Customize registration form / hide or normalize username field”.
- New topics (last 24h): 5 — including fresh reports/ideas such as “Category creation floating box blocks out settings at the bottom” and “Pouvoir changer de canaux et de fermer en grande fenêtre chat”.
Top users by recent activity (posts) and appreciation (likes):
| User | Posts | Likes | Seen in… |
|---|---|---|---|
| ToddZ | 7 | 7 | feedback in “Opinions on the forum I’ve built”, guidance in “Customize registration form…”, and more like FAQ link review |
| darkpixlz | 3 | 10 | diagnosing CDN/CORS in “All plugins not functioning” and flagging workflow confusion in “‘reply to this message’ goes nowhere?” |
| merefield | 4 | 3 | theme/CSS suggestions in “Opinions on the forum I’ve built”, plus upkeep in Tag Intersection Navigator |
| NateDhaliwal | 4 | 2 | UX + hosting advice in category creation UI and ESR vs latest stability |
| awesomerobot | 2 | 3 | bug triage in HEIC upload issue and API access follow-up in about.json permissions |
| paulovbettio | 2 | 2 | community structure questions in Portuguese: read more |
| Steven | 2 | 1 | theme/plugin maintenance notes in MD Topic List Mobile and Formatting toolbar |
| R23D_Printing | 1 | 1 | extending the “challenge bot” idea in Discourse Daily Challenges |
| TomoftheFog | 1 | 2 | follow-up testing plans in plugin loading issue |
| 25w31b | 1 | 1 | confirming resolution in Discourse ID alt-email thread (#discourse-id) |
Interesting Topics
#SELF-HOSTING
-
darkpixlz traced “plugins not functioning” symptoms to a likely CDN/CORS failure, suggesting a targeted test to confirm the root cause before chasing plugin bugs in “All plugins not functioning” (with TomoftheFog planning weekend tests read more).
-
Frustration with update stability sparked a reminder that
latestis inherently fast-moving, whileesris the better choice for those prioritizing stability in “Unstable software - constantly breaking update processes”. -
A migration/admin workflow question came up around moving group inbox messages, with pointers to bulk topic-moving capabilities in “Transfering inbox group messages to another instance?”, referencing the how-to on moving topics between instances read more.
-
Deploy/version-management troubleshooting continued with a YAML indentation gotcha while reviewing older-version deployment attempts in “Help deploying older versions of Discourse”.
Community Building
-
A site feedback thread highlighted theme aesthetics, category organization, and small UX polish (including a mobile header-links CSS snag) in “Opinions on the forum I’ve built” and follow-ups like the mobile layout note read more.
-
Portuguese-language forum-organization feedback focused on balancing categories vs many tags, homepage choice (Latest vs Categories), and onboarding clarity in “Eu tenho um fórum, mas não sei se ele está bem organizado o suficiente”, with practical notes and inspiration links like Topic List Previews (TLP) read more.
bug
-
A composer/data-loss report described lost paragraphs / unexpectedly huge posts tied to uploading HEIC images, with awesomerobot steering toward reproducible steps (text volume + same images) in “Lost paragraphs / huge post due to HEIC upload”.
-
Search UX/bug history got an update: hashtag/tag autocomplete behavior that overrides the first choice now has a proposed fix queued, per davidb in “Autocomplete overrides first choice…” (search hashtag-autocomplete).
ux
-
A copy/flow mismatch was flagged: the system DM suggesting “reply to this message” during revision requests appears to route replies into a void (no admin visibility / reviewable linkage) in “‘reply to this message’ goes nowhere?”.
-
The category-creation screen’s floating action box was reported to block lower settings (particularly noticeable with horizon-theme styling) in “Category creation floating box blocks out settings at the bottom”.
-
Ongoing housekeeping for built-in guidance links continued, including a reminder that “Upcoming Changes” itself may be gated behind a setting, discussed in “Review and update topics related to FAQ & Guidelines links” with the referenced “Upcoming Changes” feature intro read more.
Support
-
A common admin requirement—encouraging real names—landed on a pragmatic solution: enable username suggestions from the Name field + add signup instructions via site text, discussed in “Customize registration form / hide or normalize username field”, alongside CSS hiding cautions and references like “Making custom CSS changes on your site”.
-
API permissions nuance: an API user with granular access couldn’t read
about.json, and awesomerobot confirmed it’s reasonable to include that access (plus opened a PR) in “API user with granular access cannot read about.json | Discourse MCP” (mcp). -
A long-running styling/regression thread noted category images being forced into a squashed square; the workaround path is CSS-based if core behavior doesn’t change, as discussed in “Tiny category image”.
#PLUGIN / #THEME-COMPONENT / #FEATURE (grab-bag updates)
-
Maintenance + a new quality-of-life feature landed for intersection-based navigation: banner notifications without leaving intersections, in “Tag Intersection Navigator”.
-
A lightweight maintenance check-in suggested the “MD Topic List Mobile component” is still holding up, with an invitation to report breakage in “MD Topic List Mobile component”.
-
A chat UI question (in French) observed that maximizing chat can hide controls to switch channels or close the window—forcing users to resize to regain controls—in “Pouvoir changer de canaux et de fermer en grande fenêtre chat”.
Activity by the @team Group
-
awesomerobot focused on actionable bug triage, asking for reproduction details (error message, repeatable steps, testing with placeholder text + same images) in “Lost paragraphs / huge post due to HEIC upload”.
-
awesomerobot also followed up on API surface consistency, agreeing it’s reasonable for granular API keys to access
about.json, and noting a PR was opened for team review in “API user with granular access cannot read about.json | Discourse MCP”. -
davidb shared a concrete fix path for the search autocomplete override issue, pointing to an implementation that should resolve it once merged in “Autocomplete overrides first choice…”.
With CDN mysteries, “Disconite” naming debates, and autocomplete fixes in the mix, today’s meta energy was equal parts detective work and delightful bikeshedding.