Topic OP moderation Plugin

[Lhc_fl (Linca)]

Continuing the discussion from Ability for users to act as moderators on their own topic:

@Lhc_fl

Does anyone still care about this?

I have a forum that needs this, and I’ve developed a plugin for it - it’s still in active development, but almost all the features mentioned in this topic are already available.

Anyone willing to try it?

By the way, its I18n support is not good

This plugin has basically been developed and tested now.

GitHub - Lemon-planting-light/user-autonomy-plugin

Features

I don’t really like to explain its functions, so I decided to use pictures to illustrate what it can do.

Users

• It adds a button appears just after topic-admin-button for public topic’s creator
• PM is not supported since I don’t think it’s necessary.
  
  
• Everyone should apply before gain moderation permissions, but the application can be automatically approved.
  
  
  
  
  
• After application, moderatior buttons would appear.
  
  

Manipulating Groups

• This button appears in every topic
• The options below the dividing line will only appear if the user is Staff
  
  
  
  
  

Admins

• It added a whole tab to the settings because it was a bigger plan
  
• Site settings
  
  
• It will create logs in a special topic
  
  

Important notes

After installation, please follow the instructions below before enabling the plugin

• Before enabling this plugin, you need to create an account to be used as a “User Assistant bot”. Although this plugin can automatically create bot user or use existing @Discobot, I don’t recommend doing that, because the bot users created by the plugin cannot be modified in the admin panel. You can grant it any permission you want, because in fact, the relevant code is specially written to make the bot always act as Admin, but I suggest that it is best to grant it Admin or moderator permissions. During development, sometimes unknown bugs that I cannot reproduce stably are caused due to this reason.

• Then, you need to create a topic, which can be a private message or a public topic. Fill in its topic_id to SiteSetting.topic_op_admin_logger_topic. If topic_op_admin_enable_topic_log is turned on, the above bot will create more detailed log posts within the topic.

• After creating the user assistant robot, write down its user id, and then fill it in SiteSetting.topic_op_admin_bot_user_id above.

• Opening certain settings without following the above steps correctly can cause errors or even break your website

[Heliosurge (Dan DeMontmorency)]

Have you considered seeing if you can tie the bot to category mod group? As full Mod/Admin imho might be risky.

There aree a few plugins that have been on the plugin category marked experimental until it was considered out of development phase like Who’s Online.

Maybe @Canapin can look into category and discuss with you.

[merefield (Robert)]

Great going, good luck with the development!

@Lhc_fl

I’m not sure what category it should be placed in. Considering it’s still under active development, I put it in dev

I wonder if we should have “Alpha” and “Beta” tags in plugin?

That would make new plugins easier to find and also reflect the risk you would take installing them …

[Lhc_fl (Linca)]

@Heliosurge

Have you considered seeing if you can tie the bot to category mod group? As full Mod/Admin imho might be risky.

Plugins are code that runs alongside Discourse. It is not a problem for the bot to have any permissions, from Admin to TL0, because in fact it is just an object of code operations, and it has unlimited permissions.

@Heliosurge

There aree a few plugins that have been on the plugin category marked experimental until it was considered out of development phase like Who’s Online.

In fact I have now finished developing this part of the plugin. But I’d be wary of publishing this plugin to plugin given the more catastrophic consequences if a plugin (rather than theme component) goes wrong.

I will release it officially after the plugin is launched on my forum and after a period of verification.

[Lhc_fl (Linca)]

