Daily Summary (9pm UTC)

[system]

Today on meta.discourse.org…

Key Stats

In the last 24 hours (2026-03-07 → 2026-03-08), Meta saw 36 new posts across 5 new topics, with discussion spread across support troubleshooting, theming experiments, and self-host/dev setup snags (e.g. read more, read more, read more).

Top posters & most-liked (last 24h)

User	New posts	Likes received	Where they were active
NateDhaliwal	4	4	Mobile debugging questions read more and onebox/composer customization ideas read more
stephtara	3	2	Follow-ups on the tag styling tool read more and per-user embed customization read more
Lilly	2	5	Clarifying legacy mobile mode deprecation read more and safe-mode troubleshooting + deprecation notes read more
jdc20181	2	4	Progress updates on a style builder + color picker direction read more
darkpixlz	2	4	Noting ?mobile_view=1 removal context read more and theme maintenance for the upcoming default theme read more
gilles	2	2	Windows dev setup Ruby mismatch resolution read more
Falco (@team)	1	4	Pointing to native HTML color input + Discourse wrapper component read more
sam (@team)	1	2	Brainstorming “agentic” support workflows in Discourse AI read more
ToddZ	1	1	Guidance on mobile/desktop layout overrides shifting over time read more
merefield	1	1	Explaining why Ruby 3.4.0.dev can fail Gemfile constraints read more

Also bubbling up on the sidelines: a multilingual blog thread got fresh replies read more, and the long-running events plugin topic flagged a broken external support link read more.

---

Interesting Topics

#Theme-component

• jdc20181’s Tag Style Tool thread continued evolving into a mini “style builder” discussion, including Font Awesome icon support, UX requests for linking resources in settings, and experiments toward a color-picker UI read more (plus a progress demo read more).

Support

• A “why can’t I see the mobile UI on desktop browsers?” investigation explored the fading legacy of ?mobile_view=1 read more, with pointers that it’s deprecated/legacy behavior read more and may have been removed recently read more; the deeper direction is viewport/capability-based styling read more.

• A self-host admin reported Discourse ID signups silently failing (button does nothing) and noted anonymous-only console 404s like vendor.map/start-discourse.map, seeking configuration/debug guidance read more (discourse-id).

• A new SEO/localization report suggested translated ?tl= pages aren’t being indexed because the canonical tag points to the non-translated URL (Google treating localized pages as “alternate with proper canonical”) read more (content-localization).

• A self-hoster described AI Search resource impact and others asked for “hardware profile” details before enabling it themselves read more (ai ai-search).

• A theming question asked how to create a transparent “Discord-like” look, ideally per-user or for a small group—highlighting the common constraint that theme components typically apply instance-wide read more.

• An iPadOS Safari oddity where the composer “flies off screen” when focusing different fields was reported—and then (mysteriously) stopped reproducing the next day, leading the OP to mark it resolved/withdrawn read more (resolution update read more) (composer tablet).

• In a solved onebox thread, NateDhaliwal suggested a composer button that inserts an iframe (theme-component feasible), and the discussion moved toward per-user personalization via custom user fields and access patterns read more (and follow-up on user-specific values read more).

• A “non-admin users can’t load pages” support thread got a familiar first-line check: “does it work in safe mode?”, plus a reminder that the advanced search banner component is deprecated and its functionality moved into core/banner patterns read more (safe mode reference read more, deprecation notice read more, and the current banner guide read more).

#Self-hosting

• The Windows 11 dev environment guide saw a fresh round of Ruby version mismatch troubleshooting (3.4.0.dev vs Gemfile ~> 3.4), with links to common “build fails / update fails” cousins and a confirmed fix by installing Ruby 3.4.8 read more (related: build mismatch thread read more, crash-during-update read more, and the “big scary red button” update thread read more) (dev-install).

#Site-feedback

• In the ongoing “improving support categories” conversation, sam pointed out Discourse AI already supports sophisticated agents and asked how to make advanced workflows easier to configure, tying into a parallel “split automations into triggers/actions” feature direction read more (feature request context read more).

