#2141 closed defect (bug) (fixed)
Forum Topic delete button warning before deletion
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | 1.2.2 | Priority: | major |
Severity: | Version: | ||
Component: | Keywords: | needs-patch dev-feedback | |
Cc: | snark |
Description
When viewing a topic or topic reply, admins see edit/delete options, as do regular members for their own posts. If a user with such privileges clicks "delete" by mistake, instead of "edit" or "#", the Topic or Reply is automatically deleted.
There should be an intermediate, "Are you sure you want to delete this Topic/Repy" message that you have to confirm to make a deletion. It's too easy now to accidentally delete your Topic or reply, and I have had user do just that.
Change History (6)
#4
@
15 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
Not sure what @cnorris23 is talking about re:blogs -- the issue of this ticket is deleting FORUM topic and topic reply posts without getting a warning.
@andy -- you wrote above that it was fixed in trunk#2827, but I just installed trunk#2829 and verified that the issue still exists: one-click on the topic reply "delete" button deleted the reply, with no pop-up warning box.
#5
@
15 years ago
- Resolution set to fixed
- Status changed from reopened to closed
This is fixed in the 1.2 branch, not trunk.
#6
@
15 years ago
@snark
I'm very much aware of that your ticket was about deleting a "FORUM" topic. The message was not for you -- hence the lack of @snark, or a reporter-feedback tag -- it was for the developers, to speed up the process of closing the ticket. In order for the "Are you sure?" message to appear, a particular line of javascript needs to show up on the page, in the HTML code. This is the case for every instance an "Are you sure?" message should appear. However, there was a line of code in the code posted above, this line to be specific,
if ( $current_blog->blog_id != BP_ROOT_BLOG ) return false;
that only allowed the javascript to be shown on one very particular blog. That's what "re:blogs" was about.
The problem here is in with bp-core-css-js.php with the function:
The jQuery code needed to trigger the confirmation dialog is only included if the current blog being visited is the same as the root blog. I don't know if there's a particular reason for only showing it on the root blog, so I didn't write a patch. I do know that there are multiple links with the
confirm
class added, and they are not getting any confirmation dialog.