Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

forum topic access rights #75

Open
kayjay07 opened this issue Jun 21, 2019 · 5 comments

Comments

Projects
None yet
3 participants
@kayjay07
Copy link

commented Jun 21, 2019

Is there any way we can control the access right for the user not to delete the topics under the forum module. Currently, it seems the user can delete their topics.

@Givo29

This comment has been minimized.

Copy link

commented Jun 27, 2019

Currently there are three cases for which a user can edit or delete a forum/message:

  1. The forum creator can delete their forum
  2. Administrators can delete and edit all forums and messages
  3. Message authors can edit and delete their own messages.

From what I can see there is no way to change that for the moment, what kind of functionality are you looking for?

@kayjay07

This comment has been minimized.

Copy link
Author

commented Jun 27, 2019

Thanks for your reply. Much appreciated. Actually, I was aiming for functionality that user should not delete their message if a reply is posted to that message avoiding the break in the transcripts loop.

@Givo29

This comment has been minimized.

Copy link

commented Jun 27, 2019

No problems,

I see what you mean, when a user deletes their message any replies to it are moved up.

I can look into how this could be changed: Its not too hard to simply restrict a comment author from deleting their comment but that won't solve the problem of an administrator doing the same thing. I'll have a look and see if it would be possible to check for replies on delete and possibly either delete all replies or notify any users that the original comment has been deleted.

@ajdonnison

This comment has been minimized.

Copy link
Contributor

commented Jul 16, 2019

Should we instead go from actually deleting to marking as deleted, but keeping the message in the database? Then on the user interface, if it is a child of another, or has children of its own, display as "message deleted", and allow an admin to undelete?

@Givo29

This comment has been minimized.

Copy link

commented Jul 17, 2019

Yeah I think that would be a good solution for it, once I get a test server running at home I can take a proper look at how I might be able to implement it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.