#Theme

• Pyx’s Modern Theme shipped an update aimed at compatibility with the upcoming default theme, including restoring a cursor-active behavior (under a new name) and tweaking button borders with an option to disable if it has side effects read more.

#Site-Management

• A question on auto-bumping configuration asked whether “1” is effectively the minimum daily bump, after .25 (every 4 days) didn’t persist—raising practical concerns about overwhelming the feed in “resources” categories read more.

#Sysadmins

• In the NodeBB → Discourse migration guide, a contributor shared a tweak to mongo.rb to ensure posts within a topic sort chronologically via sort(score: 1), improving import ordering read more (how-to).

#Feature

• A “Math should be quotable” proposal suggested a theme-component approach to improve quoting of MathJax/KaTeX-heavy posts by replacing math wrappers with original TeX source before quote-to-Markdown conversion read more (pr-welcome).

---

Activity by the @team Group

• Falco jumped into the Tag Style Tool discussion to note there’s a native HTML color picker input (<input type="color">) and that Discourse wraps it for easier usage—useful for turning a “maybe-plugin” idea into a realistic theme-component enhancement read more.

• sam weighed in on improving support workflows, pointing out that Discourse AI already supports “extremely sophisticated agents,” and raised the key product question: how to expose these capabilities so admins can configure advanced workflows without heavy bespoke work read more.

---

If yesterday was any indication, today’s Meta motto is: may your mobile views be viewport-driven and your color pickers be delightfully native (read more, read more).

[system]

Today on meta.discourse.org…

Key Stats

• New posts (last 24h): 77
• New topics (last 24h): 12

Top posters (with likes received in the last 24h)

User	Posts	Likes
sam	3	12
ToddZ	7	10
jdc20181	5	6
HAWK	3	5
gilles	5	4
merefield	3	4
Falco	6	4
NateDhaliwal	5	4
nat	2	3
mentalstring	3	3

---

Interesting Topics

#Announcements

• sam announced service tiers for OpenAI/Azure providers (including guidance on the responses endpoint for caching/costs) in Service tiers on Open AI providers, with a pointer back to the LLM settings page for configuration.

• In the long-running “bundled plugins” discussion, mentalstring reported a surprising rebuild failure + missing cakeday UI on an older stable install in Bundling more popular plugins with Discourse core, and david explained the warning behavior + offered a cleanup hook workaround (read more).

#Site feedback

• A docs-audit thread kicked off around FAQ vs Guidelines vs About links, clarifying differences between hosted vs self-hosted behavior and calling out the hidden setting rename_faq_to_guidelines in Review and update topics related to FAQ & Guidelines links, referencing the earlier announcement Renaming FAQ to Guidelines and the how-to Using Hidden Site Settings.

Support

• Dashboard UX feedback: merefield asked whether the Site Traffic graph should rescale its Y-axis when toggling series in Site Traffic graph: should reselection of included series re-scale the Y axis?, and nat confirmed changes are underway (read more).

• “Can Discourse force a one-way TOS acceptance?” was answered with a custom user field pattern that blocks saving until checked (marked solved) in Require TOS acceptance.

• Two separate discourse-id support threads saw admins run into workflow snags: one about duplicate redirect URIs after reinstall in Can’t set up Discourse ID: Application with this redirect URI already exists and another where signups appear to do nothing (404/console/log issues) in New users can’t sign up, 404 errors in console.

• A big ops/perf report: enabling ai ai-search caused heavy load while backfilling embeddings for a large site (millions of posts) in Enabling AI search crippled my server, after earlier requests for server/DB/provider specifics (read more).

• Mobile UX regression report: the text-selection popup (Quote / Copy Quote) fails on some mobile browsers, reproducible even in safe mode, in The three buttons that pop up after selecting text on a mobile browser do not work when clicked.

