We have the same issue in fact.Started using this and while we are sending conversations to warned users, the conversations is not showing up in the issuer's inbox.
Is this intended behavior?
When checking the test account that I issued the warning to, it's saying that is was sent from "moderation staff" (guest), so a conversation was sent.
What happens if a user responds to the conversation?
My "anonymize issuer" option is also left blank.We have the same issue in fact.
In settings, the "anonymize issuer" option is left blank, which seems to indicate they shouldn't be anonymized - but they are.
Indeed that's the option that also, as a byproduct, impacts whether the issuer sees the conversations in their inbox (sent).reread option:
Anonymise warnings and warning alerts as a given user if the warned user does not have the 'View warning issuer' permission.
If Empty, uses the phrase WarningStaff.
Changing this is only retroactive for Warnings, Warning Alerts but not Warning Conversations.
Okay, open permission
View attachment 223988
If the right is turned off, it will anonymously create conversation.
reread option:
Anonymise warnings and warning alerts as a given user if the warned user does not have the 'View warning issuer' permission.
If Empty, uses the phrase WarningStaff.
Changing this is only retroactive for Warnings, Warning Alerts but not Warning Conversations.
Okay, open permission
View attachment 223988
If the right is turned off, it will anonymously create conversation.
Indeed that's the option that also, as a byproduct, impacts whether the issuer sees the conversations in their inbox (sent).
- 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...
- Only show warnings the viewing user can see.
- Support for User Essentials v2.7.0 "[UserEss] Warn posts in own thread" permission.
- Fix that the 'points' phrase used was shared with trophy points, new svWarningPoints phrase is used instead
WOAH! ...Thanks for resolving this one so quickly.Xon updated Warning Improvements by Xon with a new update entry:
2.4.4 - Maintainance update
Read the rest of this update entry...
- Patch XF's usage of
points
phrase in the list of warnings to usesvWarningPoints
phrase
- Remove duplicate : when editing a warning in the admincp
- Add "Warning Escalating Defaults - Old-age limit" option (default disabled)
We use essential cookies to make this site work, and optional cookies to enhance your experience.