All Activity

We have added several new features to Discourse based on popular theme components to make it easier to customize the design of your community. In this topic, we’ll share more about these new core features, how to use them, and provide information about they compare to the theme components that inspired them. Header search The header search feature moves search from the magnifying glass in the top right corner to a more prominent input field in the site header. When more header space is needed (such as when scrolling a topic), the search will revert to the magnifying glass to save room. To turn on header search… In the admin area, go to your site settings. Find the Search experience setting. Update this setting to “Search field in site header”. Click the green check to save. Header search feature vs. Advanced Header Search component Header search was inspired by the Header Search theme component, which we’ve renamed to Advanced Header Search to distinguish it from the core feature. You should use the Advanced Header Search component when you need to support external searches (i.e. searches outside of your Discourse community). Otherwise, you can use the header search feature that’s now part of Discourse core. Welcome banner The welcome banner greets members and visitors and adds a prominent search bar to your topic lists. The welcome banner and header search features are compatible with each other so that header search will be hidden while the welcome banner is visible. To turn on welcome banner… In the admin area, go to your site settings. Find the Enable welcome banner setting. Enable this setting. Click the green check to save. To customize the message displayed on the banner, go to the Site Texts area, and search for “welcome_banner”. You can modify text strings for registered member greeting, anonymous user greeting, and search field. Welcome banner vs. Advanced Search Banner component Welcome banner was inspired by the Search Banner component, which we’ve renamed to Advanced Search Banner to distinguish it from the core feature. You should use the Advanced Search Banner component when you want to use custom background images for the banner, enter multiple lines of text in the banner, or change who can see the banner (i.e. logged in members, logged out users, or both). Otherwise, you can use the welcome banner feature that’s now part of Discourse core. Category icons and emoji You can now use icons and emoji to distinguish categories, instead of the colored square. To use category icons / emoji… When creating or editing a category, change the Style setting to Icon or Emoji. Choose the icon or emoji you want to use. The color will determine the icon color (if using) and impact other areas where a color is associated with the category, such as on the /categories page. Click Save Category. Category icons and emoji vs. Category Icons component Category icons and emoji were inspired by the Category Icons component, which we will soon be deprecating in favor of this core feature because it supports more customization (i.e. emojis) and offers a much simpler setup experience. For those currently using Category Icons, we recommend moving your icon customizations from Category Icons to the core category settings for longterm support and ongoing feature improvements. In our testing, the component settings override the core feature settings, but these were not designed to be used together. 1 post - 1 participant Read full topic

Quick PSA: github.com/discourse/discourse FEATURE: when rich editor is enabled markdown is in monospace main ← monospace opened 03:34AM - 01 Apr 25 UTC SamSaffron +11 -1 - adds .d-editor-container--rich-editor-enabled to d-editor-container - conditio…nally swaps textarea to monospace when siteSettings.rich_editor is enabled For those of you testing the new composer (either here on meta or your own site) we just swapped the markdown (aka. source code) font to a monospace font. This helps clarify to users that you are in “markdown” mode vs “rich” mode. The change aligns the font choice to what is generally accepted in the industry (reddit / stack exchange) The change only takes effect on sites with rich editor enabled, and should be live here in 20-40 minutes. 11 posts - 6 participants Read full topic

Discourse 3.0.2 Stable Release Discourse strongly recommends that all sites follow the default tests-passed branch of Discourse. The “stable” branch is more focused on lack of change than lack of bugs - all releases, including those on tests-passed and beta are production ready. Security Updates This release includes fixes for these security issues reported by our community and HackerOne. https://github.com/discourse/discourse/security/advisories/GHSA-4p63-qw6g-4mv2 2 posts - 2 participants Read full topic

New features in 3.5.0.beta2 Review queue We have begun making a series of improvements to the review queue, where moderators can review and handle flagged content. A popup is displayed after completing a review action, as a success indication and to prevent accidental multi-clicks. If a post is flagged due to matching watched words, the responsible words are listed now so it’s easier to immediately know the reason for the flag. Welcome banner We have added a new welcome banner feature, to welcome members and allow them to search site content. To turn it on, select the Enable welcome banner site setting. Admin interface We continue to make improvements to the admin interface at a rapid pace. Three improvements to highlight: Uploading and managing your site’s logos has become easier with the newly redesigned and reorganized branding page. The logos we think every site should have are highlighted, while optional logos have been tucked away. When editing your theme’s color palettes (formerly known as color schemes) you can now specify color hex codes in addition to the usual color picker. If you like to get into your theme’s code to edit HTML and CSS, you will enjoy the newly improved theme editing interface. We hid seldom used fields behind a toggle, added better descriptions, and always display descriptions at the top rather than behind tooltips. Security Updates This release includes fixes for these security issues reported by our community and HackerOne. https://github.com/discourse/discourse/security/advisories/GHSA-hfcx-qjw6-573r https://github.com/discourse/discourse/security/advisories/GHSA-4p63-qw6g-4mv2 2 posts - 2 participants Read full topic

