Kian wrote:A quick and dirtier fix might be to have both at the same time, which may not require a template rewrite at all (though I'm not sure about that). I.e., if you change the <voting> </voting> block in the php, could it be possible to just display the aggregate of + or - votes before the individual votes?
So you would end up with front-end reading: <normal etc font>+10</font> [red thumbsdown logo] 5 [red thumbsup] 15
Dunno, just thinking out loud...
This is what I originallhad working 100% in my own branch of the codebase. However I had to "clone" every single block of code related to voting and resulting in several new hundred lines of code (because I don't know enough to re-write the existing code, just add conditional branch and alternate code) and even then I couldn't get the AJAX to work right - whenever someone voted on a post, the "-2" would
transform from -3 (new combined) back to 5 / 2 (current seperated)
My personal preference would be to ditch the separate numbers completely in favour of a combined +ve or -ve number of some sort, but others may have different views about it.
Exactly the reason why this hasn't become the new default
I'd prefer a combined method, but others might not. The soon to come Premium Skins will probably contain a combined number and the free "basic" skins will retain the classic mode.
It would be great if there was a separate permanent RSS feed that contained ALL the comments on various articles, so someone could subscribe to the full comments RSS and read all activity on a site rather than just on one article.
That's a good idea for a module