Résumé quotidien (13h UTC)

[system]

Today on meta.discourse.org…

Key Stats

• New posts: 82 (with lots of momentum around AI + admin tooling, e.g. AI translation + PMs and routing fixes like /llms.txt 404s).

• New topics: 9, including:

  • AI translation not translating 1:1 PMs (read more)
  • Root-level “system pages” like /faq + creating your own equivalents (read more)
  • Group mentions + scheduled topics in private categories (read more)
  • Production upgrade procedure for self-hosters (read more)
  • Sidekiq 8 support PR for mini_scheduler (read more)
  • Chinese UI alignment issue in the composer/category selector (read more)
  • Google Search Console acceptedAnswer warnings after an update (read more)
  • “Image could not be loaded” when clicking to zoom (read more)
  • Discourse CDN flagged for invalid SSL cert (read more)

• Top users (posts / likes in the last 24h):

  • pfaffman — 4 posts / 9 likes (notably cautioning about data safety in Plugin Cleaner)
  • Moin — 6 posts / 9 likes (clarifying scope of PM translation in AI translation + PMs)
  • Lilly — 5 posts / 8 likes (sharing permalink/static-page options in root-level links)
  • Falco — 1 post / 5 likes (proposing a more granular translation setting in AI translation + PMs)
  • sam — 3 posts / 5 likes (confirming router/route gaps behind /llms.txt in OpenClaw plugin thread)
  • nat — 1 post / 4 likes (previewing upcoming “translate these categories” controls in AI translation + PMs)
  • david — 2 posts / 4 likes (explaining the CORS impact of script type="module" in CORS after upgrade)
  • elmuerte — 1 post / 3 likes (noting foreign-key edge cases in Plugin Cleaner)
  • itsbhanusharma — 1 post / 3 likes (confirming /faq-style routes are hardcoded in root-level links)
  • tobiaseigen — 2 posts / 3 likes (reporting the “PMs not translating” confusion in AI translation + PMs)

Interesting Topics

#contribute:feature

• tobiaseigen found that AI translation appears “100% complete” yet won’t backfill 1:1 PMs, prompting discussion of clearer UI and a more granular setting set (including a proposed ai_translation_backfill_targets menu) in Help me troubleshoot why AI is not translating PMs on my site (ai content-localization). Related roadmap chatter: limit translation to specific categories and setting redesign ideas surfaced in-thread (read more)

#customization:extras

• A long-running integration thread surfaced a routing issue for “special paths” (like /llms.txt) depending on how they’re opened, and the discussion converged on missing Ember routes and the “two routers” tax in OpenClaw plugin for Discourse integration (with historical parallels to Safe Mode docs: safe mode topic). The fix was tied back to a core change (read more)

#customization:plugin

• The “cleanup after uninstall” debate returned: pfaffman warned that an automated remover is risky, while elmuerte highlighted how foreign keys can make leftover tables more than just clutter in Plugin Cleaner (and why reliable detection is hard) (read more)

Support

• paco asked how /faq, /privacy, and /about actually work (especially with must be logged in enabled) and how to add an /acceptable-use equivalent; the consensus: those routes are special/hardcoded, but Page Publishing + permalinks can approximate the desired behavior in How do root level links work? (see also: Page Publishing)

• Scheduling a topic for later publication still has sharp edges: group mentions won’t notify the way admins expect when a scheduled post publishes, leading to workarounds like editing after publish (and linking back to the known issue) in Question about group mentions in a private category (related: mentions don’t fire when scheduled post is published)

• A French-language Chat UX question turned into a “working as designed” clarification: in fullscreen, Chat becomes a dedicated page (no drawer close button), and channel switching moves to the sidebar in Pouvoir changer de canaux et de fermer en grande fenêtre chat (chat) (read more)

#Self-hosting

• After upgrades, some sites saw plugins fail due to CORS issues when using BunnyCDN, and the resolution leaned on understanding that newer systems increasingly load JS via type="module" (which requires correct headers) in All plugins not functioning due to CORS error after recent upgrade (cdn). The thread also cross-referenced older BunnyCDN/highlight.js behavior (read more) and the “why now?” explanation landed here (read more)

• Self-hosters compared upgrade methods (rebuild instance vs ./launcher rebuild app, and what “production-safe” means across channels) in Production upgrades - correct procedure to follow. The conversation pointed back to release/channel docs like Understanding Discourse release channels and Configure a supported tracking branch (read more)

• Tag/branch confusion and constrained networks came up again as david clarified how the rebuild script treats tags vs branches, and why a tag checkout can look “weird” but still be expected behavior in Help deploying older versions of Discourse

bug

• A setting expectation mismatch became a clarified limitation: “Use name for username suggestions” only applies to SSO/OAuth flows, not the local signup form—leading to a docs/description update in “Use name for username suggestions”: no effect on signup form? (signup) (read more)

• Google Search Console warnings about structured data reappeared after an update: “Either acceptedAnswer or suggestedAnswer should be specified” became actionable again and was tied to recent changes, with a fix queued in Google search console acceptedAnswer error (read more; related background: Either acceptedAnswer or suggestedAnswer should be specified)

• A report described a puzzling “Image could not be loaded” error only when clicking directly to zoom (but not when navigating via arrow keys), with testing suggestions around safe mode, cache reload, and account-based repro in “Image could not be loaded error” when click to zoom in (read more)

• Hosting surfaced a possible incident: Discourse-managed CDN domain was reportedly failing SSL validation (as observed via Cloudflare warnings) in Discourse CDN with an invalid SSL cert? (cdn)

Dev

• A contributor offered forward-compat help by opening a PR to support Sidekiq 8.1 in mini_scheduler, unblocking Rails app upgrades in PR: Add Sidekiq 8 support to mini_scheduler

ux

• A small but visible polish issue: when the category name is Chinese, the category dropdown and title input align slightly differently, producing a “not quite level” composer row in 中文类别选择框与标题输入框不对齐 (composer) (horizon-theme)

Activity by the @team Group

• Falco proposed reworking a single boolean into a more expressive setting menu so admins can explicitly choose translation targets—potentially including all PMs—in AI translation PM backfill targets.

• nat previewed an upcoming “translate these categories” feature and suggested splitting translation controls into clearer options like “translate PMs” plus category scoping in AI translation settings rethink.

• sam confirmed the /llms.txt behavior is a real routing gap (not just “documented weirdness”) and suggested tracking it properly in OpenClaw plugin thread, later noting why fixing it matters more than Safe Mode’s long-documented new-tab quirk in the same thread.

• zogstrip linked the /llms.txt + related 404s to an incoming core fix and pointed to the PR in OpenClaw plugin thread.

• david explained why “suddenly after upgrading” CORS problems appear: the migration to script type="module" makes correct CORS headers mandatory, especially for CDNs, in CORS errors after recent upgrade. He also clarified expected behavior when deploying tags/refs vs branches in deploying older versions.

• HAWK helped triage signup expectations by moving a report into bug classification in username suggestion setting report, and pointed to prior art around scheduled posts + mention notifications in group mentions + scheduled publishing.

• chapoi confirmed a reported Chat fullscreen “can’t close / can’t switch channels” behavior is expected and showed where those controls live in Chat fullscreen behavior explained.

• martin dropped helpful “this was already removed” context for FAQ/guidelines navigation changes in FAQ & Guidelines links review, and pointed admins to the current category-level setting for easier Solved-based support workflows in Support categories + discourse-solved.

Until tomorrow: may your CORS headers be correct, your /llms.txt route resolvable, and your “translate PMs” checkbox finally say what it means.