darkpixlz initiated a discussion on improving desktop view for mobile devices, suggesting that the current desktop view on mobile feels lacking. MarcP questioned the feasibility of optimizing desktop versions for mobile screens, while Heliosurge shared insights on using mobile interfaces and potential improvements.
Andro sought help with receiving bounce notifications for their local Postfix server. After some troubleshooting, they successfully resolved the issue by changing the VERP regex user name.
Campa inquired about adding a banner to the top of their site. Moin provided helpful links to documentation on creating banners and mentioned that the specific custom theme component used by the Discourse team is not public.
nolo contributed to the Breadcrumb Links theme component discussion, suggesting improvements to the code and considering moving the conversation to the original development topic.
Users continued to express appreciation for the Discourse AI Helper, with MarcP sharing his experience using AI for theme components and suggesting tools like Cursor for enhanced development workflows.
Users discussed bringing back the AI helper for non-TL3 members. sam bumped it to trust level 1, noting that self-hosted LLaMA makes costs less of a concern. This sparked a conversation about TL3 requirements being too difficult to reach/maintain. sam acknowledged that the reading requirements for TL3 are quite high, with meta currently requiring 6302 posts and 500 topics read. read more
Users discussed object storage options, with LJT recommending Internxt Object Storage as a cost-effective S3-compatible solution at €7/TB/month. read more
mcwumbly introduced the first edition of “Current Projects,” a new monthly newsletter sharing ongoing work at Discourse. The post covers various projects including a composer redesign, new theme chooser in the setup wizard, and other features in development. Read more
#Site feedback
hugh called for community contributions to improve Discourse documentation, listing several areas that need new or improved content. This initiative aims to enhance the documentation for administrators, moderators, users, and sysadmins. Read more
gormus updated the Notification Banners theme component to support targeting specific categories, allowing single or multiple category selection per banner. Read more
A bug was reported where opening a keyboard on modal inputs causes the page to jump to the top on mobile devices. The Discourse team has been asked to address this issue. Read more
An issue with user fields during signup was reported and subsequently fixed. A PR was opened to backport the fix to the stable branch. Read more
A suggestion was made to add a new Category Permission called “Display,” allowing admins to show categories without revealing topics to visitors. Read more
A feature request was made to link the Sign Up process to the Subscriptions Plugin, allowing forums to display a Subscription page with membership fees after sign-up. Read more
A user reported an increase in spam on their forum and sought guidance on best practices for filtering and reducing spam. Read more
An issue was reported regarding AI not responding when mentioned in a reply to a post. It was clarified that the AI bot doesn’t answer if mentioned in a reply to a post, but does respond when mentioned in a reply to a topic. Read more
A user inquired about the possibility of displaying user birthdays as events in the Discourse Calendar plugin, potentially enabling cool automations for engagement. Read more
MachineScholar asked about the storage of embeddings for AI Personas, inquiring if they are stored in the same vector database as other Discourse embeddings. sam confirmed that all embeddings are stored in Postgres using the same database. Read more
mcwumbly introduced the “Current Projects” newsletter, providing insights into ongoing Discourse developments. They also merged a topic about adding timers to banner topics. Read moreRead more
hugh called for community contributions to improve Discourse documentation and responded to various queries about the initiative. Read more
sam implemented basic support for o1-preview & o1-mini LLMs in the discourse-ai plugin and provided information about embeddings storage. Read moreRead more
lindsey announced plans to implement threading in DMs and group chats, addressed a design oversight in official warnings, and asked the team to fix a mobile UI issue. Read moreRead moreRead more
pmusaraj was mentioned in discussions about the Discourse Hub app and its compatibility issues. Read more
Joe_F asked for advice on finding the perfect theme for their Discourse forum, receiving suggestions for various theme components and sidebar solutions.
A user inquired about changing the link under the logo on their Discourse site, with Moin and Lilly providing guidance on customizing the logo link and homepage settings.
A discussion arose about implementing user-created groups in Discourse, with explanations provided on why this feature is not currently available and potential alternatives.
matenauta suggested having related topics as the default view instead of suggested topics, with sam acknowledging the potential for an extensibility point to make this customization easier.
The Discourse team provided an update on current projects for September 2024, including information on the composer overhaul and other ongoing developments.
An error was reported when testing email configuration: “no implicit conversion of Integer into String”. The user provided system information and SMTP logs for troubleshooting.
patrickemin encountered issues with the Approve unless allowed groups setting, leading to a discussion about the complexity of Discourse’s overlapping layers of permissions and settings. simon suggested that the setting’s description could be clearer about how trust level groups work read more.
Arkshine introduced a new theme component called Banner Featured Links, which allows users to create a banner of links inspired by the Meta Branded theme. The component received positive feedback and a small fix was pushed to address an initial issue.
A user reported that category icons were not displaying on mobile in the autocomplete search results after updating to Discourse 3.3.1. Arkshine provided a quick CSS fix while suggesting it might be related to existing component CSS.
SupportGeek sought help with compiling JavaScript for a custom component to add a new topic button in the topic list. After some trial and error, they managed to get working code using LLaMA AI. merefield advised against using widgets and recommended Glimmer Components instead.
mbiistscther reported an issue with the Activate Account page showing a blank page after updating to Discourse 3.4.0. simon suggested it might be related to Cloudflare’s Speed Brain feature and recommended disabling it.
riderdivyanshu sought help installing the AI plugin on Discourse v3.4.0.beta1, sharing error logs. Other users suggested addressing email, domain, and database configuration issues first.
The Discourse team is upgrading icons to Font Awesome 6, which has caused some issues with missing icons for users. Aaron_B reported problems with several random icons missing, including the search icon in the top toolbar and icons on the left menu. Lilly suggested upgrading the Discourse instance and provided screenshots showing the correct implementation read more.
A user reported issues with CloudFlare integration causing mobile access to keep loading. The problem was traced to a configuration failure in CloudFlare, and the user sought guidance on adding the cloudflare.template.yml to app.yml read more.
A user asked about customizing editor buttons, specifically to remove the calendar symbol that conflicts with a custom Event Plugin. Moin suggested either disabling the feature entirely or using CSS to hide the button read more.
Users continued to discuss the Discourse Chatbot plugin, with ozkn reporting an issue where the chatbot couldn’t see image content. merefield provided a fix and explained a timing issue related to image processing in Discourse read more.
ppcole encountered an issue with blocked words in URLs when adding an event. The problem was resolved by identifying a watched word that was unintentionally matching the URL. read more
BCHK faced a problem with their logo not updating after uploading a new file. The issue was traced back to a setting in the Big Header/Little Header theme component. read more
Aaron_B experienced some icons not showing up after upgrading their Discourse instance. The problem was resolved by running the ./discourse-setup command. read more
rahim123 reported an issue with iframe embedding being broken despite having the correct domain in the allowed iframes setting. Lilly and others helped troubleshoot, eventually discovering that the issue was caused by a missing trailing slash in the allowed domain URL read more.
_thiago discovered an issue with users being able to see deleted comments. merefield and Moin suggested configuring the delete removed posts after setting to address this concern.
A user encountered problems with their topics not appearing in the latest feed. Lilly suggested using plugins to suppress categories from the latest view, while RGJ identified a potential bug in how muted tags and categories are treated differently.
The_Alchemist reported an issue where the Torii-gate Font Awesome icon caused the post reaction button to disappear. Lilly provided a fix using a replacement script and emoji configuration.
Tealk reported an issue with Let’s Encrypt not working for ECC certs with multiple domains. pfaffman provided a solution by modifying the letsencrypt script.
Lilly provided support in multiple threads, including suggesting plugins for suppressing categories from the latest view, offering a fix for a Font Awesome icon issue, and confirming a bug with the Invite modal on iPadOS.
awesomerobot responded to a query about updating official Category Icons and Tag Icons theme components, assuring that they should automatically use the new Font Awesome 6 icons.
gerhard provided an update on the converter framework project, mentioning that documentation is still in progress and that it will take a few more months before it’s ready for actual migrations.
Thanks for reading, and I’ll see you again tomorrow!
A discussion on having more trust levels was initiated by Elena. merefield explained that there are actually at least 8 de facto trust levels, including anon, TL0-4, moderators, and admins read more.
An issue with category endpoints not working was reported. angus discovered that the Discourse instance was not returning categories as expected, affecting both the WP Discourse plugin and native Discourse features. Lilly confirmed the user was on a Basic plan, which should still have API access. RGJ suggested checking the lazy load categories groups setting, which Lilly found had been changed to “everyone” and recommended reverting.
In the Discourse Reactions topic, users expressed interest in replicating the emoji picker from Discourse Chat for post reactions. putty suggested adding an admin option to blacklist certain emojis to help curb toxicity and promote positive discussions.
A user inquired about whether the ‘Posted’ field in user cards includes posts from private categories. Lilly confirmed that it does, explaining how this affects the displayed post counts for team members who are active in private categories.
NateDhaliwal asked for clarification on how pageviews are calculated for hosted Discourse instances, noting a potential discrepancy in the documentation regarding web crawler traffic.
A user reported an issue with the Clickable Topic theme component where the body text on topic cards was not clickable in the latest Discourse beta version.
In the National Flags plugin discussion, Heliosurge clarified the difference between region and flag data, noting that regions provide more granular location information than national flags.
A user encountered issues during the “Resetting topic counters” step while migrating from XenForo to Discourse. pfaffman suggested retrying the script and checking the system’s partition setup.
Moin suggested improving the wording when undoing membership acceptance in groups, proposing “user removed” instead of “request undone” to better reflect the action taken. Read more
The ongoing discussion about community health metrics saw gentrificationzolaz commenting on the importance of transparent community health statistics. merefieldquestioned the necessity of such metrics for individual members, suggesting that meaningful interactions and recognition might be sufficient indicators of value.
A user reported Search Console errors related to schema markup, specifically the “comment” property. nwnuyhsshared a similar issue and provided the error message details.
A user inquired about the location and usage of the Topic List Latest-Post Excerpt plugin after installation, indicating potential difficulties in finding or activating the component.
The topic of mailing list mode for Groups resurfaced, with agitsuggesting the addition of an option to activate this feature for less tech-savvy users who prefer full discussions in their email clients.
A user encountered an “embed url is already taken” error in the Gutenberg editor when working with WordPress and Discourse integration. Petr_Mišák described the steps that led to this issue and asked for potential solutions.
The DiscourseHub app issue with connecting to accounts on iOS 18 has been addressed. pmusaraj submitted a fix to Apple for review, which should resolve the problem once approved. read more
A user encountered difficulties with post editing for users despite configuring settings to allow indefinite editing. The issue was resolved by adjusting user permissions. read more
A user reported issues with restoring backups containing Discourse onebox links, particularly with images from /uploads/default/original. A workaround was found by modifying the link format. read more
After migrating to Discourse, a user noticed unexpected username changes for many accounts and sought advice on reverting these changes. read more
EmilyJane suggested adding the ability for users to rotate uploaded images within Discourse, similar to existing size adjustment options. Moin recommended a theme component that enables image annotation. read more
Discussions continued on improving the AI-generated daily summaries. simon suggested reducing the use of active voice to enhance readability. sam mentioned potential improvements using GPT4-o. read more
A user encountered an error when rebuilding their Discourse instance, with the launcher failing due to a NULL-Byte being ignored. pfaffman suggested some troubleshooting steps to resolve the issue read more.
A user asked about resizing images offline to save server space. pfaffman recommended adjusting Discourse settings or using S3 storage instead read more.
A user reported issues with spell checking not working in Firefox on macOS read more.
A question was raised about manually sorting subcategories within a specific parent category read more.
A user requested the ability to indent subcategories in the sidebar, noting it’s important for color-blind users. A solution was provided using custom CSS read more.
A discussion continued about changing the “in reply to” field when editing posts. ToddZ shared a use case for administratively “re-parenting” replies read more.
A discussion continued about why Discourse isn’t more frequently recommended as a “community platform”. Users compared Discourse to other platforms like Discord read more.
Acknowledged a bug report about the documentation navigation closing unexpectedly and confirmed it would be included in upcoming development work read more.
pmusaraj discussed the possibility of creating a “Sign in with Ghost” plugin for Discourse:
Suggested that it might be possible to create such a plugin if Ghost supports oAuth read more.
joffreyjaffeux commented on an issue with copying and pasting from Word:
Suggested that the problem might be related to specific Word documents rather than a change in Discourse read more.
sam mentioned an upcoming feature in Discourse AI:
Informed users that the ability to force LLMs to call functions will be implemented in Discourse AI read more.
Thanks for reading, and I’ll see you again tomorrow!
