Discourse no bump Plugin is too restrictive

Product Support

AI-generated summary

The discussion revolves around the Discourse no-bump plugin being overly restrictive, specifically blocking private messages (PMs) with the error “Please wait for others to participate.” itsbhanusharma confirms the issue is tied to the plugin, noting the error disappears when trust levels are lowered. Mittineague questions whether the plugin is truly responsible, suggesting users may be misusing @mentions instead of invites or edits. sam asks eviltrout if recent changes caused this, to which eviltrout responds that no changes were made but affirms PMs should be exempt from the no-bump rule, referencing a relevant commit. The core issue appears to be unintended plugin behavior affecting PMs, despite the intention to ignore them.

1

The no bump plugin has become so restrictive it is stopping people from even sending PMs to each other.

The same “Please wait for others to participate” message is shown to people when they reply to a PM.

4

Are you certain it’s the discourse-no-bump plugin?
I’m not seeing an “allow others to participate”, I see

Assuming that’s the message you meant, I’m guessing that instead of using the Invite or editing their existing post members are using @ mentions in a second post?

5

Yes I’m certain that this is being triggered by the no bump plugin, Because the error matches the no_bump_error when a fellow was trying to pm me.

Screenshot%20(190)
Screenshot%20(190)1283×701 49.2 KB

As soon as I reduced the no bump trust level, the issue disappeared.

6

@eviltrout did anything change with the plugin recently? Should PMs be blanket ignored?

7

Nothing changed, but I do believe PMs should be ignored:

https://github.com/discourse/discourse-no-bump/commit/63ac5ba720a1bc902d018fe5e091a287524f9640