xF2 Add-on XF2 [8WR] Discord Integration 2.1.1.9

• BUG FIX: Fixed a double posting bug where the bot will post a thread twice when the first post in a moderated thread gets approved.
• BUG FIX: Fixed a bug where on some browsers, user role sync relations will not properly apply a default value for the sync direction on managed roles. You will have to click "save" in your admin CP settings once to apply this fix.

• When posting messages to Discord, their rate limits only allow 5 posts per second. So if XenRio tried to post new streams, and there were more than 5 streams, many streams would get lost. I've added a small delay per post, so that all streams get posted.
• Over time, the cached data for connected accounts gets lost. This is EXPECTED BEHAVIOR, as outlined by XenForo staff here. However, because of a bug, instead of showing "unknown account" or "account associated", this addon's connected account would show an empty #. This bug is now fixed and will instead show "account associated", in order to prevent confusion.
• Because of the confusion caused by the bug above, some intrepid admins felt the need to go into their databases and try to manually fix the missing information. In the process, they may have ended up deleting entries from the connected accounts table. Doing so, actually ends up breaking XenForo's connected account system and makes it impossible for the user to disassociate their account from Discord. In response to this, I have implemented a workaround that will force a cache reset and disassociate the account properly.

Widgetbot Bot Cluster disweb.dashflo.net has been deprecated. It has been replaced by e.widgetbot.io . It is highly recommended you update your bot cluster setting if you use Widgetbot.

Fixed a bug related to some leftover code from an older version.

Click to expand...

• Fixed direct messaging for private message conversations.

Fixed an error with the upgrade script in the last version.

Click to expand...

This is a continuation of the 2.1.1.0 update that came out a few hours ago. I HIGHLY recommend you read the patch notes for that update as well:

XF2 [8WR] Discord Integration - Updates

xenforo.com

This update continues with the normalization and standardization which began in the last update. However, this update is a bit trickier. In this version, the connected account provider has been changed from discord to ewr_discord. This will prevent collisions with other addons...

• Ban syncs will now provide a reason in Discord logs.
• Fixed the user count on the navbar based on Discord API changes.
• Fixed some thread posting based on moderation queues.

Click to expand...

• The account sync cron job has been made faster. Instead of syncing 1 account every 5 minutes (which limits to 288 accounts per day); the cron has been updated to run every 1 minute (which limits to 1440 accounts per day).
• You can now redefine the sync buffer limit on the options page. In previous versions, an account could only be synced with Discord once every 24 hours. You can now redefine this limit to make the buffer longer or shorter if needed.
• The connected accounts list will now do a better job at showing the user's avatar. It will also now include the user's discriminator ID. Unfortunately, the data may be blank until the user disconnects and reconnects their account.

I think some of the sync issues people have been having is due to a misunderstanding of how accounts are synced. Every time an account is changed on XENFORO, it is moved automatically to the front of the sync queue. However, if an account was changed on DISCORD; there was no way for XenForo to know about the changes; until the next time the account came up in the sync queue. This of course meant an account would have to wait up to 24 hours (or even more if your forum had more than 288 synced accounts on it) before the next time it cycled into the sync queue.

This means, if an account was connected on XENFORO; it was synced immediately. If the account was ALREADY a member of the Discord server, then that user immediately got all their roles as needed and everything appeared to be working properly. However, if the account was NOT a member of of the Discord server, XenForo would have no account to sync to. Then of course, when the user would join the server after the fact, there is no way for XenForo to know the account is now available to sync. So that account would have to wait till the next time it comes up in the sync queue... or they can disconnect and reconnect their account on XENFORO to force themselves back to the front of the sync queue.

WidgetBot has been having a lot of issues with their clusters. They shut down their official clusters, and then DisWeb became the official cluster... but then DisWeb had their domain stolen from them by an ex-staff member, so that had problems well. So the cluster/shard option has been changed from a dropdown menu to a simple text field with disweb.dashflo.net as the default value. So now you'll be more easily able to change the cluster at will... you could even use your own cluster if thats what you want to do.