About This File

This plugin will preserve the identity of your moderators by using a generic user as the author of warnings.

Notes:

• Only moderators with permission Can issue warnings? can view the real moderator on warning details
• Warned members won't be aware of the real moderator who issued the warning: the user won't see the real moderator on warning details or on received email
• The generic moderator does not have to be a moderator; you can choose a regular member
• Real moderators will be back on plugin uninstall

 

 

Edited May 27, 20168 yr by Adriano Faria

Can this be updated for 4.2? I can't even install it - I got an "1S111/1" error when I tried.

Edited September 20, 20177 yr by Hezeber

Hi Adriano,

Will this work with 4.3.5?

Thank you in advance!

Kind regards, Wim

 

I don’t see why not. If want to wait for a test, I’ll let you know today later or tomorrow in the morning. 

looking at purchasing this as well

just waiting to hear if it is ok for 4.3.5 ?

 

I recently purchased and installed this on my site but it doesn't appear to be working. I viewed a profile as a member and it still showed which moderator issued a warning,

What's New in Version 1.1.0
 

New feature:

• Add the ability to choose a generic moderator per warning reason.
  • If a moderator isn't provided for a specific reason, the moderator from the app settings will be used

Instructions:

Plugin converted to an application due to an IPS request. Simply install the application and it will take care of everything:

• Will copy the plugin data to a proper application table
• Will copy the settings
• Will uninstall the plugin

 

A background task runs after the app install to move data from the plugin to the app table. Plugin will be uninstalled after this process.

No, you don’t need to set a moderator for each type. It will use the setting if it hasn’t.

Worked fine to me. Can’t reproduce.

 

Maybe the background task didn't have a chance to run, as you didn't say anything about it above

I did:

 

A background task runs after the app install to move data from the plugin to the app table. Plugin will be uninstalled after this process.

So let me try again, in a simpler way. A background task is fired when the app is installed; last process on it, actually. As you might know, background tasks (queue) runs based on a task that runs at every minute or so, if you’re using Cron; if you’re not, it might take a few minutes. After start, it will copy the data from the plugin table to a new table created by the app. Depending on how many records you have, it can take more than one batch to go through all records and insert into new table. The whole process can take a few minutes, again, depending on your server configuration/number of records.

So if you went immediately to Plugins page and manually uninstalled it, you deleted the data from real moderators of your warnings. All you had to do was: go to Dashboard (you would see the background task there); wait a couple of minutes or even ask in this topic before uninstall the plugin.

Btw, I’ll release a new version to add a routine (existing in the plugin and forgotten in the app) to swap the generic moderators for the real one when uninstalling the app.

 

Does it stop getting duplicated with it disabled?

Confirm. When the plugin is disabled the duplicates stop.