Daily Summary (5am UTC)

Site feedback Forum summaries
519

Today on meta.discourse.org…

Key Stats

Interesting Topics

Bug

  • Self-hosted discourse instance appending “7d” to the FQDN
    odhiambo discovered that email links were landing on …or.ke7d/admin instead of /admin; Moin traced it to a typo in the Admin Quick Start guide and submitted a fix read more.

  • Topic notifications emails not being sent if adding a Staff Colour to the post
    Richie confirmed that applying a staff colour changes post_type and prevents notification triggers; this was reproduced and logged for a future patch link.

Support

  • Why does the like count show for the entire topic?
    MihirR asked why the topic list displays topic-wide like counts; merefield and NateDhaliwal clarified that the like count reflects all likes in the topic, not just the first post discussion.

  • Unable to grant Admin to user
    WolfpackFan couldn’t upgrade a migrated user to admin because they accepted the confirmation link in the wrong session; JammyDodger walked through the correct workflow and resolved the issue details.

  • How does group messaging work in Discourse?
    HAWK asked about associating chat channels with custom groups; the thread reviewed current behaviour of category-based auto-join channels and DM group chats, noting that true group-based auto-join remains a requested feature chat here.

  • Not receiving admin verification email after setup
    Nicca reported never getting the initial verification email; ondrej pointed to the Troubleshoot email on new Discourse install, while JammyDodger and pfaffman recommended switching SMTP to port 2525 or contacting DigitalOcean support more.

  • General question about Saved Replies
    Rubi asked if templates can be restricted to moderators and how to create personal saved replies; Moin explained that templates respect category security, demonstrated a staff-only subcategory setup, and linked to the Discourse Templates plugin read more.

  • Hooks from: & to: syntax in yml to disable anonymous searches
    opcourdis blocked anonymous searches by setting DISCOURSE_RATE_LIMIT_SEARCH_ANON_GLOBAL_PER_MINUTE: 0 in app.yml; Falco confirmed this effectively disables /search for non-logged-in users without affecting authenticated sessions discussion.

Community

  • Use of Flags
    TonyG kicked off a debate on whether moderation equals censorship; voices ranged from riking’s suggestion to start a PM with moderators to Heliosurge’s broader view of content control, with Jagster arguing for a clear distinction. Lilly challenged the notion that toolkit limitations were at fault thread.

#DATA & REPORTING

  • Anonymous views suddenly very high
    agemo saw a surge in “Anonymous” traffic on Google Analytics, speculating about AI-driven bot traffic; ryan_olsen recommended fronting with CloudFlare and geo-blocking, and the discussion covered SSL mode nuances details.

General

  • DNS4EU, is it for me?
    patrickemin asked if the EU’s new DNS resolver enhances Discourse security; Falco clarified that DNS4EU is a public resolver and only affects client-side lookups, not self-hosted Discourse instances info.

Feature

  • Push notifications PWA or iOS
    ryan_olsen inquired about true push on mobile PWAs; NateDhaliwal pointed out that the Discourse mobile app supports native push, and guided on enabling browser notifications in /my/preferences/notifications more.

  • Feedback for Ask Discourse
    Ed_S noted that Ask sometimes suggests posts in restricted categories; the thread is exploring ways to filter out non-public results and improve AI prompt handling discussion.

Announcements

  • AI Artifact User storage
    MachineScholar and NateDhaliwal brainstormed a UI for custom artifact storage instead of SSH or Web Creator persona workarounds, highlighting use cases for code help forums discussion.

  • Webinar: Meet the Discourse Customer Projects Team
    satonotdead asked why Zoom is used and whether recordings will be posted; ondrej confirmed each webinar is recorded and shared under the #webinar tag for on-demand viewing details.

Activity by the @team Group

That’s a wrap—between bug fixes, email deep-dives, and AI artifact dreams, the forum logged enough troubleshooting and brainstorming to power a rocket… or at least a really enthusiastic puppy playdate!