• A theme/CSS question explored options for making a theme “transparent” and selectively available, in How can I make a theme that is transparent?, with related references to Show/hide themes for specific groups? and the component idea CSS classes for current user’s groups.

• A tricky error log around editing wiki posts for some users (with create_errors_json called with unrecognized type) landed in Error when editing a Wiki Topic.

• Privacy/GDPR concerns surfaced again around oneboxes: max.l questioned whether onebox preview images/favicons are fetched remotely (tracking risk) in Cache onebox images and/or serve them from the main domain, and Falco walked through live testing and clarified behavior differences between composer preview and baked posts (read more).

bug

• Tag permissions: jdc20181 reported restricted tag groups still visible on /tags in Restricted visibility tag groups are still visible on /tags page, referencing an older “we fixed this” note in Tags that are supposed to be only visible to staff are shown on /tags for everyone.

• nat dropped a confirmed fix for a tags UI issue affecting certain slug-generation settings in 在 Slug 生成方法为 none 情况下，创建新标签后无法正常显示新版编辑标签功能 (with the upstream PR linked in-post).

#Theme component

• A fast-moving iterative debug session continued for the Tag Style Tool, including a disappearing builder button and icon rendering quirks, in Tag Style Tool.

Dev

• Plugin feasibility (FR): gilles sketched a workflow for a BoardGameGeek API-powered composer toolbar button, and the thread weighed theme component vs plugin tradeoffs (API key exposure) in Besoin d’avis pour essai de programmation de plugin.

#Feature

• Automation design discussion: sam revisited the idea of splitting automations into trigger → filter → action pipelines in Feature Request - Split Automations into Triggers and Actions.

• SSO privacy: a report noted emails exposed in DiscourseConnect provider redirect URLs (base64 payload, not encrypted), and the proposed path forward was a backward-compatible site setting (pr-welcome) in Security/Privacy concern: Email exposed in DiscourseConnect Provider redirect URL with reference to Use Discourse as an identity provider (SSO DiscourseConnect).

---

Activity by the @team Group

• sam led on AI + automation improvements: rolling out provider service tiers in Service tiers on Open AI providers (tied back to the LLM settings page), and engaging on the automation pipeline proposal in Split Automations into Triggers and Actions. He also asked for deeper diagnostics on large-scale embedding backfills in Enabling AI search crippled my server.

• HAWK helped untangle confusion around FAQ vs Guidelines links, steering a docs cleanup conversation in Review and update topics related to FAQ & Guidelines links and looping in Danielle for coordination (read more).

• Danielle confirmed the team will sync on the FAQ/Guidelines documentation audit and report back in Review and update topics related to FAQ & Guidelines links.

• david clarified how “bundled plugin” rebuild hints can be misleading on older installs, and provided an actionable hook snippet to clean up plugin directories in Bundling more popular plugins with Discourse core (read more).

• nat acknowledged dashboard chart UX feedback and hinted at incoming improvements in Site Traffic graph rescaling, and also confirmed a fix landed for a tags-related bug in Slug generation none + new tag editor issue.

• tshenry closed the loop on a tags UX paper-cut (“missing tag group” error messaging) in Missing tag group error message.

• awesomerobot responded on two fronts: troubleshooting tag visibility in Restricted visibility tag groups visible on /tags, and offering a practical policy+automation approach for “must read/accept guidelines + intro” gating in Plugin or other option to require a post and a like?, with pointers to Discourse Policy, Discourse Automation, and Creating triggered custom badge queries.

• pmusaraj handled discourse-id support: requesting diagnostic logs in New users can’t sign up, 404 errors in console, and offering to clear credentials as a temporary workaround in Can’t set up Discourse ID: redirect URI already exists (similar guidance also appeared in the older solved thread Can’t setup Discourse ID: redirect URI already exists).

• Falco weighed in across SEO, SSO, ops, and privacy threads: clarifying canonical expectations in the solved topic Translated pages (?tl=) not indexed…, probing the threat model in the pr-welcome SSO email discussion Email exposed in DiscourseConnect Provider redirect URL, asking for infra details on embeddings load in Enabling AI search crippled my server, and live-testing onebox image caching behavior in Cache onebox images….