Invision Community 5.0.5 Beta 1 Released Mr Milchick approved We're back with a brand new release! This release fixes a few of the bigger issues reported over the past couple of releases. ElasticsearchFor those using Elasticsearch, please note that the new minimum version for Elasticsearch is now 8.0, with the latest version 8.17 recommended. Those using Elastic search in v5.0.4 and earlier (including all of v4) will need to upgrade their Elasticsearch server, and then rebuild the search index. We chose to update to the latest version of Elasticsearch as v7 is no longer supported and there's been some document level changes in how data is stored. We've tested it thoroughly but let us know if you find anything odd! Using BetasIf you do not see an upgrade, it means that you do not have betas enabled. Invision Community CloudCloud customers can opt-in to betas in the client area. Invision Community ClassicSelf-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! Coming up soonishThere's some discussion around sluggish javascript in some areas. This looks to be specific to Chrome and occasionally Safari, which honestly has taken a nose dive in quality recently. We think we know why, but it's taking some time to figure it all out. Essentially, we think it's some parts of our older javascript framework struggling with the new CSS framework. We'll get it figured out, but I wanted you to know that we're on it.

From 1st May 2025, Discourse’s minimum supported iOS version will be updated from 15.7 to 16.7. After that, visitors using older versions of iOS will be shown a basic-html version of community content, and won’t be able to login or interact with the site. Devices limited to iOS 15 are the iPhone 6s, iPhone SE (gen 1), iPhone 7, and iPad Mini 4. These were all released more than 9 years ago, and are no longer updated by Apple (see iosref.com). Unfortunately, it will not be possible to use Discourse on those devices going forwards. For more recent devices, iOS should be updated to iOS 16.7 or higher. From today, we’ll be rolling out a warning banner for affected users, with a link to this topic. On the technical side, dropping support for older iOS versions will allow us to start using modern web technologies including relative color syntax, subgrid, and lookbehind regex, all of which will enable improved experiences for Discourse users. 1 post - 1 participant Read full topic

I use forum signatures for building backlinks. I also use forum marketplace and advertising section

The most important thing is to publish unique and original content. If you have a lot of original content, you will easily ranked higher

I use it on my blogs and forums. In the past earnings were great but these days it is no so great

I have used Private Blog Network, and it really worked. However, my blogs on the private Blog Network were also had a lot of quality content.

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 testThere 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 BetasIf you do not see an upgrade, it means that you do not have betas enabled. Invision Community CloudCloud customers can opt-in to betas in the client area. Invision Community ClassicSelf-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

At Discourse, we are committed to fostering safe and healthy online communities. To support this, we’re introducing an important update that allows forum administrators to access and manage group chats within their communities. This update ensures that community leaders can effectively manage group chat memberships, enforce guidelines, and respond to safety concerns when needed. It also helps communities align with evolving online safety legislation, providing admins with the necessary tools to maintain a secure and welcoming space for all members. We believe this change will empower admins to uphold community standards while continuing to provide a space for meaningful and productive discussions. As always, we remain dedicated to building features that balance user experience, moderation needs, and community well-being. This feature will be available for all Discourse sites in the coming days, and was added in these two pull requests: github.com/discourse/discourse FEATURE: Allow admins to remove users from chat DMs main ← feature/admin-remove-users-from-chat-dms opened 10:13AM - 17 Feb 25 UTC Drenmi +375 -17 ### What is this feature? This feature allows admins to remove users from cha…nnels. This is allowed for category channels and group DMs, but not one-on-one DMs, as that wouldn't make any sense. 😉 **Screenshot:** <img width="263" alt="Screenshot 2025-02-19 at 10 59 49 AM" src="https://github.com/user-attachments/assets/049aa77d-67ae-42f8-a190-f640e4285118" /> ### Implementation details This PR attempts to follow the existing structure as much as possible. The major moving parts are: - A new back-end service for removing users from channels. - A guardian extension checking the ability to do so. This is also propagated to the front-end. - A new method in the front-end chat API. - UI changes. - Tests. ### Known limitations - When removing a member from a group DM, the header doesn't update to reflect this. This is a pre-existing issue. (It also doesn't update when adding members.) I have created a task to fix this separately. - The terms `users` and `members` are mixed throughout the code base. I tried as best I could to follow the terminology of the _directly adjacent code_. We could potentially fix this up later. github.com/discourse/discourse FEATURE: Allow admins to access group chats main ← feature/admins-access-group-chats opened 05:45AM - 21 Feb 25 UTC Drenmi +36 -1 ### What is this change? In #31366, we added the ability for admins to remove… people from group chats. However, that only works as long as the admin is already in the group chat. For forum-side group messages, admins can join any of them at will. This PR extends that same ability to chat for parity. 1 post - 1 participant Read full topic

