vBShout v6.2.0 Released!

Fillip H.

Staff member
Owner
Developer
Customer
Hey all,

We're pleased to be able to release vBShout v6.2.0, available immediately to Lite and Pro customers. This release adds half a dozen new features, 100% of which were requested by you, our customers.

The main feature in this version is a rework of something that's bugged a lot of people (including me!) for quite some time: Automated notices like posts and forum PMs would previously flag someone as active in the Shoutbox - if you couldn't see the notification, you'd just randomly see someone suddenly marked as active.
This has been corrected in v6.2.0, and the Shoutbox will now only flag someone as active if they've taken some form of action such as un-idling themselves, changed tabs etc. Additionally, we've added an online indicator to let you know whether you're currently showing as active to other users.
A side-effect of this change is that forums with a very large shout history should now experience a slight boost in performance, as the "session" table for the Shoutbox is routinely pruned of expired sessions in order to keep the query for fetching active users running speedy.

The main Pro-only feature in this version is the addition of Global Custom Commands. What was previously a per-user only feature is now also available for Administrators. You can put your own unique twist on the old /slap command by having it slap people with a keyboard if you're running a computer forum, or something else more appropriate to your forum's main topic.
This feature will also prevent users from creating custom commands that match your globally defined custom commands, so you won't have to worry about any overlap.

We've also added some smaller features; You're now able to anonymise links via Anonym.to on a per-instance basis, the Shoutbox will now optionally respect vBulletin's "Prevent SHOUTING" setting, there's a new slash command /resetshouts that will reset all users' "Lifetime Shouts" counter to their current shout count (/resetshouts Fillip H. to reset it for a specific user only is available in the Pro version), the ability for each user to turn the shoutbox off entirely (Pro-only) and finally, you're now able to initiate editing/deleting a shout via context menu items - great for mobile management of shouts where double-tap invokes a zoom feature.


If you like the product, you can show your support by nominating it for Mod of the Month here: vBShout (vB4) or here: vBShout (vB3), and also please rate it to help cancel out the users who 1 star our mods. Thanks :)


vBShout v6.2.0

Shoutbox Sessions
  • Shoutbox activity is tracked separate from users' shouts
  • Only shows people who perform an action as active
  • "Active Indicator" on the toolbar shows whether the user is active in the SB or not
  • Doesn't flag users generating automatic notices as active

Anonym.To Integration
  • Ability to anonymise any URL entered in the Shoutbox per-instance with Anonym.to
  • Works with BBCode URLs
  • Displays regular URL while editing shouts

Disallow "ALL CAPS"
  • Ability to disallow all caps per-instance
  • Uses vBulletin's "Prevent SHOUTING" setting to de-caps the shout

New Slash Command: /resetshouts
  • Resets all users' "Lifetime Shouts" counter to how many shouts they currently have in the system
  • (Pro) /resetshouts user to reset an individual user's "Lifetime Shouts" counter
  • Great way to put spammers in their place

Context Menu Improvements
  • Dedicated context menu item for editing shouts (if user has permission to edit that shout)
  • Dedicated context menu item for deleting shouts (if user has permission to delete that shout)
  • JavaScript performance for menu closure operations has been improved

(Pro) Global Custom Commands
  • Create custom commands that anyone can use via the AdminCP
  • Prevents users from creating commands with the same shortcut
  • Great for "canned responses"

(Pro) Per-User Shoutbox Toggle
  • New UserCP option to turn off the entire shoutbox
  • Hides it completely from all pages

Bugfixes
  • In certain cases, the menu could fail to close properly


Thank you for your continued support :)

Discuss this news here.
 
Top