Unmaintained User Essentials 2.8.4

• Fix pre-xf 1.5.13 support (undefined variable extraWhere)

• Improve robustness of the installer's legacy code upgrade path
  
• Actually implement batched updates of user's Post likes on renaming/merging, this avoids long running update statements which block posting.
  • Previous attempt was rendered non-functional by a typo and didn't expose that it was failing.

• Fix Username changes not correctly displaying on the user profile tab.
• Move more template code from the template modifications for the members_view into the useress_member_view_tabs_heading and useress_member_view_tabs_content templates.

• Fix support Tag Essentials tag preview on profile tags.
  

• xf 1.5.13 compatibility fix, do not double handle xf_thread_user_post
  • pre-xf1.5.13 would not correctly handle user merges if both accounts had posted in the same thread.
• When editing a thread, only show per-thread permissions if the thread starter has them. Applies to the following permissions:
  • [UserEss] - Lock / Unlock own thread
  • [UserEss] - Manage reply bans within own thread

This is a major rework of add-on used on https://forums.sufficientvelocity.com/ and https://forums.spacebattles.com/ for the last 4 months as the feature list and changes have evolved.

Recommend the following index changes for the Likes Given feature (Warning, may be slow):

Code:

ALTER TABLE `xf_liked_content` ADD INDEX `user_like_date` (`like_user_id` ASC, `like_date` DESC);

2.7.0 Changes:

• Use template modifications instead of template hooks
• Use hinted code event listeners
• Minify redistributed javascript
• Rebuild installer to be more robust and consistent between upgrades/new installs
  • Only add default permissions to the stock Registered User group, not every group.
• Move most bulk template code in template modifications into actual templates.
• Add flood checking to various post operations which may be expensive or vulnerable to race conditions.
• Remove Mark Alerts As Read functionality when viewing thread.
  • Please use Alert Improvements add-on instead to replace this functionality.
• Changes to watched/conversation account wrapper (better compatibility).
  • Missed conversation actions
  • Watched thread/forums account wrapper selected key fixes
  • Improve add-on compatibility by ensuring the wrapper is applied much later
• Rewrite Username change feature to be more robust and consistent
  • Improve UI for user; consistently and correctly display why a username can't be used.
  • Improve UI for moderators; by adding extra information to the moderated user name change request.
  • Moderated username changes can always be approved, regardless of the general configuration.
  • Option to control if AdminCP renames are logged to the username change history
  • Merging users merges user rename history, includes into rename history the merge event.
  • Breaks out updating username information in content to work in a deferred tasks to prevent users with huge numbers of posts blocking the site for everyone. This applies to user merging!
    • If you have "User Merge Search Update" installed, please update it to v1.1.0
• Improve MultiPrefix compatibility
• Rewrite lock/unlock own thread to work with non-moderators having the forum/global lock/unlock thread permission.
  • Under Thread Tools; users with the Lock/Unlock thread permission can prevent normal users locking or unlocking their thread.
• Rework "go invisible" feature, now with less surprises.
  • Now extendable by other add-ons.
  • By default, the user does not have their activity setting changed.
  • Use the "Force user visibility change" to revert to the old behaviour.
  • Should supress the visibility option working, not reset their preference. As otherwise group changes can result in the loss of user configuration.
  • Option to keep existing functionality for those who want it (disabled by default)
• All permissions are consistently named and prefixed
• Username must NOT match regex option

• Fix user registration when "Allow previous names" is disabled, bug introduced in 2.6.8

• The "Manage reply bans within own thread" permission now only applies to own threads, instead of all threads.
  

Fix:

• Username changes did not enforce permissions when a user POSTed a request to change their username.

Workaround:

• Enable "Moderate Name Changes" to capture username change requests. Other add-on options related to user name changing do not work.

• Fix compatibility issue with conversation improvements & conversation essentials with conversation account wrappers enabled