A user sought help replacing the AI robot header icon. mcwumbly provided links to topics about replacing icons, and Lilly shared a code snippet for replacing the robot icon with a rocket icon using FontAwesome 6.
Musa_H encountered issues with their theme being stuck in dark mode. Moin suggested checking browser and device settings, and provided information on disabling the default dark mode color scheme.
In the FKB Pro - Social theme topic, Jagster reported a compatibility issue with the Full Row Bulk Select component, causing layout problems on desktop and mobile. Don clarified that the feature is already integrated into the theme.
A user inquired about the status of an e-commerce plugin for Discourse. pfaffman indicated no progress had been made but offered to discuss further if a budget was available.
In the Filtered Topic Lists theme component discussion, jrgong asked about the best way to hide the core topic list when displaying the filtered list in a specific category.
chapoi expressed concerns about making image resizing more obvious during uploads, suggesting it might make the interface busier without addressing a real discoverability issue.
mcwumbly announced the release of 3.4.0.beta2, highlighting new features such as better pageview metrics, multiple category moderator groups, and the ability to watch chat threads.
sam provided insights on AI features in Discourse, explaining that not installing or enabling the AI plugin is sufficient to remove AI features. He also suggested improvements for the AI proofreading feature, including background proofreading and user settings for automatic proofreading.
lindseymoved a discussion about the AI proofreading button to the UX category and shared information about ongoing composer redesign efforts. She also followed up on chat sound issues.
keeganproposed an option for automatic proofreading similar to automatic image captions. He also mentioned plans to update the Markdown Flavors theme component.
jbrains sought advice on archiving a site and integrating existing comments into blog posts. The community offered suggestions for preserving and utilizing the content.
omarfilip reported issues with a slow site after restoring from a backup. Falco suggested removing the Post Badges component, which initially seemed to help but didn’t fully resolve the problem. Moin shared some potential Cloudflare-related solutions read more.
db0 reported issues with ActivityPub federation between Discourse and Lemmy. angus provided guidance on setting up Actors for categories to make them discoverable read more.
pmusaraj reported that the iOS CSS loading issue persists in the latest Safari on Sequoia and reopened the upstream Webkit bug report.
tobiaseigen discussed potential improvements to custom flag management and mentioned the possibility of increasing the limit on flag reasons for hosted customers.
xandra.cc reported an issue where users could no longer edit any posts since updating to 3.4.0.beta3-dev. Moin suggested a fix related to the discourse-reactions plugin, which resolved the problem.
RGJ encountered a problem with overriding text in Discourse 3.3.2 stable. The overridden text was still present but not displaying correctly. Moin provided some troubleshooting steps to help identify the issue.
NateDhaliwal suggested renaming the ‘user_archive.csv’ file in user archives to ‘posts_archive.csv’ or something similar for clarity.
Support
Rick_Jing encountered a 500 internal server error when trying to create a topic with tags via the REST API. Firepup650 pointed out a security concern with visible API keys in the screenshot.
NateDhaliwal introduced a new Discourse Persistent Banner theme component that displays a banner at the top of every page, which can only be hidden by admins. The component sparked discussion about its functionality and potential improvements.
davidtdc3377 sought advice on rounding login buttons for platforms like Google and GitHub. ondrej provided a helpful solution, linking to a guide on making CSS changes.
Shauny reported issues with enabling the AI button in the toolbar, discovering it works differently on mobile devices. Moin explained recent changes and advised waiting for the next stable release.
Lilly provided feedback and suggestions on the Discourse Persistent Banner theme component, offering insights on improving its functionality and customization options.
joo asked about triggering AI-generated replies when users create new topics or posts. sam mentioned ongoing work on this concept for personas but expressed concerns about potential noise in topics.
NateDhaliwal found a solution for using Plugin Outlet Connectors from a Theme or Plugin, involving creating .hbs and .js files for different outlets and checking the banner_location setting value.
A user needed help setting up Discourse on Ubuntu 22.04 for organizational use. pfaffman advised setting up a reverse proxy for HTTPS termination and provided a link to a guide on running other websites on the same machine as Discourse.
hoangphuctran93 suggested improvements for the Code-block line numbers theme component, including options for dark or light themes and shared some custom CSS for terminal-like code blocks.
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.
Eviepayne sought advice on scaling Discourse horizontally for a high-traffic community, considering separating Discourse frontend, Redis, and Postgres onto different servers.
Epoch posted a request for paid plugin or component creation, detailing three different desired functionalities including color-coding user names based on group membership.
The new site traffic report sparked discussion, with some users reporting discrepancies in pageview statistics and requesting options to retain historical data.
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.
joffreyjaffeux investigated issues with Discourse Automation, confirming the functionality of recurring triggers and group membership through badge scripts.
gurtz reported an issue where “in reply to” links were no longer working on their forum. After some troubleshooting, it was determined to likely be a forum-specific issue. Moin suggested finding steps to reproduce the issue and sharing them for further investigation read more.
ludwikc inquired about marking all posts as read for users wanting to achieve “Inbox:0”. pfaffman explained that Discourse doesn’t allow marking posts as read without actually reading them, but users can dismiss unread and new posts read more.
baronesh accidentally deleted a member and asked about undoing the action. pfaffman explained that for users with few or no posts, deletion is immediate and can’t be undone read more.
rishabh provided guidance on running Discourse in production, suggesting the use of Docker for production environments and linking to the official installation documentation.
Lilly assisted a user in locating specific pages within their Discourse instance, providing screenshots and instructions on how to access the desired settings.
natmerged a fix for an issue with focus shifting while searching the user directory. However, this introduced a new bug affecting table headings for plugins, which nat acknowledged and humorously responded to.
The new sidebar design on tablets was discussed, with chapoi announcing an update to add the divider on tablets as originally intended. This change aims to improve the user experience on tablet devices.
A fun and festive theme component called Discourse Confetti Clicks was introduced. Lilly suggested tying it to the automation for members’ birthdays, adding a celebratory touch to the forum experience.
MCATAKCIN shared their success story of reaching nearly 1,000 members in 1 month using Discourse. They sought advice on customizing the Reddit-ish theme to resemble Twitter’s layout. denvergeeks provided CSS code to achieve the desired three-column responsive design.
mjbergman92 encountered challenges while attempting to reverse proxy into Discourse. With guidance from Falco and others, they successfully set up the reverse proxy and resolved Mixed Content errors by enabling force_https and adding the x-forwarded-proto flag in nginx proxy manager.
peternlewis continued to troubleshoot their upgrade to Discourse 3.3, which was failing. pfaffman suggested upgrading Docker as a potential solution and advised against trusting OS upgrades.
wenqin sought guidance on configuring the Discourse Doc Categories plugin, specifically regarding the location of certain icons and setup instructions. Community members provided step-by-step assistance.
MCATAKCIN shared tactics for strengthening their community, including insights on community building, copywriting, and conversion rate optimization. They emphasized the importance of collective effort in achieving visibility online.
LVA reported that the reply composer is still broken on Firefox mobile, providing details about the browser version and operating system. This ongoing issue affects the mobile user experience for Firefox users.
ganncamp discovered a useful auto-linking feature in Discourse, similar to Slack’s functionality. This feature automatically creates links when pasting text, potentially saving users hundreds of keystrokes over time. Read more
renem inquired about webhooks for whisper posts. simon explained that while there’s no specific webhook for whispers, users can filter for whisper posts in the code receiving the webhook. Read more
Users reported issues with restoring backups due to a missing chat_mention function. kendoer found a solution by updating the old server to match the new installation’s version before creating a new backup. Read more
Monikas noticed that medals disappeared after an update in the Post Badges theme component. david recommended ensuring the latest Discourse core version is installed and suggested reinstalling the theme component if the issue persists. Read more
The_Alchemist expressed frustration over the lack of a drafts feature in Discourse, seeking advice on how to manage 65 published posts they wanted to keep private. Moin suggested using unlisted topics or creating a private category, while Jagster recommended using a personal category and topic timers for publishing. The discussion highlighted the ongoing debate about expanding draft functionality in Discourse. Read more
A user mistakenly posted about an “Empty Queue” issue on meta.discourse.org, thinking it was their community’s forum. Moin clarified that this was a general Discourse forum and directed the user to their specific community for support.
The discussion on hiding IP addresses from moderators continued, with Jagster, schneeland, and others debating the legal and privacy implications of IP address visibility, particularly in relation to GDPR compliance.
Trancos resolved an SMTP mail sending issue by using the server’s IP address and adjusting SSL verification settings, highlighting potential DNS-related complications in Discourse setups.
Amicable reported an issue with the Discourse AI plugin where topic links were being replaced with “slug” in the URL, seeking clarification on the cause and potential solutions.
A discussion about creating a cryptocurrency idea submission plugin with API integration continued, with pfaffman suggesting potential solutions for handling large numbers of tags and inquiring about the project’s budget.
Monikas reported difficulties in getting the Post Badges theme component to work, noting that while the plugin version functions, it lacks customization options for displayed medals.
Rizal shared a helpful resource for learning LaTeX, particularly for beginners. simon contributed by sharing a useful PDF reference for LaTeX symbols. The community appreciated these resources for improving their LaTeX skills. read more
Don introduced a new theme component called “AI Bot - New Question Modal”. This component adds a modal for AI-powered question suggestions when creating new topics. Jagster provided feedback on mobile usability, noting some display issues on iPhone. read more
The topic of hiding IP addresses from moderators continued with discussions about privacy concerns and the potential need for this feature in certain communities. mcwumbly confirmed that while not a current priority, Discourse is open to adding this feature and marked it as pr-welcome. read more
Users discussed issues with the Discourse AI Topic Summary plugin, particularly regarding link generation in local development environments. merefield clarified that the plugin is designed for production use and offered to accept PRs for improved localhost support. read more
A PG13 compatibility issue was reported when restoring PG15 backups on PG13. ted provided a workaround and inquired about the specific use case to better understand real-world scenarios. read more
Paul_King sought advice on creating a hybrid public/private forum for architects and laypeople, with different signup experiences and access levels. The community discussed potential solutions using custom fields and plugins. read more
A restore failure issue due to a missing chat_mention function was discussed. RGJ explained that the problem occurs because migration timestamps don’t always match commit times, causing version mismatches during restores. The solution is to ensure both source and destination sites are fully up-to-date. read more
merefield announced the release of Chatbot 1.3, introducing new features such as token-based quota management, cost tracking for API calls, and a function for users to check their remaining quota. read more
Paul_King started a discussion about alternative sign-up pathways for different user types, with Don suggesting solutions using authentication validations and automation plugins.
T_Disco explored the functionality of solved/unsolved filters in category pages, with Moin clarifying that it depends on whether solutions are enabled for specific categories.
A new blog post was published discussing how Discourse serves as a primary workplace collaboration tool, with JimPas noting an issue with the newsletter signup form that stella investigated.
A discussion about simplifying forum interfaces where Firsh sought advice on making Discourse more accessible to non-technical users. awesomerobot provided detailed insights on potential UI simplifications and limitations of Reddit-style nested replies.
Moin reported an issue with broken text in the account deletion process, where “home” was accidentally changed to “house” during the FA6 icon upgrade.
willie initiated a discussion about theme components for group images, seeking help identifying a specific visual element for displaying group affiliations.
An interesting exploration of topic viewing behaviors by Saif, gathering community feedback on how users interact with topic lists and what influences their clicking decisions.