This plugin has basically been developed and tested. Now you can install it with confidence!
(but follow the steps written above:

@Lhc_fl

Important notes

After installation, please follow the instructions below before enabling the plugin

• Before enabling this plugin, you need to create an account to be used as a “User Assistant bot”. Although this plugin can automatically create bot user or use existing @Discobot, I don’t recommend doing that, because the bot users created by the plugin cannot be modified in the admin panel. You can grant it any permission you want, because in fact, the relevant code is specially written to make the bot always act as Admin, but I suggest that it is best to grant it Admin or moderator permissions. During development, sometimes unknown bugs that I cannot reproduce stably are caused due to this reason.
• Then, you need to create a topic, which can be a private message or a public topic. Fill in its topic_id to SiteSetting.topic_op_admin_logger_topic. If topic_op_admin_enable_topic_log is turned on, the above bot will create more detailed log posts within the topic.
• After creating the user assistant robot, write down its user id, and then fill it in SiteSetting.topic_op_admin_bot_user_id above.
• Opening certain settings without following the above steps correctly can cause errors or even break your website

[orangeandblack5]

@Lhc_fl this looks super useful, but does it allow the OP to post on their own topic while it is closed, like a moderator or admin could? To us that seems like a much better flow than making them unlock it, post, and then re-lock it.

[Lhc_fl (Linca)]

I’m planning to add this feature - but I’ve been busy recently and don’t have much time to look at my plugin. Anyone interested can submit a pull request

[fbpbdmin (deepblue)]

@Lhc_fl
this is a nice plugin,

• possible to make this a theme component ? more folks will be able to use this,
  we don’t have permission to install plugin to the instance, but could install theme component.

• could add the “Split and merge topics” to the permission list ?

thanks…

[Lhc_fl (Linca)]

@fbpbdmin

possible to make this a theme component ?

No, it’s impossible because it needs to interact with the database.

@fbpbdmin

could add the “Split and merge topics” to the permission list ?

Maybe, but it’s more difficult. I don’t have the energy to add new features to it recently.

[Lhc_fl (Linca)]

I’m sorry that this plug-in is incompatible with the new version of discourse due to the upgrade of ember.js, but I am too busy now to fix it. If anyone is willing to fix it, please PR it on Github

[Lhc_fl (Linca)]

I upgraded this plugin today to adapt to the new version of discourse. Now the plugin is no longer broken

[whitewaterdeu (王白水)]

i have opened User autonomy plugin enabled , but there is an error after submitting request

this is the log in browser terminal

chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:393 
 SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
    at D.parse [as parseJSON] (<anonymous>)
    at l (chunk.7b3110aa5b5be8…1d8cd9.js:393:63167)
    at p (chunk.7b3110aa5b5be8…1d8cd9.js:393:63847)
    at k (chunk.7b3110aa5b5be8…41d8cd9.js:308:3688)
    at w (chunk.7b3110aa5b5be8…41d8cd9.js:308:3581)
    at f (chunk.7b3110aa5b5be8…41d8cd9.js:308:3077)
    at invoke (chunk.7b3110aa5b5be8…1d8cd9.js:121:10063)
    at m.flush (chunk.7b3110aa5b5be8…41d8cd9.js:121:9140)
    at g.flush (chunk.7b3110aa5b5be8…1d8cd9.js:121:11012)
    at q._end (chunk.7b3110aa5b5be8…1d8cd9.js:121:16062)
    at q.end (chunk.7b3110aa5b5be8…1d8cd9.js:121:13189)
    at q._run (chunk.7b3110aa5b5be8…1d8cd9.js:121:16576)
    at q.run (chunk.7b3110aa5b5be8…1d8cd9.js:121:13722)
    at c (chunk.7b3110aa5b5be8…1d8cd9.js:161:53419)
    at t.error (chunk.7b3110aa5b5be8…d8cd9.js:302:131483)
    at l (chunk.7b3110aa5b5be8…1d8cd9.js:191:58317)
    at Object.fireWith [as rejectWith] (chunk.7b3110aa5b5be8…1d8cd9.js:191:59062)
    at C (chunk.7b3110aa5b5be8…41d8cd9.js:194:5783)
    at XMLHttpRequest.<anonymous> (chunk.7b3110aa5b5be8…41d8cd9.js:194:8211)
l	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:393
p	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:393
k	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:308
w	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:308
f	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:308
invoke	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
flush	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
flush	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
_end	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
end	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
_run	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
run	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
c	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:161
t.error	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:302
l	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:191
fireWith	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:191
C	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:194
(匿名)	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:194
XMLHttpRequest.send		
send	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:194
ajax	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:194
o	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:302
(匿名)	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:308
e	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:308
D	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:302
submit	@	request-op-admin-form.js:106
(匿名)	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:421
invoke	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
flush	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
flush	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
_end	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
end	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
_runExpiredTimers	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
setTimeout		
setTimeout	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
_installTimerTimeout	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
_reinstallTimerTimeout	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
_later	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
later	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:121
T	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:161
_triggerAction	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:421
click	@	chunk.7b3110aa5b5be8…8f9.d41d8cd9.js:421