Today on meta.discourse.org…
Key Stats
- New posts: 134
- New topics: 15
Top users:
- Moin (23 likes, 14 posts)
- Falco (10 likes, 7 posts)
- sam (9 likes, 3 posts)
- david (8 likes, 2 posts)
- peternlewis (7 likes, 9 posts)
- chapoi (7 likes, 1 posts)
- Lilly (6 likes, 3 posts)
- darkpixlz (6 likes, 3 posts)
- merefield (5 likes, 8 posts)
- denvergeeks (5 likes, 2 posts)
Interesting Topics
- ludwikc suggested a new feature to turn chat threads into full-fledged topics. The proposal includes automatically closing the original thread and adding a link to continue the discussion in the new topic.
-
Tris20 reported an issue with the js.composer.reply_placeholder text appearing in both new topics and replies, suggesting separate placeholders for each.
-
Moin discovered that autolinking breaks the link added to the sidebar in the Administrators Index, affecting the display and linking of topics.
-
MarcP encountered difficulties with the search function when querying “down”, which was explained by Moin as being due to it being a stop word.
-
Eviepayne sought advice on scaling Discourse horizontally for a high-traffic community, considering separating Discourse frontend, Redis, and Postgres onto different servers.
-
peternlewis faced challenges upgrading to Discourse 3.3, encountering issues with the upgrade process both through the UI and manual methods.
- woozievert requested assistance with a Discourse installation that was failing due to an ActiveRecord error during database migration.
- A discussion about the new sidebar design on tablets continued, with users providing feedback on its functionality and appearance.
- Sidi_Codet reported responsiveness issues with the Discourse Central Theme on mobile devices, particularly in the user preferences section.
- merefield introduced an experimental feature in Chatbot 1.2.x that uses AI to collect User Field information, supporting text, dropdowns, and confirmations.
- Epoch posted a request for paid plugin or component creation, detailing three different desired functionalities including color-coding user names based on group membership.
- maiki suggested validating the Name field for AI tools to prevent errors caused by invalid characters in tool names.
- The new site traffic report sparked discussion, with some users reporting discrepancies in pageview statistics and requesting options to retain historical data.
Activity by the @team Group
sam addressed concerns about the new site traffic report, clarifying that no information was lost and explaining how to view all previous data. He also provided guidance on validating AI-generated responses before implementing automated systems.
Falco responded to inquiries about Discourse’s AI features, directing users to ask.discourse.com for a demo of the “talk with AI” feature. He also addressed security concerns, advising on proper reporting channels for vulnerabilities.
david assisted a user with troubleshooting template placement issues, recommending development against a proper development environment for better error messages.
chapoi confirmed that designs for multiple ‘new topic’ drafts are ready and on the development backlog.
Lilly made updates to the Halloween Decorations theme component and addressed issues with the Topic List Author component.
HAWK provided additional resources for preventing spam in response to a user’s concerns about Akismet failing to stop spam attacks.
jordan-vidrine directed a user to the appropriate feedback channel for the Discourse Central Theme.
joffreyjaffeux investigated issues with Discourse Automation, confirming the functionality of recurring triggers and group membership through badge scripts.
fitzy updated the documentation for setting up Discourse on Fedora Linux to include the installation of oxipng.
Thanks for reading, and I’ll see you again tomorrow! 