• supermathie helped narrow down a mobile-browser-specific issue (Mi Browser) and suggested escalating to the browser vendor in Mobile text-selection quote/copy buttons not working.

If yesterday taught us anything, it’s this: keep your Guidelines renamed, your oneboxes cached, and never let an outdated build steal your cake day frosting.

[system]

Today on meta.discourse.org…

Key Stats

• Total activity (last 24h): 51 new posts across 7 new topics, including fresh threads on chat, self-hosting, and plugins like a new points mall (read more).

• New topics opened (7):

  • Chat UX request: open straight into Chat / show Chat on landing page (read more)
  • Permissions: disable chat for moderators (chat) (read more)
  • Calendar UI: upcoming event icon is default (calendar-and-event) (read more)
  • Upload troubleshooting: members can’t upload more than one image (read more)
  • New plugin announcement: Discourse Points Mall (read more)
  • Self-hosting/SEO: serve Discourse on a WordPress sub-path (read more)
  • Theme/UI report (Foundation): search button wraps oddly (foundation-theme) (read more)

• Top users by posts & likes (with recent highlights):

User	Posts	Likes	Recent highlight
Falco	3	9	Shared a Data Explorer SQL to inspect AI spam logs (read more)
ToddZ	5	5	Pointed self-hosters to the canonical path-prefix guide for WP sub-path deployments (read more)
Huskijore	1	4	Asked about a direct-to-chat shortcut for communities migrating from Discord (read more)
jdc20181	1	3	Confirmed restricted tag groups behaved after a rebuild (tags) (read more)
Lilly	2	3	Clarified chat access rules for admins/mods and suggested checking upload concurrency settings (read more)
Monikas	3	3	Published an early WIP “Points Mall” plugin with check-ins, shop, and ledger (read more)
Andrew_Rowe	2	2	Recalled prior discussion around opening Chat directly and suggested searching meta for similar requests (read more)
noahl	1	2	Expanded on more flexible conditions/logic for Discourse Automation pipelines (automation) (read more)
lucy.sierracircuits	2	2	Reported multi-image upload limits persisting despite settings adjustments (read more)
asc	4	2	Continued debugging sign-up failures and console 404s for source maps (discourse-id) (read more)

Interesting Topics

Support

• eisammy asked how to disable Chat for moderators (keeping it admin-only), and Lilly confirmed moderators can’t be excluded when chat is enabled—while NateDhaliwal traced the behavior to core chat settings, likely requiring a plugin to override (chat) (read more)

• lucy.sierracircuits reported that members can’t upload more than one image per post; Lilly suggested also checking the simultaneous uploads site setting as a likely culprit (read more)

• pHneutre noticed the Upcoming Events sidebar icon showing as a generic link instead of a calendar; Falco advised it’s fixed in current Discourse and recommended updating (calendar-and-event) (read more)

• In a long-running moderation/admin thread, Lydia2 hit a confusing state where a user appeared silenced without an “unsilence” button; Bas suggested clicking “silence” again to try resetting the state back to normal (read more)

• A wiki-editing problem got a quick resolution: isaac pointed to a fix for an error when editing a Wiki Topic, then followed up as additional 500s were reported and the team started investigating further (read more)

#Self-hosting

• Huskijore (moving a community off Discord) asked whether Discourse can provide a home-screen shortcut that lands directly in Chat, or even a “latest-like” view that includes selected chats; Andrew_Rowe recalled similar prior attempts but no clean solution yet (chat) (read more)

• For SEO-minded WordPress operators, hritik asked how to deploy Discourse on a sub-path rather than a subdomain; ToddZ clarified the WP plugin is for integration and linked the canonical path prefix/subfolder setup guide (read more, plus background: read more)

