This plugin prevents users from bumping their own topics. On some higher traffic forums, if a user doesn’t receive replies to their topic they will reply to themselves (bumping) repeatedly to gain visibility.
When enabled, a user will need to wait for a different user to reply to their topic before they can reply again.
Staff members can always bump their own topics
Settings
no bump enabled - set to true to enable the plugin
no bump trust level - users at this trust level (and lower) will not be allowed to bump their topics
Hosted by us? This plugin is available on our Enterprise plans
Bonjour, j’essaie d’installer ce composant depuis l’interface admin depuis le dépôt Git mais j’ai le message d’erreur suivant : “Une erreur est survenue : Import Error: about.json does not exist, or is invalid. Are you sure this is a Discourse Theme?”
Comment pourrais-je régler le problème s’il vous plaît?
Good day,
I’ve been attempting to install this component via the admin interface from the Git repository, but I’m encountering the following error message: “An error has occurred: Import Error: about.json does not exist, or is invalid. Are you certain this is a Discourse Theme?”
I would be most grateful if you could advise me on how to resolve this issue, please.
This is a plugin rather than a theme component so needs to be installed in a different way. If you follow the instructions (Install plugins on a self-hosted site) it will show you how to add it to your app.yml and install it on your site.
Ok I didn’t know, I’ve some things I could install like a component while I believed it was a plugin I’m a beginner with discourse and I crashed myself many times in the wall of my ignorance^^
So, possibly it will be difficult to install it because I create a professional forum on a VM where I don’t have direct access but I’ll see.
It can be confusing. Theme components generally only change the front end, whilst plugins need to change the back end so need to be added at build time and not via the UI.
Everything has its learning curve and there is nothing to apologize. Discourse is super easy and logical (after basics, of course) when compared to Mastodon server — I just couldn’t understand how to upgrade it, and if I’ve nagged documentation of Discourse it is superb, when docs of Mastodon are more or less just absolut minimum and everyhing is more messages between devs. So with Mastodon isn’t enough learning Mastodon, but one must understand how git works. Well, we have another mystical creature Docker, but (almost) every admin can handle Discourse with zero understanding of Docker.
Yet handling of plugins could be more… human
Back to topic. Sometimes there is need to answer and there is no need to bump. When there is extra piece of needed data and there is a fear that those who are already red OP doens’t understand that starter is edited. So perhaps there could be certain time limit before no-bump kicks in?
Or is this just another policy question and makes simple thing too difficult?
About the need of this special plugin no-bump, it’s not absolutely necessary for me in fact, but I had the same issue with others plugins more interesting too so, the answer for this plugin responds too for others plugins . That was I would to know and…I know now
I’ll try to bribe the sysadmin of the VM to give me some rights now
I’m a beginner with discourse and I crashed myself many times in the wall of my ignorance^^
