User delete ONLY their own post

kridz

All is in the title, how can i allow the users to be able to delete their own post (ONLY, not the other's one as well). I can't found it in the permissions
Can someone help me ?

hgtonight

What version number of Vanilla are you running?

kridz

2.0.18.10

hgtonight

Discussions are deleted via the DiscussionController::Delete() method in /applications/vanilla/controllers/class.discussioncontroller.php. You will need to change the permission checking to include a check for owning the discussion.

This is the current code snippet that performs the checking:

$Discussion = $this->DiscussionModel->GetID($DiscussionID);
if ($Discussion && $Session->CheckPermission('Vanilla.Discussions.Delete', TRUE, 'Category', $Discussion->PermissionCategoryID)) {
  if (!$this->DiscussionModel->Delete($DiscussionID))
    $this->Form->AddError('Failed to delete discussion');
  } else {

This is a potential modification:

$Discussion = $this->DiscussionModel->GetID($DiscussionID);
if ($Discussion && ($Session->CheckPermission('Vanilla.Discussions.Delete', TRUE, 'Category', $Discussion->PermissionCategoryID) || $Discussion->InsertUserID == $Session->UserID)) {
  if (!$this->DiscussionModel->Delete($DiscussionID))
    $this->Form->AddError('Failed to delete discussion');
  } else {

Do not modify the core files, the above snippet is only for edification purposes

kridz

unfortunately this does not work, users still can delete post/discussions of them AND other users when i put this permission on true.

x00

@kridz said:
unfortunately this does not work, users still can delete post/discussions of them AND other users when i put this permission on true.

You don't want the permission to be true, you would either need a new permission for that, or $Discussion->InsertUserID == $Session->UserID logic above. However @hgtonight 's code only covers the capability, it don't not handle the display of that option in the menu, etc.

Also you want to avoid hacking up the core. Perhaps a better way would be through s plugin using Gdn::Session()->SetPermission() on the fly perhaps using a reference permission, which you can then assign to role..

You wan to control it tightly with logic. I thought I released a plugin that used this, this turns out I forgot.

x00

Ok now i know why i didn't release it the client fell of the face off the earth, shame I think other would have appreciated Purchase Anonymous Posts.

hgtonight

@x00 said:
Also you want to avoid hacking up the core.

Very true, not sure what I was thinking. Warning added.