I'm not sure if this is a bug or more of a question. I set up a posting event on a node that was limited to every 18 hours and I noticed the negation issue a little while later. Fortunately the update had just been released for this, so I installed it. It did stop extra negations from taking away credits, but I'm wondering if it could still be adjusted a little bit.
In one test I did, I made a new post which gave me the credits. I then edited an older post, which took away credits. But this basically cancels out any credits I made in the 18 hour block since I edited a different one.
Is it possible to have the negation events check the reference_id / content_id and only apply if a positive event on the same post was applied? And also, when the edited post is resubmitted, the positive amount would still go through since the post was originally allowed. (In other words, events for the edited posts would be allowed only if the original post had an event applied.)
Note: I currently have the "Smart event negation" setting turned off. Not sure if this would affect anything if I turn it on.
In one test I did, I made a new post which gave me the credits. I then edited an older post, which took away credits. But this basically cancels out any credits I made in the 18 hour block since I edited a different one.
Is it possible to have the negation events check the reference_id / content_id and only apply if a positive event on the same post was applied? And also, when the edited post is resubmitted, the positive amount would still go through since the post was originally allowed. (In other words, events for the edited posts would be allowed only if the original post had an event applied.)
Note: I currently have the "Smart event negation" setting turned off. Not sure if this would affect anything if I turn it on.
Last edited:
