Warning Improvements by Xon 2.9.5

• Remove duplicate : when editing a warning in the admincp
• Add "Warning Escalating Defaults - Old-age limit" option (default disabled)

• Patch XF's usage of points phrase in a user's list of warnings to use svWarningPoints phrase

• Fix that the 'points' phrase used was shared with trophy points, new svWarningPoints phrase is used instead

• Only show warnings the viewing user can see.
  • Support for User Essentials v2.7.0 "[UserEss] Warn posts in own thread" permission.

• New "Anonymize warning conversations" option, default disabled. Reverting to pre-v2.4.0 behaviour.
  • If using Anonymize Warning feature, please enable this option.
  • Warning Conversations can not have their conversation starter retroactively changed and introduces a change in moderator work-flow if anonymized.
  • The paid Warning Acknowledgement add-on is probably a better solution if you need an anonymized warning notification system compared to conversations.

• Fix "TypeError: Argument 3 passed to XF\Service\Conversation\Pusher::setInitialProperties() must be an instance of XF\Entity\User, null give"
• Fix error when "Anonymise as" is not set to a real user, and a guest user is used instead
• If installed, Recommend updating Conversation Essentials to v2.3.11+ if users lack the "view warning issuer" permission

• Ensure warnings & notifications are transactional
• Add content action variable to message replacements (thanks @TickTackk)
• Support anonymized warning conversations

• Remove XF2.0 support, require XF2.1+
• Fix case where the alert/push notification for a warning is not correctly anonymized

• Fix error when Report Improvements is not installed/enabled and notices for warnings/warning actions are created
• Use phrase groups instead of individual phrases when creating threads/posts for Warnings and Warning Actions

• Ensure thread notifications do not occur inside the transaction when issuing a warning that causes warning action notifications