Warning Improvements by Xon

Warning Improvements by Xon 2.11.6

No permission to download
Threshold is contextual, and only occurs if a warning action was triggered. I've updated the FAQ to indicate when various replacables are filled in

I did notice a bug in that notes wasn't being populated. Will be added in the next version
 
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?
 
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?
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.
 
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
1588448425325.webp
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).
 
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).

Just tested this further and that was the problem. Thank you @kick

Unfortunately, the facts are (as far as I can see) that if anonymised:
  • If the default anonymisation is used, a warned users reply will go into limbo as it's replying to an anonymized as a "guest" (non existing) account.
  • The issuer cannot see the conversation that was sent and cannot see any replies the warned user has made.
  • You would have to create a separate "anonymized" account to get responses (this is based on an assumption as I haven't tested that yet), which you would then have to tell all your staff how to access that account to be able to respond to user responses, adding an unnecessary step.

That's what I can think of off the top of my head, I'm sure there are others. Those three in and of themselves make the anonymisation feature (IMO) unusable.
 
Xon updated Warning Improvements by Xon with a new update entry:

2.4.2 - Maintenance update

  • 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...

Read the rest of this update entry...
 
Just found a bug with this one @Xon.

If you have "View Own Warnings" enabled, under the user profile it shows up columns "Warning, Date, Points, Expiry, Acknowledge State"

However that phrase appears to be shared with "Points" for Trophies (standard Xenforo) it seems.

As such if you change the default phrase of "Points" to "Trophy Points", you guessed it, it also shows up under Warnings as well.

1589121456698.webp
 
Hi @Xon ,

Sorry to be the one to say, but it's still doing it.

I installed the maintenance update, and then refreshed browser cache, changed Points to "PPP Points" and under Member Profile > Warnings > it comes up as "PPP Points".

SVWarningPoints Phrase is set to "Warning Points".

Is it because the Master Value is "Points"?
 
Can you screenshot exactly where it is happening?

My guess is it is XenForo using the same phrase for both (ie like I was). I can add a small template mod which patches the phrase used.
 
Awesome Xon .... thanks so much for the fast update.

I can confirm that the issue is fixed (and no refresh of cache even needed) :)
 
  • Like
Reactions: Xon
You've already got a warning category (hidden or otherwise) in your MySQLi database, hence the error.

Did you delete all the default categories and attempt to setup from scratch as in a test build that's how I got that error.

Uninstall and reinstall the add-on and that error should clear up itself as thats how I fixed it :)
 
Back
Top Bottom