Closed (won't fix)
Project:
Abuse
Version:
6.x-1.1-alpha1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Feb 2011 at 05:08 UTC
Updated:
6 Mar 2011 at 18:54 UTC
In functions _abuse_disable() and _abuse_remove()
status changed directly in DB.
In this case all nodeapi hook doesn't called, and it's cause bugs. I.e. disabled/removed content can be found thru search some time instead instantly removing from index.
I think it should use node_save or call nodeapi hooks manually.
Comments
Comment #1
jcisio commentedThat was the problem in 1.x where the status is used to mark an abuse. This issue won't exist in 2.x (not release :( yet) where a separate table is used to track abuses.