Topics

Invision Community 5.0.4 Beta 1 is now available Please celebrate responsibly. A whole two weeks has passed since our last release. The extra week allowed us to fully review a few larger updates that we've held back and require a beta or two to fully test before we're happy to include in a full release. Things to test There have been some areas that have received a lot of attention and need extra special testing, these include: Page Editor (now works correctly for right-to-left languages but needs some testing in LTR) Custom badges (lots of work to make them more efficient and store a built version in SVG format) Editor bug fixes (lots of complex fixes, so please test the editor thoroughly) If you want a full list of changes, you can see that here. The release notes also have some changes which may impact third party developers. Using Betas If you do not see an upgrade, it means that you do not have betas enabled. Invision Community Cloud Cloud customers can opt-in to betas in the client area. Invision Community Classic Self-hosting customers can either download the release from the client area, or add the following line to constants.php define( 'USE_DEVELOPMENT_BUILDS', TRUE );If you do not have this file, create it in a text editor, so the contents looks like: <?php define( 'USE_DEVELOPMENT_BUILDS', TRUE );Let me know how you get on!

We have been working on a new rich text editor mode for our composer so that it’s easier to write on Discourse. We’re now ready to start testing this mode out on Meta to get more feedback from our community on this feature! This topic will serve as both a guide to testing the new composer and a hub for tracking feedback. Thanks in advance for all your help! Getting to know the new composer The new composer is a rich text editor that simplifies the writing experience, particularly for non-technical users who are not comfortable with Markdown. This editor still supports Markdown, but formatting is rendered immediately for a WYSIWYG (“what you see is what you get”) experience that feels similar to other modern web composition tools (like Notion or Google Docs). To access the new composer, click the toggle in the toolbar. This will let you switch from the current Markdown-only mode to the new rich text editor. You can click the toggle again to switch back, if needed. What you’re testing today is the first version of the new composer. It is not yet intended to be a complete replacement for the current Markdown-only composer. We have focused on the basics first, which should cover most users’ needs. Please review the sections below to understand what is currently possible and what’s not yet ready in the new composer. We will update these areas over time as support expands! Supported features The following features are supported in the new composer: Ability to add title and set categories and tags Single-pane editor when in rich text editor mode (i.e. no preview pane) Toggle to switch between Markdown-only and rich text editor modes Basic formatting [1] supported in Markdown, keyboard shortcuts, and toolbar icons Emoji support Auto-converting Markdown to rich text when pasting plain text (e.g., **bold** → bold) Auto-convert emoticons (e.g., :) → ) Table builder UI Poll builder UI Support for mentions and hashtags Inline HTML <tags> [2] Typographer replacements (e.g., , → , ± ) Image uploads File attachments Topic quotes Hide Details Blur Spoiler (with limitations, see Missing Features section) Oneboxes Missing features The following features that we know are currently missing or not yet fully supported in the new composer: Link UI to visit, edit, copy, or remove added links and change their titles Image UI to resize, caption, or grid added images Table UI to add or remove columns and rows after creating the table Poll UI to edit previously created polls Footnotes Horizontal rule autoconversion (i.e. --- converting to the rule; you can add a horizontal rule now with CMD + Shift + -) Chat quotes Tight list support (all lists are currently “loose”, meaning there’s extra padding between list items) Improved Blur Spoiler support to add blur to existing text, support inline blur, and make it easier to remove blur. Anything else not explicitly noted in the supported features section Testing and sharing your feedback As you test, you may run into issues where the composer does not behave as you expect. When that happens, please let us know! Your feedback is an invaluable asset to help us improve the new composer so that it’s ready to make available in your community. Please provide specific reproduction steps, information about your browser / device, and any relevant screenshots or recordings! You can also review our known issue tracker below to see if someone has already reported what you’re seeing. We will keep these sections up to date as we identify and fix issues. Remember, you can always switch back to Markdown-only mode using the toggle if you’re running into an issue using the new composer. Bugs Autocomplete and inputrules are converting mentions, hashtags, and emoji within inline code On mobile Safari, problem with container positioning when keyboard is open and you tap out of and then back into the editor On Firefox, can’t position cursor ahead of mention when it starts the post When an emoji isn’t found in the emoji autofill (:), clicking more doesn’t work. it should open the full emoji picker, but it doesn’t. (desktop, chromium) On Safari, the content after a bullet / number drops to a new row for the first few characters while typing UX issues When focused in the composer, CMD+K should open Link UI instead of chat search Increase the size of standalone emojis (i.e. emoji not surrounded by text) Prevent underline on links Apply expected visual rendering to valid category / tag hashtags Improved handling of composer tips (or removal from rich text editor mode) to avoid overlapping with the composer pane Mentions and hashtags don’t validate content Toolbar tweaks for accessibility, indicating which formatting button is in an active state Cursor is focused inside the quote (instead of the line below) when beginning a post with a quote or when copying / pasting quotes Composer isn’t auto-focused if the first time it’s opened is for a Reply If you leave and return to content in inline code formatting, you can’t escape the formatting (i.e. the new content you type will also be in inline code) Caret (i.e. cursor) positioning after creating a full or inline onebox needs adjustment to improve writing flow Dev improvements Improve inline HTML parsing Bold, italic, underline (no toolbar support), strikethrough (Markdown-only via ~~ ), links, blockquotes, code, checkbox (Markdown-only via []; toolbar support coming soon), bullet lists, number lists ↩︎ Some convert to closest Markdown (e.g., s, strike, strong, b, em, i, code; u is specifically unsupported because it does not cook to an actual underline); others will be allowed as “html_inline” nodes (e.g., kbd, sup, sub, small, big, del, ins, mark) ↩︎ 8 posts - 5 participants Read full topic

