Posted by interface907 on January 2, 2009 at 12:54am
| Project: | abuse |
| Version: | 6.x-2.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | BTMash |
| Status: | needs work |
Issue Summary
None of the buttons on the moderate form are clickable for me. I am trying to review my first abuse reports and when I click on Allow, Remove or any of the buttons, nothing happens. I have tried in Firefox, IE, and Safari. It is the same in all of them. I have disabled the FCKEditor for that screen. I am running Drupal 6.2 and have the latest version of the abuse module, dated 2008-Nov-05. Am I missing something obvious?
Comments
#1
I'm going to remove the jquery functionality to see what is going on. If that fixes it, then that might be the best solution for now...
#2
I have a similar problem. If I navigate off the form page I eventually get the 'Invalid user account - content cannot be allowed' error message. The content that was flagged was created by the Anonymous user (uid 0). I've traced my problem to this code block (lines 938-942 of abuse.module):
function _abuse_allow($type, $oid) {$object = _abuse_load($type, $oid);
$account = user_load(array('uid' => $object->uid, 'status' => 1));
if ($account->uid) {
// Re-Save the node so it can get indexed if not already done so and any other important functionality is carried out by being published
The test of
if ($account->uid)fails since $account->uid is zero. Changing line 941 to:
if ( ($account->uid) || ($account->uid === "0") ) {seems to fix the problem. I'll see about rolling a patch as soon as I get a chance.
#3
Patch attached
EDIT: don't use patch. Use patch in comment 4.
#4
Changed patch. Previous patch required status of anonymous user to be 1, which is not the expected value.
#5
I am still in problem ..I applied the patch manually by understanding the patch file ..Is it okay with patch ???
#6
I'm facing the same problem. Applied the patch as described but not working.
Any ideas ?
#7
If you're not getting the error message that I described in comment #2, the patch isn't going to solve your problem. There is some other problem that the patch doesn't address.
If you are getting that error message and you applied the patch (and it applied correctly), then I don't know what the problem is. Are you getting any messages?
#8
No error messages are displayed.
#9
same here no error are displayed ... if any one got the answer than please post it over here ... thank you in advance
#10
Hi, did anyone found a solution for this problem? I am new to Drupal and i tried to review to code of the module, but i did not find the solution till now ...
#11
Also need it in my project,
Did anyone found something ?
Thanks,
#12
I was having the same issue where the links would not work and the form would not submit. The strange thing was, the issue only came up on production and not on local.
Temporary Fix:
/abuse/abuse.js
Line: 20
Replace:
url: Drupal.base_url + 'admin/abuse/moderate/content/js',
with :
url: Drupal.base_url + '?q=admin/abuse/moderate/content/js',
Hope that works.
#13
I am also experiencing this same problem, the Allow, Warn etc buttons have no action assigned. Clicking has no response.
Tried #12 and still not working :(
Didn't try #4 as not experiencing #2
We have abuse, moderation and modr8 installed..not sure if any conflict?
We also have multi-lingual installed which has caused other issues in this module so not sure if related to that?
Not a coder - just a novice who has been left in charge of the website so afraid I can't (and would insult anyone by trying!) to advise what it could be - but any help appreciated as at the moment can't move forward in this area as can't have the website live without the watchlist. but anything caught by the watchlist can't be approved if it is okay....
Interested to see any further responses.
Thanks
Beki
#14
Applying the simple patch in #4 solved my problem where comments by anonymous users with 'post comments' permission could be published normally, but could not be allowed via the abuse interface. Not sure if the patch provided is 100% ideal, but the issue should be considered a bug.
#15
Also need replace in abuse.js
With:
$(':input[@id^="edit-allow-body"], :input[@id^="edit-remove-body"]', $element).val(body);
To:
$(':input[@id^="edit-allow-body"], :input[@id^="edit-remove-body"]', $element).not('.form-submit').val(body);
It fix ploblem "Sorry, could not perform requested operation".
#16
Only security fix goes in 1.x. This one is not. Leave as "needs work" because the patch is reported not working.
#17
I think that this patch fixes the problem I described in #2. I've been running that patched code on our production site for over two years now. If I need to create a different thread that just handles that case and provide the patch there, I'm willing to do that. Otherwise, this thread has become a collection of different issues and no single patch is likely to solve all of them.