New features in 2.6.0.beta5
Suspend or silence users when flagging
When flagging posts, staff can now suspend or silence a user immediately, without needing to visit the review queue or use admin page. This allows for a more streamlined active moderation workflow, when moderating against a topic directly.
WCAG-compliant color palettes
Discourse now ships with two additional color palettes - WCAG Light and WCAG Dark. These color palettes follow the Web Content Accessibility Guidelines for minimum contrast. Admins can create color palettes from these base palettes and set them as user selectable, giving users control over the colors they want. Read more about them in WCAG high-contrast color palettes for low vision.
Topic slow mode
We added a new slow mode for topics that are heating up. Staff can enable slow mode from the topic admin wrench. When enabled, users will have to wait for a staff configured period of time before being able to post again.
Ctrl+Shift+Enter or Shift+Click do not scroll when posting
By default, Discourse will automatically scroll down in a topic when you post, so you can see your post. In some circumstances, users may not wish to scroll, and instead keep their place in the topic. To skip the scrolling, users can hold the Shift key while clicking the Reply button, or use the keyboard shortcut Ctrl+Shift+Enter.
Detect dates in posts when creating bookmarks
Discourse now attempts to detect dates within posts when a user creates a bookmark. If a date is detected, that date is shown as an option in the bookmark modal.
Category group moderator improvements
Category group moderators can now edit all posts with the category, even if they do not have TL4.
Disable default bingbot throttling
Previously we blacklisted, then allowed but throttled, bingbot due to crawling sites at a significantly higher rate than other crawlers. More details in Bingbot is default throttled. 2 years later after testing we’ve found that bingbot is crawling at a normal rate again, and thus have removed the default throttling.
Ask user to confirm topic deletion when topic views are high
Thanks to community member @RickyC0626, staff are now warned before they delete a topic with a large number of views. The view count defaults to 5,000, and is configurable by admins via the min topic view amount for delete confirmation site setting.
Process bulk actions in batches
Previously if staff attempted to bulk update a large number of topics, the process could time out. We now process bulk actions in smaller batches to avoid such errors.
now