Hello from Danielle + Supporting Community Initiatives Danielle shared her new role supporting the Meta community, recapped recent webinars, and invited feedback on future events community-strategyread more
Problème accès aux onglets des paramètres des catégories gilles reported missing security & image tabs in category settings due to the Locations plugin, and merefield merged a patch to resolve it Supportread more
Change in behaviour re mail Andro flagged the new “Someone replied to a topic you are Watching.” preheader, Ethsim2 traced it to %{email_preview}, spurring discussion on template overrides Supportread more
Show Full Name only in specific categories newbit1337 asked if users can toggle between username/full name per topic; Lilly pointed to an existing feature request and noted a custom plugin would be needed Supportread more
Title seems unclear for “Moros Protocol” on my forum hipp0 discovered title entropy restrictions prevented “Moros Protocol” and supermathie explained lowering the title min entropy setting fixes it Supportread more
Untranslated text when creating a poll: “Allow options to be added or removed after posting” Davi_Araújo noted a missing Portuguese translation on poll creation, and Moin explained community translation workflow Supportpollsread more
No visual or message showing when there is no /unseen content Richie requested a “Nothing unseen at the moment…” message on the /unseen page, and Moin suggested adding a default empty-state illustration UXread more
403 error for /discourse-ai/credits/status?features[]=topic_summaries when logged out Moin spotted console errors on AI credit checks and awesomerobot fixed it in PR #37070Bugairead more
The “Discobot discoveries” search results on Meta Lilly saw external links in AI-assisted Discobot results; Moin explained forum-address replacement quirks in the search algorithm Bugsearchairead more
Div with id “skip-links__container” appears above header in vertical orientation awesomerobot merged a margin tweak to fix skip-link positioning; upcoming in the next update BugUXread more
Composer stuck in “Saving” state when topic requires moderation awesomerobot acknowledged the report and merged PR #37067 to resolve the save-lock issue Bugcomposerread more
Authenticated ICS feeds for private calendar events Ethsim2 proposed per-user tokens for private ICS export; community weighed in on aligning with private RSS/Atom workflows Featurecalendar-and-eventread more
Discourse Gifs: Has anyone else received an email about the deprecation of the Tenor API offering on June 30, 2026?Moin flagged the change and Falcomerged Klipy support in a flash.
Right Sidebar Blocks: xu2 asked how to show the right sidebar on every topic page; Lilly explained it only applies to list routes and bryce confirmed the compatibility limitation.
Usability und UX Unterstützung für eine gemeinnützige, Discourse-basierte digitale Selbsthilfeplattform: Aurora is recruiting Discourse experts to enhance usability, structure, and workflows on their neurodivergent self-help instance; Lilly and RGJ already offered their services read more.
REQUEST: Highly Effective Age Assurance (OneID Phone No. Age Verification) Integration: BJPickles proposed a OneID-based HEAA plugin for UK compliance; NateDhaliwal and pfaffman weighed in with SSO alternatives and plugin advice read more.
Add link to sidebar category setting to new admin menu: Moin suggested an “edit sidebar default” option near “edit sidebar categories” to reduce confusion; the community debated the UI wording and visibility read more.
Ability to display all the likes/reactions on a post: Arif33 urged the team to revisit the reaction cutoff threshold, noting that hidden likes can dampen engagement in busy communities read more.
Inviting another user to an existing personal message: EricGT clarified that the “+” button under the first PM post replaces the old “Add or Remove” link after PR #34022, ending confusion over private message invites read more.
The ⊕ composer menu is not accessible by screen readers: dfabulich reported that VoiceOver users cannot dismiss the composer menu; j.jaffeux and awesomerobot tested and traced the issue through recent PR #34615 fixes.
Unexplained Email::Receiver::InvalidPost errors: lavamind dissected multipart Mailman messages triggering InvalidPost; supermathie dug into Email::Cleaner and the mail gem’s part reordering, pinpointing the root cause for further investigation.
Locations Plugin : merefield highlighted a recent fix for UserLocation state handling and shared a Rails console script to identify and correct bad data, calling for PRs or rake tasks to automate the cleanup read more.
Take the New Carousel Mode for a Spin: oshyan and NateDhaliwal confirmed that the image carousel is live; the thread turned into a light-hearted riff on Discourse as “the next dating app,” complete with meme reactions read more.
Restore button not active: Saiano discovered the missing “Restore” button when migrating to a new server; Moin identified that enable_backups must be enabled in addition to allow_restore to re-enable the feature read more.
Can’t create Wiki (as admin): jenmck hit a Forbidden error when creating a wiki; renato traced the issue to custom plugins still executing guardians code and advised toggling them out of the YML to isolate the culprit read more.
#Self-Hosting
Setup Cross-Origin Resource Sharing (CORS): HaPe asked about limiting CORS headers to /latest.json; the community reviewed header configuration options to balance security and selective data sharing read more.
The AI Search Revolution’s Hidden Dependency: In a new blog post, mae explored how structured forum threads power AI synthesis, positioning Discourse as a trusted knowledge substrate for next-gen search read more.
FKB Pro – Social theme update: Don shipped live auto-refresh and cross-tab sync to the FKB Pro panel, introduced fkb_panel_cache_ttl, and confirmed compatibility with Glimmer Post Stream. read more
hipp0 encountered a “conflict with edit” alert when using the preview arrows in Conflict with edit, and Lilly guided them on checking console errors and splitting distinct questions into separate topics (reply #2) read more
That’s a wrap for today—after diving into import scripts, chat pins, and disappearing search shortcuts, here’s hoping your next rebuild goes a little smoother!
sam announced a major upgrade to the Discourse Math plugin (tags: math) in A new release of Discourse Math, bumping MathJax to v4.1, improving LLM-friendly rendering, and enabling KaTeX toggles. read more
sniper756 kicked off a lighthearted chat asking if the recent flurry of updates has settled down after the holiday lull and xenForo → Discourse migration buzz—mcwumbly explained our continuous delivery strategy and upcoming admin controls (discussion)
Don proposed a visual indicator for watched-words auto-links—an icon + tooltip to distinguish system-generated links from manual ones, boosting transparency and trust (proposal)
tom_eric unveiled an AI-powered “meaningless reply” filter prototype combining regex and LLM classification to hide low-value replies, offer summary sentences, and let moderators tune sensitivity (ai) (idea)
taravasya asked how to restrict watched words to specific categories or threads rather than forum-wide, sparking pointers to category-based restrictions (watched-words) (thread)
chapoi debated updating the topic voting icon in user activity to a “check-to-slot” symbol, aiming for UI consistency with topic cards (topic-voting) (details)
JJde suggested including poll options directly in HTML email notifications (in addition to plaintext), so users can vote on the go without clicking through (email, polls) (request)
bck055 asked if quiz forms with explanations exist—looking for a way to show an explanation popup upon answer selection and review results later, akin to enhanced polls (question)
TypicalThieves reported Discord signup errors under #hcaptcha: users see “email already registered” banners overshadowing the captcha prompt on self-hosted sites, causing confusion (report)
RGJ rescued a hung restore by toggling off S3 uploads before backup and back on after, fixing the “restore cancelled at migrating uploads to S3” scenario (solution)
Multiple admins diagnosed SMTP “end of file reached” errors post-update, tracing failures to Sidekiq and patching with commit c7e9cddb069c on latest-release (+153) (email) (details)
Neil_Evans and zogstrip confirmed the post_created_edited DiscourseEvent now fires reliably across processes, clearing up inter-process confusion for automations (automation) (confirmation)
apf fixed a group watchlist API error by moving "update_existing_users": true outside the group object in the JSON payload when calling PUT /groups/{id}.json (groups, rest-api) (fix)
祁同伟 requested more granular Discourse User Location (state/province level) and a theme component to display this in topic headers, teasing location-based customization (Plugin) (feature request)
shortmort37 uncovered attachment order issues in the phpBB3 import script: imported posts with many images had reversed attachments, and community members shared patches to preserve original ordering (phpbb) (report)
#USING DISCOURSE
hendersj asked if flag notification emails to users can include the moderators group, not just admins, to help non-English moderator teams collaborate on flagged content (moderation, reference) (discussion)
Moin highlighted difficulty entering special formatting like [wrap] in automation message composers—the RTE escapes example code, so themes can’t register templates in that menu (automation) (details)
mcwumbly explained our continuous delivery cadence and preview-first feature toggles in the General update frequency thread (link)
zogstrip confirmed the post_created_edited automation event now triggers properly after edits, helping surface misconfigurations in Rails console tests (link)
chapoi weighed in on the topic voting icon refresh, aligning user activity and topic card iconography (topic-voting) (link)
Keep the energy high—41 posts later, our meta community is humming like a finely tuned plugin!
Rotating Composer Placeholder (composer): Ethsim2 introduced a theme component that rotates the Discourse composer’s placeholder text each time it opens, fully configurable via theme settings. GitHub repo • Beginner’s guide • read more
“If you put just one, it’ll soon be ignored… If you put all of those, no one would read any of them.” — pfaffmansee post
本轮大规模更新终于告一段落了?: sam kicked off a discussion on whether the recent large-scale refactor is winding down, noting a spike in code removal after MathJax was pushed out. view discussion • artifact full screen
Discourse Group User Status (user-status): Lilly released a plugin that restricts who can set and display user statuses, with group-based permissions, admin override, and automatic cleanup. repo • install guide • read more
Resenha – Add Discord-style Voice Rooms: nathank praised the Voice Rooms plugin for lightweight, on-the-fly voice conversations and requested tighter chat integration and AI transcription. experience thread
Discourse User Location: 祁同伟 enabled the user-location plugin but encountered missing location data on user cards; the community is investigating. issue details
Bulk tag creation rejects tags with uppercase letters (tags): Moin reported that uppercase tags (e.g., “UppercaseTag”) are wrongly rejected during bulk creation, despite being allowed via the regular UI; flagged for post-tag-overhaul fixes. bug report
Rich text editor erases HTML tags from post (composer): seanblue discovered that <br> tags disappear when editing a post in rich text mode, breaking tables in wiki posts—a confirmed regression in the inline/table editor. initial report • developer confirmation
Unexplained Email::Receiver::InvalidPost errors: lavamind observed new InvalidPost errors logged with Access Denied reasons post-upgrade, showing unexpected rejection details in email processing. error logs
Discourse forum AI configuration limits for individual users (ai): Moin clarified that the built-in “quota” feature already tracks AI usage per individual user, not shared across the group. question • answer
Quiz form with explanations?: merefield and pfaffman explored the feasibility of an educational quiz plugin using topic custom fields and new models for user responses, referencing the Experimental Form Templates work. plugin discussion • form templates
Using Tools as Pseudo-Agents for Specialized Directives (ai): BrianC shared a pattern for invoking specialized “agent” tools via custom JavaScript in Discourse AI, keeping the core system prompt lean and injecting edge-case logic on demand. conversation
Access common chat channel actions from the sidebar context menu (chat): martin merged a fix that restores missing chat actions in the sidebar menu. pull request • announcement
Horizon: High Context Topic Cards (horizon-theme): AquaL1te asked if admins can enforce topic excerpts for all users in Horizon; the team is looking at the always_include_topic_excerpts setting. topic
A new release of Discourse Math (math): sam confirmed that SVG rendering is available as a site setting, accommodating forums that block custom fonts. feature discussion
Creating a component to staff-limit user status (user-status): Moin pointed back to a 2023 Dev thread where a plugin for per-group status permissions was proposed, linking to the newly released Discourse Group User Status plugin. original thread • plugin
sam contributed to General in 本轮大规模更新终于告一段落了?link, confirmed the br-tag bug in Rich text editor erases HTML tags from postlink, and weighed in on SVG options in A new release of Discourse Mathlink.
nat chimed in on General with a warm welcome in 本轮大规模更新终于告一段落了?link and acknowledged the uppercase-tags bug in Bulk tag creation rejects tags with uppercase letterslink.
martin merged the sidebar chat actions fix in Access common chat channel actions from the sidebar context menulink.
Here’s to hoping your placeholders stay fresh, your tags stay lowercase, and your community stays as lively as yesterday’s whirlwind of posts!
hipp0 discovered that their group @mention name for trust level 4 had been changed and couldn’t revert it; Moin pointed them to examine the groups.default_names.trust_level_4 site text and recommended using CSS safe mode for debugging (393762/1, customize-text guide).
Nick-Permaculture ran into an issue where one subcategory refused to save permission changes; Lilly requested the parent category settings screenshot, and Moin traced it to a 3-digit color code bug matching 383099/1 (393825/5, 383099/1).
A user forgot which setting excluded categories from the Latest page, and Moin & Lilly reminded them to check the default_categories_muted site setting or the suppress-categories plugin (393802/1, discourse-categories-suppressed).
Andro raised a complaint about the new email preview prefix and asked where to customize it; chapoi suggested updating individual user_notifications.user_posted.preview site texts and Moin shared the site-text editing workflow (393781/1, 393205/11).
hipp0 wanted to restrict uploads by subscriber group rather than trust level; itsbhanusharma highlighted that trust levels map to groups, Moin pointed to the Restrict uploads theme component for extension, and Heliosurge offered a code snippet from #112688 (393763/1, 112688).
tobiaseigen reported that mail stopped sending after migrating to Hetzner; supermathie walked through openssl s_client diagnostics, Ethsim2 suggested trying port 2525, and Hetzner’s firewall docs clarified why ports 25 & 465 time out by default (393621/1, Hetzner FAQ).
Saen noticed the From: header lost its “via SITENAME” text; supermathie linked to the commit that removed it and pfaffman discussed the redundancy-reduction rationale (393814/1, commit 826d346).
As of June 4, Let’s Encrypt no longer sends expiration emails, making LETSENCRYPT_ACCOUNT_EMAIL obsolete; pfaffman proposed removing the conditional in the Docker SSL template (393831/1, template snippet).
Android users on Chrome reported that closing a topic then reopening jumps to an earlier post; Moin recommended testing in safe mode to rule out theme or plugin conflicts (393830/1).
Moderators observed that cleared items reappear in the new review queue immediately after approval, possibly due to secondary AI spam checks; the thread is collecting further examples to isolate the root cause (393804/1, #review-queue).
#Hosting
Ethsim2 documented two hosting patterns—multiple standalone installs vs. multisite—and linked to the HAProxy rebuild 503 workaround; he and david clarified Redis isolation requirements for separate sites vs. scaled web setups (392692/51, HAProxy 503 workaround).
The Horizon theme component gained a “High Context Topic Cards” option; chapoi confirmed admin overrides of user preferences and zogstrip provided an su discourse command to toggle the excerpt setting (393470/8, theme guide).
A user requested a per-user toggle to hide AI summarization nudges; Canapin noted the Discourse team’s reluctance to add extra settings without traction, and awesomerobot reminded that an admin-controlled AI toggle already exists (393818/1, feature request).
After customizing the Subscribe title, hipp0 discovered it also changed the button label; NateDhaliwal traced this to the product-item.gjs component in the Discourse Subscriptions plugin (393766/1, product-item source).
Florent was stuck on the “Register Admin Account” screen despite having an active admin; pfaffman suggested defining DISCOURSE_DEVELOPER_EMAILS or bypassing the prompt via /login to proceed (393828/1, login bypass).
zogstrip clarified the new email preview prefix in topic 393781/2, merged the two-emoji title bug fix in 389922/8, and applied the silenced account resolution in 392090/5.
supermathie diagnosed SMTP hang-ups in 393621/8 & 393621/10, traced the missing “via” header to a core commit in 393814/4, and suggested an RTE fallback for HTML tag erasure in 393758/6.
chapoi outlined admin-enforced defaults for high-context cards in 393470/8 and integrated the vote-icon update via 393695/5.
HAWK proposed splitting the HAProxy vs. multisite discussion into its own thread in 392692/58.
awesomerobot noted that admins can globally disable AI features with a single toggle in 393818/10.
No puppies were harmed in the making of today’s summary—let’s keep it that way tomorrow!