Resumo Diário (5h UTC)

Notícias e Eventos Resumos do fórum
857

Today on meta.discourse.org…

Key Stats

In the last 24 hours (2026-06-06 → 2026-06-07):

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

  • Moin — 4 posts / 10 likes (notably diagnosing AI language detection and translation state: read more)
  • stephtara — 5 posts / 4 likes (reported the locale/edit confusion: read more; and opened an admin-side editing error thread: read more)
  • Lilly — 2 posts / 4 likes (shared R2 migration tasks + ordering guidance: read more)
  • pfaffman — 3 posts / 4 likes (advised on port exposure / install expectations: read more)
  • David_Ghost — 3 posts / 2 likes (reported lingering “old thumbnails” issues after R2 move: read more)
  • typed-sigterm — 1 post / 2 likes (contextualized WeChat “mini program” expectations and browser realities: read more)
  • Andro — 1 post / 2 likes (raised a serious regression report around experimental nested replies: read more)
  • RGJ — 1 post / 2 likes (defended the long-running migrated password hash approach: read more)
  • Arkshine — 1 post / 2 likes (posted a major modernization PR for the image comparison slider TC: read more)
  • Idoru_Toei — 1 post / 1 like (confirmed a self-hosting “port 443” resolution + shared a runbook: read more)

Interesting Topics

#Site feedback

  • stephtara noticed a strange combo where a reply was flagged as originally written in French (despite being English) and where edits seemed “missing” unless viewing the correct (non-translation) version; Moin explained AI locale detection can be tripped by keywords and that viewing the “English translation” can make edits look outdated until translation refreshes (issue report, analysis + workaround).

bug

  • In an ongoing Cloudflare R2 migration thread, David_Ghost reported older uploads still resolve to the bucket endpoint URL (and thumbnails break unless a theme component is enabled), while Lilly recommended running migration + rebake tasks and ensuring DISCOURSE_S3_CDN_URL (or the “S3 CDN URL” setting) is set before migrating—and also suggested discourse remap for string replacement when needed (problem details, steps + ordering guidance).

  • A separate composer complaint (in French) resurfaced around “smart punctuation” behavior: apostrophe replacement is especially painful for French writing, prompting people to disable the setting even if they’ll miss emdash replacement (latest report, related locale/translation confusion elsewhere).

Support

  • Admin-side topic editing started failing for stephtara; early troubleshooting focused on checking the browser console and site logs, and narrowing down by disabling problematic plugins (notably “Discourse Custom Wizard”) to see if edits succeed again (initial error report, first debugging steps).

  • A mobile Safari regression on iOS 26.5 was reported where the new topic composer editor becomes too small/crushed, while replies still appear usable; the report notes it reproduces on try.discourse.org and includes UA/device context for debugging (screenshots + environment, reference capture).

  • Experimental nested replies was described as a “can’t-revert” disaster: enabling it allegedly led to confusing UI for users, “disappearing” posts, then error pages when attempting to disable—leaving the site in a broken state and prompting requests for rollback/debug steps (problem statement, read more).

  • In Discourse Automation, one1 successfully templated one profile field via {{languages}} but found other custom/required fields didn’t resolve—raising the question of how field names map to automation variables and whether a code fix is needed to avoid renaming fields (working vs failing variables, read more).

  • A solved self-hosting setup thread turned into a practical “runbook” for Virtualmin/Webmin users: pfaffman emphasized not installing Postgres manually and suspected port exposure conflicts, while Idoru_Toei ultimately got things running (using --skip-connection-test) and documented cleanup + install steps for subdomain setups (diagnosis, solution + runbook).

ux

  • “New Topic” button visibility continues to be a pain point in read-only / restricted categories; Moin pointed to a merged core change introducing a hidden setting hide_disabled_create_topic_button to restore older behavior by hiding the button when the user lacks create permissions (context + pointer, read more).

#Self-hosting

  • A Russian-language SEO question about adding an H1 on the homepage prompted pfaffman to remind that crawlers see a different (server-rendered) view than users do in the JS app, and that Discourse already handles SEO well—encouraging clarity on the actual SEO goal before changing templates (SEO caution, read more).

#Site Management

  • Auto-bump tuning got a feature suggestion: instead of bumping based purely on category selection, patrickemin proposed incorporating “interest” signals (views/votes) and topic age thresholds—while also referencing a related desire to avoid repetitive auto-bump alert noise (feature suggestion, related alert-noise discussion).

#Theme component

  • The image comparison slider theme component saw a big modernization update proposal: Arkshine shared a PR adding zoom/pan, fullscreen, lightbox originals, better handles/labels, keyboard accessibility, group-based insertion controls, and RTE editing—while keeping backward compatibility via a new [wrap] format (and noting 2026.6.0-latest is required) (feature rundown, read more).

#Theme

  • On the long-running FKB Pro – Social theme thread, xlg256 reported inconsistent “clickable areas” on mobile topic cards causing confusing hit-or-miss taps and accidental navigations; they proposed restricting click targets to core content and shared a CSS pointer-events “whitelist” approach as an interim fix (UX problem + suggestion, read more).

development

  • A WeChat mini program integration discussion revisited whether embedding Discourse inside an app-like container is worth it; participants highlighted WeChat constraints (openid/token needs, audits/content review), the friction of requiring email, and the cultural reality that many users expect “mini programs” over standalone browsers—especially given outdated Chromium forks common on devices (integration discussion, China browser context).
    • The thread also pointed back to earlier WeChat-login/plugin caveats, especially around WeChat not exposing email (related topic, read more).

#Migration

  • A PHPBB migration optimization thread briefly detoured into password handling: pfaffman recommended the long-established “migrated password hashes” approach for self-hosters, and RGJ pushed back on blanket security concerns—arguing the plugin has a long track record when insecure password allowances are disabled (plugin mention, security clarification).

Activity by the @team Group

No posts from the @team group were recorded in the last 24 hours within the captured threads for this digest. For reference, the newest/most-active topics during the window included:

If yesterday taught us anything, it’s this: may your port 443 stay reachable, your thumbnails rebake on the first try, and your AI stop insisting everything is written in French.