A lighter Moderator Warning

Wlork

Hello,

I'd like to make a suggestion based on an existing extension that no longer seems to be supported : Moderator Warnings.

I'd like a lighter version 🙂

I'd like the warnings to be displayed directly on the message. At the top of the message to be precise, like a quote. Rather than displaying a line at the bottom and clicking on it to see warnings. More practical, more transparent and it avoids CSS problems, especially on mobile.
I'd like to remove the ‘strikes’. Just a box for the moderators to write the warning that will be displayed at the top of the message.

On the other hand, I'd like to keep the notifications and warnings in the profiles.

This weekend I'll do some screenshots and drawings to explain things better 🙂

Thank you in advance

GreXXL

Wlork Moderator Warnings extensions just works perfectly fine?

Wlork

Wlork This weekend I'll do some screenshots and drawings to explain things better 🙂

As promised :

Wlork I'd like the warnings to be displayed directly on the message. At the top of the message to be precise, like a quote.

Wlork I'd like to remove the ‘strikes’. Just a box for the moderators....

GreXXL Moderator Warnings extensions just works perfectly fine?

I'm looking for a lighter and, above all, supported extension. The developer in question can't seem to answer us or do anything.... ?

Then, no, the “strikes” don't work 🙂 It's just a number. It has no impact on suspensions or anything else. As you can see from the Github description, it's still in the “TODO” list.

GreXXL

Wlork I understand your request about the lighter version of such an extension. But I wanted to clarify that the extension has no issues that force it to be labled "Incompatible" and it actually is used here on discuss as well. If you want to automate actions that's already possible with the combination of another extension: https://flarum.org/extension/nodeloc/flarum-auto-moderator

Wlork

GreXXL I understand your request about the lighter version of such an extension. But I wanted to clarify that the extension has no issues that force it to be labled "Incompatible" and it actually is used here on discuss as well.

Yes, it's not incompatible.... but “abandoned” in the sense that the original developer is no longer able to respond to our requests. I don't know if I'm making myself clear ? 🙂

That's why I took the liberty of making this suggestion. In addition to the fact that I want something lighter.