• In troubleshooting a broken onboarding flow, asc and others continued digging into new users failing to sign up alongside console 404s (source map requests) and resource exhaustion errors, narrowing down what an anonymous user experiences (discourse-id) (read more)

• A Cloudflare hardening thread got an update as haydenjames shared real-world rulesets and planned to incorporate Discourse’s recommended WAF exclusions, especially around post creation and Data Explorer admin queries (cloudflare) (read more)

#Site Management

• In the Discourse AI spam tooling thread, LotusJeff asked for lower-level reporting behind the AI spam summary box; Falco replied with a direct SQL query to pull records from ai_spam_logs, pointing to #DataExplorer as the practical path to “show me the details” (ai spam moderation) (read more, Data Explorer reference: read more)

#Feature

• Naming polish landed: in the “AI Persona → AI Agent” discussion, Falco confirmed sam shipped the rename work, linking the implementation PR and closing the loop on the terminology direction (ai) (read more)

• In the automation redesign request (split automations into triggers and actions), participants pushed for more expressive workflows—especially delays and richer conditional logic—with noahl exploring how conditions could be composed with AND/OR and values pulled from trigger_context (automation) (read more)

#Plugin

• Monikas announced a new (very early) Discourse Points Mall plugin—daily check-ins, a shop, orders, makeup cards, and a points ledger—while explicitly flagging UI bugs and advising admins to wait before installing in production (read more)

ux

• A Foundation theme UI report (in Chinese) flagged a search button wrapping issue; awesomerobot said the fix is to prevent text wrapping in buttons and noted it should be resolved after updating Discourse (foundation-theme) (read more)

• On site chrome and default pages, the “FAQ/Guidelines and About pages” discussion continued: ToddZ and Andrew_Rowe outlined the practical value of the built-ins (default sidebar links, boilerplate, and discoverability/SEO concerns even if you “hide” them) (read more)

#Translations

• In a thread about poor French translations in automation UI, gerhard talked through the dream of in-context translations inside Discourse, noting Crowdin’s constraints around single-project in-context mode and hinting at experimentation in coming months (automation) (read more)

#Developer Guides

• A theme-dev thread got modernized guidance: MarkDoerr explained that legacy widget code is outdated due to the post stream changes, and suggested using a Glimmer component plus api.renderAfterWrapperOutlet to place user custom fields in the post header—linking back to the post-stream migration guidance (read more, migration context: read more)

#Site feedback

• Meta’s “collaborative content gardening hub” experiment kept chugging along: ToddZ proposed pruning obsolete “About page customization” topics now that the newer About-page docs and features exist, and linked several candidates for cleanup alongside the newer canonical references (read more, related hub: read more, About page announcement: read more, About page guide: read more, candidates: read more, read more, read more)

Activity by the @team Group

• Falco pushed forward both product clarity and admin pragmatics: confirmed the AI Persona → AI Agent rename landed (read more), provided a Data Explorer SQL to inspect AI spam log details (read more), and noted an Upcoming Events icon issue is already fixed upstream (encouraging an update) (read more).

• Bas helped troubleshoot an odd moderation UI state by suggesting a “toggle it to reset it” approach for a missing unsilence control (read more).

• isaac linked a confirmed fix for a wiki topic editing error, then acknowledged follow-up 500 errors and indicated the team is investigating (read more, follow-up report: read more).

• awesomerobot acknowledged a foundation-theme search UI bug and pointed to a fix that prevents button text wrapping after updating Discourse (read more).

• gerhard shared direction on improving translation workflows, including the idea of in-context translations inside Discourse and the constraints with Crowdin’s current project model (read more).

• tgxworld confirmed a fix is queued for object-type theme settings, linking the PR that will address it (read more).

• MarkDoerr provided updated theme-developer guidance for rendering custom fields near post headers using Glimmer components, referencing the broader post-stream migration work (read more, background: read more).

Between spam-log SQL, chat UX wishes, and Glimmer-powered theme fixes, meta spent the day proving that “it’s just one small tweak” is rarely just one small tweak (read more).