I’m looking for an option to disable this feature as it may cause some complexity in managing threads when you have different moderators teams for different categories and suddenly they find themselves with a big or controversial thread in their category without prior notice. I’ve read here Access rights for moving a topic to another category but it says that this is something that only Trust Level 3 should be able to do. I’ve a test environment in which a Trust Level 2 user was able to do that. I tried to enable the “disable editing after staff edit a post” but it didn’t seem to affect the ability to change category for a thread. Am I missing something here? I probably am :smiley:

Alright, thanks to a good friend who suffer from insomnia we figure out where to find the right hook :stuck_out_tongue: Here is it, it also adjust the form visuals and allow to select a minimum trust level from which the access to editing category will be available anyway (default trust level 0 to be in line with default discourse settings) [image] GitHub - netgamers-forum/discourse-restrict-edit-category Contribute to netgamers-forum/discourse-restrict-edit-category development by creating an account on GitHub. I’ll go create a new topic in the #plugin section now. Thanks a LOT @Canapin for pointing us in the right direction at the start :heart_eyes:

Not sure would need to do some testing. A category group mod may still be able to move a topic via edit or move command. You may want to look into the #plugin Custom Trust Levels as well.

I checked that and will take it into consideration but I’ll try first to create a simple component that hide that select for editing except for staff. I prefer plugins that does simple things :slight_smile:

@Canapin provided me code to hide like button from groups not within a specified groups. It may give you a good baseline to work from. [image] Looking to hide Likes & Decorate Op Development You can hide the like button with CSS, but that won’t prevent users from liking posts (a plugin would be required to ensure that), if they figure out how to un-hide the button for example. I suppose the easiest way would be using CSS Classes for Current User's Groups which adds the current user groups to the body classes, then use CSS such as: body.category-your-category-slug:not(.group-group_name) { button.like { display: none; } } Let me know if you have trouble understandi… fixed link

Thank you so much @Heliosurge (and the ubiquitous @Canapin :stuck_out_tongue: ) I was just thinking of where I could look for a similar plugin to use as example :slight_smile:

Your quite welcome! The team and this community are awesome in my xp. :clinking_beer_mugs::smiling_face_with_sunglasses::+1:

I gave it a look, it’s a good MVP but the community I look for is quite tech savvy and it would be better if the DOM would entirely skip drawing that component instead of simply hiding it from view. Would that require a plugin or is it something I could achieve anyway with a component? What I need to do, roughly is basically determine if the HTML for that select is generated or not, based on the role.

I’m pretty sure a component would suffice.

I’m not a coder. To hide the category selector when you edit the first post (from the edit post action, not the edit title), this works: let currentUser = api.getCurrentUser(); api.modifyClass("component:composer-title", { pluginId: "PreventCategoryChange", didInsertElement: function() { if(currentUser.trust_level == 1) { let categoryInput = document.getElementsByClassName('category-input')[0]; let miniTagChoser = document.getElementsByClassName('mini-tag-chooser')[0]; if(categoryInput != null) { categoryInput.remove(); if(miniTagChoser != null) { miniTagChoser.style.marginLeft = '0'; } } } } }); [chrome_NTAAc37JXB] I used the trust level, but I think you can manage to check the user group instead, it’s all in the currentUser object. I don’t know how to dynamically remove the category selector when we edit the title. Maybe you can figure it out from the files that seems related: discourse/app/assets/javascripts/discourse/app/templates/topic.hbs at 53695e7d29e718041fa53bf4fef21e02354a4088 · discourse/discourse · GitHub discourse/app/assets/javascripts/discourse/app/controllers/topic.js at 8fc11215e195a5bd8db130f52717c126c119432b · discourse/discourse · GitHub

Thank you so much @Canapin I’ll need to add something also for the edit from the title but this definitely help already :slight_smile: When it’s done, I’ll post it in the theme components section here so other may use it :wink:

This discourse/app/assets/javascripts/discourse/app/templates/topic.hbs at 53695e7d29e718041fa53bf4fef21e02354a4088 · discourse/discourse · GitHub seems to be the right handle to access, now if someone knows how to interact with it via theme component… :stuck_out_tongue:

Prevent users from moving topics in other categories

Development

Crius (Crius) February 27, 2023, 4:55pm 19

Yes, that’s why I was looking into plugins as well but for a first version, a component is enough.

Topic		Replies	Views
Restrict Category Editing for Topics Theme component	0	697	February 24, 2023
Theme component to hide topics if user is in a certain group Marketplace	5	1172	January 9, 2023
Users can't change the category of a topic, if the category is not allowed to everyone (even with the right permission) Bug	9	1261	August 21, 2020
Hide categories according to user group membership Theme component	16	4481	October 6, 2019
Access rights for moving a topic to another category Product Support	7	1277	August 11, 2023

Prevent users from moving topics in other categories

Related topics