Invision Community 5.0.3 is now available via your Admin Control PanelThis release focuses on bugs reported since the release of 5.0.2 and features many UI improvements. You can see the full list of fixes in our release notes section. What's next?We expect 5.0.4 to follow within two to three weeks as we work in some larger fixes that will require more testing. We may release a beta release ahead of the full release to ensure that any bugs from those larger fixes are caught and fixed early. If we see anything more pressing, we'll release a patch which can be applied via your Admin Control Panel. As always, thank you for your testing and reports. It really does help us!

Discourse 3.4.1 Stable Release Discourse strongly recommends that all sites follow the default tests-passed branch of Discourse. The “stable” branch is more focused on lack of change than lack of bugs - all releases, including those on tests-passed and beta are production ready. Bug Fixes Improve group name validation (31315) Wikipedia onebox images and sections (31384) Language parser matches with dashes or underscores (31381) Ensure revoke_ungranted_titles! works with user_ids (31371) Adds further support for ‘prioritize_full_name_in_ux’ setting (31346) Make permalink search work even when there’re 100+ permalinks (31354) Don’t show &nbsp; in date to button (31352) Missing link to deleted post in /my/deleted-posts (31342) Image uploads in site-settings and profile (31350) Prevents double set in the same computation (31348) Relative date format consistency (31349) Post revision respects ‘prioritize_full_name_in_ux’ setting (31293) Minimum username length should be validated (31332) Keep user in same context after login (31314) Ensures fields are correctly unregistered (31329) Calculate reaction_users_count in the bulk import script (30964) Automatically redirect logged in users to topic when… (31301) Do not show confirmation modal (31304) Limit displayed groups in <GroupChooser /> to 100 groups (31288) User profile not loading with an empty export (31290) Correctly display label (31282) Don’t load all groups when rendering <GroupChooser /> (31271) JS error when .header-cloak isn’t present (31281) Invalid CSP directive sources should allow site to boot with valid CSP directives (31256) Improvements for uploads:disable_secure_uploads task (31231) Incorrect topic per-minute invitation rate limit (31252) Automatic auth flow with full page login/signup V3 (31072) Do not notify admins about PMs when suppress is on (31232) Correct typo in property name for save button component (31221) Set the correct state of the dark mode checkbox user preference (31214) Adjust badge selector for proper nesting in plugin list (31218) Only include custom plugin config routes in tabs for old show page (31213) Clean up not secure uploads with access_control_post_id (31189) Correctly check for hasData in admin-report (31197) Propagate pointerdown events on DMenu trigger when the menu isn’t expanded (31104) Correct mobile height of badge and ownership modals (31187) UX Changes Increase limit in chat channel fetcher (31406) Remove old menu border hack (31344) Prevent long category names from overflowing on mobile topic list (31335) Hide powered-by on admin invite page (31303) Add enter key hints for search (31298) Remove main-outlet-wrapper margin reset for mobile (31286) Add confirmation to crawler settings (31269) Update banner image field to use help text (30666) Fix horizontal group nav on mobile (31259) Switch group pages to horizontal nav (31243) Use icon for create topic btn on mobile (31237) Omit date in user stream for small action posts (31236) User stream alignment fix for likes (31234) Do not use generic username suggestions for invites (31175) Conditionally refresh page on wizard styling step (31193) Remove enable_quote_copy site setting (31191) Fix HTML showing in delete user button (31201) Fix layout of invite modal errors (31199) Left-align dropdown menu button text (31198) Fix wrapping of topic map links with counter (31184) Update bot-indicator styling (31108) Multiple drafts menu improvements (31195) Show parent category name for category hashtags (31188) Ensure all children of .with-topic-progress are clickable (31176) Performance Defer consolePrefix() calculation for transformers (31367) Admin plugin preload settings routes (31215) Accessibility Fix post control button contrast issue for WCAG colors (31177) 2 posts - 2 participants Read full topic

