remove button removes wrong post
onionweb - May 29, 2007 - 12:59
| Project: | abuse |
| Version: | 5.x-1.0-beta |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
When you click remove, it removes the wrong post. It'll remove the post listed prior to the one it should remove.
#1
I uninstalled completely and then re-installed this module.
After I did that, I got a couple pages of reports. The problem with the wrong post being referenced continues.
All the buttons on the pending page, all point to the first report. If you click a button that is at the bottom of the page, it will will remove the first post on the top of the page. All the buttons on all posts only reference the first post. Including "ban." It will ban the wrong user.
#2
changed to critical
#3
I can confirm this problem as well - trying to figure out what's causing it, but not totally sure - maybe because the HTML forms all use the same names?
#4
I fixed this issue with the attached patch.
Most of the credit goes to this explanation, it just took me a lot of time to finally dig that up :)
I'm very new at this, so if anyone can confirm it works for them, that'd be good.
#5
I'm not too sure I like the way the abuse reports are handled now what with
all the forms and the associated problems as seen in this issue. For now
I've fixed this and committed to CVS but I'd like to redo the abuse moderation
pages to use a different solution than just loads of forms.
#6
I've just updated the module to the last version (March 28, 2008 - 15:35) and the issue still happens. The form field "edit-abuse-operations-form-form-token" has the same value in all the comments.
#7
Please try new development snapshot as this should
be fixed in there.
#8
yes, I've also encountered the same problem.
I had two abuses reported and clicked allow on the bottom report, the site refreshed and allowed the top report, not the bottom.
#9
Hello, first of all I'm sorry for the long time I took to revisite the issue.
I've tried last dev version and the bug is fixed.
Thank you very much
#10
Automatically closed -- issue fixed for two weeks with no activity.
#11
I'm using 5.x-1.0-beta, which states to have this bug fixed but it's not!! I missed too many reports trying to know what was happening...
At least the "Allow" button is not working as expected. The first report of the page is the one allowed.
Going to try the latest dev now...
#12
Okay, the latest dev works fine.
It should be good to specify that the beta still has this bug and people will find it for sure if they are going to sue the module and review the flagged nodes...
#13
Automatically closed -- issue fixed for 2 weeks with no activity.