[DBTech] DragonByte User Tagging 1.8.0

Update highlights

The only change in this version is that we've added an install-upgrade.json file in preparation for compatibility with the [TH] Install & Upgrade add-on.

To read more about the changes included in v1.0.3 please click here: https://www.dragonbyte-tech.com/store/dragonbyte-user-tagging.378/release/1717/


Complete Change Log

Change: Added install-upgrade.json

Update highlights

This update fixes an issue where the alerts for mentions would be hidden if the user group mentions feature was enabled. Sorry about that

To read more about the changes included in v1.0.3 please click here: https://www.dragonbyte-tech.com/store/dragonbyte-user-tagging.378/release/1717/


Complete Change Log

Fix: Fixed an issue where the user group mention feature would prevent mentioned user alerts from going through

Update highlights

This update fixes an issue where the Email Stop feature for emails on new tags would reference an invalid column. Sorry about that

To read more about the changes included in v1.0.3 please click here: https://www.dragonbyte-tech.com/store/dragonbyte-user-tagging.378/release/1717/


Complete Change Log

Fix: Fixed an invalid column reference in the EmailStop feature for "Email on tag"

Update highlights

This update adds a new feature that was requested by our customers: The ability to browse, search & delete hash tags via the AdminCP.

The browser will display each individual usage of a hash tag, so if for instance the hash tag "test" appeared in 50 different posts, there would be 50 different entries in this list. Clicking on each individual hash tag usage will bring up an overlay containing a quick link to the content in question.

You can also delete individual hash tags, though it is worth noting that this will not remove the BBCode from the post. Removing the BBCode would simply result in the hash tag being re-added to the system.

The other significant feature in this update is the ability to receive email notifications when you're tagged in a thread. You can control the registration defaults via the "User registration" options page, and each user can control their email preferences via the Preferences page. These emails also make use of XF2's "Email Stop" system, so users can opt out without needing to be logged in.


Complete Change Log

Feature: Hash tag browser in the AdminCP
Feature: Email notifications for thread tags
Change: Deleting a hash tag will now also recalculate the usage statistics
Change: Slightly reworked the content tag alerts to be content type specific

Update highlights

This update adds support for the censor system in XenForo 2 by preventing from being added to the system hash tags that match your site's censorship rules.


Complete Change Log

Change: Hash tags containing censored words will no longer be added to the system

Update highlights

This update adds support for the minified JavaScript loading in XF2, meaning that while your site is running in production mode (i.e. not in debug mode), the JavaScript files loaded will be much smaller.

• core.js has been reduced from 5kb to 3kb
• editor.js has been reduced from 11kb to 6kb

Support for minified JS for other XF2 products will be rolling out as I update them.


Complete Change Log

Change: JavaScript files served by this mod are now minified

Update highlights

This update fixes an issue with the Change Log in XF2, where installing this mod would only display correctly for this mod (and other mods loading after this), breaking default XF2 change log entries.


Complete Change Log

Fix: Fixed an issue where the user change log for XF itself and other addons would display phrases

Update highlights

This update fixes an issue where editing content where hash tags are supported would not correctly insert an entry into the "hash tag usage" table, leading to an incorrect error message saying "no usage found".

To resolve this issue for existing posts, you will need to edit each individual post and remove the BBCode, e.g. [HASH=1]#test[/HASH] should be edited to #test and then save the post. That will correctly rebuild the usage table.


Complete Change Log

Fix: Fixed an issue where editing posts / profile posts / profile post comments would not correctly add an entry to the hash tag usage table

Update highlights

This update fixes a couple minor issues from the initial RC1 release. Numeric hash tags (e.g. #4 etc) are no longer allowed, and neither are spaces.

This should reduce the amount of incorrect hash tags being generated


Complete Change Log

Fix: Fixed an issue where numeric values (such as #4) would be considered valid hash tags
Fix: Fixed an issue where spaces would be allowed in hash tags