New features in 3.5.0.beta1 Easy switching between light and dark mode If you’re using a theme that has both dark and light modes, you now have the option of displaying a selector to your users for them to choose which mode they prefer. The selector can appear in the footer or the header, and allows users to select dark, light or auto, which will select the appropriate mode based on their system settings. This core feature replaces the now-deprecated theme component that provided this selector. Read the announcement here. More useful information when flagging content To help site admins remain compliant with evolving legislation, the flag modal now includes text providing a brief explanation of what happens when content is flagged and how it is reviewed. This text can be customised to include any necessary information, like the expected timeframe for reviews. Learn more about this in our documentation. By default, this text reads: All flags are received by moderators and will be reviewed as soon as possible. Check out the feature documentation for how to edit that and add your own details to it. Encouraging better conversations In order to foster more interesting and valuable conversations, we now have a setting for not counting uploads when calculating the minimum length of a post. With the new prevent uploads only posts setting enabled, posts that contain only images or other uploads, will be blocked from publishing, encouraging users to offer more substantial and valuable input when engaging in conversations. 2 posts - 2 participants Read full topic

Getting trsffic is sometimes easy. Converting that traffic to users is the hard part.

It is worth the time. It does take a lot to build a solid rep.

Organic growth on social media means you build a huge fan following and get tons of engagements without having to spend money on ads. Organic growth on social media requires patience. Unless you already have built a strong personal brand or have celebrity status, the most effective way to expand your reach is through paid advertising. While social media offers free exposure, turning that exposure into conversions demands consistent effort, strategic planning, and financial investment.

Well, there are multiple methods to get traffic to your site, however, getting people to actually visit your site is very difficult. Well, you might have done SEO, marketed on social media or sent newsletters and think that you will get traffic. But despite your hard work traffic is not guaranteed. Your SEO effort will get you traffic only when your website ranks high on Search Engine Result Page for high traffic keywords. You might run ads for traffic but there is a price to pay.

We're pleased to announce that CSAM scanning is now available at no extra cost. What is CSAM scanning?CSAM stands for Child Sexual Abuse Material. The media served by your community will be scanned to identify any matches in a central CSAM database. These lists are provided by leading child safety advocacy groups, such as the National Center for Missing and Exploited Children (NCMEC). CSAM scanning is now recommended to increase compliance in many areas, and you can rest assured that Invision Community will now block any harmful media from being shown in your community. Moderating large communities can be challenging when your members are able to upload photos, and this scanning tool offers great peace of mind. What about privacy?Rest assured that privacy is paramount to Invision Community. CSAM scanning is not an AI tool, and neither does it mean media on your site is being shared with third parties for review. Each photo or video is assigned a digital fingerprint, which is checked against a known database. If there is a match, the photo is blocked from being viewed. What happens if there is a match?If we detect a match for CSAM, the media is blocked from being shown. We will then remove the offending media and, where possible, block the person who uploaded the material. This tool is designed to help you, as an Invision Community owner, moderate your community and protect you from unwittingly sharing CSAM. We hope you never have a member upload such material, but it's reassuring to know that your site will not be complicit in its sharing. By identifying and blocking bad actors' access across our network, we can pre-emptively protect you, too. Can I opt out?No, there is no way to opt out. This scanning service offers great peace of mind, protects you from harmful material being shared, helps compliance and prevents bad actors from accessing other communities. Note: this service is not available for Invision Community Classic.

Invision Community 5.0.2 is now available via your Admin Control PanelThis release focuses on bugs reported since the release of 5.0.1 and features many UI improvements. You can see the full list of fixes in our release notes section. This release also resolves several issues with Downloads screenshots and thumbnails. What's next?This week we'll continue to triage and manage incoming bug reports and we expect to have another maintenance release out next week to ensure that bug fixes are resolved as quickly as possible. We then expect 5.0.4 to follow within two to three weeks as we work in some larger fixes that will require more testing. If we see anything more pressing, we'll release a patch which can be applied via your Admin Control Panel. As always, thank you for your testing and reports. It really does help us!