Legacy Need full default settings for shoutbox

[Trekkan]

I put this as a bug, because as it works right now, it won't work.

Basically the problem is that when someone adds their new Twitch channel, the shoutbox created for them has all of the "default" defaults. So basically there's the issue with how things look being wrong, but even more importantly, the usergroup permissions.

As it stands, the default shoutbox perms, won't allow for my members to actually use the shoutbox. I don't use "Registered Users" usergroup. This is why I put this as a bug. The shoutbox simply isn't available to my users on their Twitch streams.

Overall, this is really sweet, but this is something that I think is pretty necessary.

 

[Fillip H.]

This is definitely not a bug, because specific interfaces need to be created in order to account for non-standard usergroup setups.

The best way of going about creating additional ACLs, I've found, is to make every other group secondary usergroups and use the Registered Users as the "base". For instance, Pre-Sale Users and Customers here @ DBTech. Everyone is a member of Pre-Sales, but they are added to Customers once they buy something.
Simple access to Pro support forums for individual products is achieved by Access Masks.

Pre-Sale Users have all the standard permissions, such as access to all Lite forums, and Customers have additional overrides such as bold username.


I think this would be best achieved by creating a "default permissions" feature in vBShout (most likely, flagging a specific instance's configuration as default) and then updating Twitch to utilise this functionality if it's available.

 

[Trekkan]

However a default works, then that's good really. Not too worried about the solution as long as it works. Althought I wouldn't consider not using the "Registered Users" non-standard since it's not a mandatory configuration.

 

[Fillip H.]

In the next release, there'll be a new vBOption to control what instance's settings/permissions is used for newly created instances