Starting today, we will be removing the Discourse Akismet plugin and will instead enable Discourse AI - Spam detection by default for hosted customers on Starter and Standard plans. Why are we making this change? Over the past few weeks, we’ve found our AI spam detector to deliver a superior performance over Akismet. We’ve had over 126 sites extensively using it and within Meta, we’ve personally seen over 96% success rate in detecting spam. On top of the performance, the setup would now be a default experience with customization and flexible options, should you need it. What do I need to do? If you are on our Starter or Standard hosting, nothing at all! The change would happen automatically in the background. You will no longer see Akismet within the plugins. You will now see the AI spam detector turned on in the AI plugin setting using a Discourse-hosted open-weights LLM If you have the AI plugin disabled, then you would manually need to turn on AI spam detector and select an LLM I already have AI spam detection enabled! If you already have AI spam detector enabled via What's New experiments, then you can safely ignore this announcement since you already have it! Why is this change only for Starter and Standard? As usual, the rollout of changes in our hosting begin with the starting tiers and are gradually expanded to cover all tiers. 1 post - 1 participant Read full topic

Introducing Advanced Sentiment Analysis: Powerful New Insights for Your Discourse Community We’re excited to announce a significant enhancement to Discourse AI with our new Sentiment Analysis Report feature. Building on last year’s Sentiment overview, this powerful tool gives administrators deeper insights into community sentiment across your forum. Where to Find It Navigate to your admin dashboard and look under the Reports section in the sidebar. You’ll find the new Sentiment analysis option alongside the existing Sentiment overview report. Flexible Analysis Options This comprehensive report empowers you to: Filter by specific parent categories Group results by categories or tags Customize time periods for targeted analysis Easily export data for further processing Actionable Community Insights The true power of this feature lies in its ability to help you identify trends and potential issues before they escalate. With a single click, you can drill down into any category to examine specific posts that are driving sentiment in your community. Availability and Implementation This feature is now available to all customers on our official hosting at no additional cost. Self-hosted Discourse instances can enable this functionality by following our existing setup guides for Discourse AI. Get Started Today We encourage all community managers to explore this powerful new tool and discover valuable insights about your forum’s emotional landscape. Share your experiences with us as you put sentiment analysis to work! 1 post - 1 participant Read full topic

For licensing reasons, we had to change the emoji sets. The following existing sets have been migrated automatically to a new set: apple → twemoji facebook_messenger → unicode google → noto google_classic → noto win10 → fluentui emoji_one → twemoji twitter → twemoji On top of fluent ui, noto, twemoji, and unicode, we also added the openmoji set. Admins can change the set at /admin/site_settings/category/all_results?filter=Emoji%20set If there’s an existing open-source set you would like to see available in Discourse, please let us know. We understand that changing emojis can be a very visible change, but we didn’t have any other way around it. We prefer to lay a good foundation for the future by only supporting fully open-source sets. 3 posts - 2 participants Read full topic