This patch provides, in a slightly rudimentary way, a method of allowing points to be define fore commenting on specific node types. Why is this useful? What if you wish to promote a section of your site to "boost" community effort?
In our case we have a Question and Answer section. We wanted to allocate 5 points for commenting "generally" (ie, on articles in this case) however we wanted to push users towards Q&A a bit more so we wanted to offer 10 points for commenting or "answering" a question node.
This module simply adds an extra field per node type to allow configuration of points for commenting per-content-type. Its basically the same code as code which generates the fields for points for posting a node.
There is also some code in the "userpoints_comment" function (which appears in userpoints_basc... Surely thats the wrong module name in the hook?!).
Anywho - I've implemented this on my checkout of DRUPAL-5--3 (//$Id: userpoints_basic.module,v 1.3.2.5.2.10 2008/03/04 10:51:34 jredding Exp $).
Any thoughts?
| Comment | File | Size | Author |
|---|---|---|---|
| userpoints-granular-comment-points.patch | 2.01 KB | nicholasthompson |
Comments
Comment #1
kbahey commentedI'd rather see such function in a standalone contrib module. So, in userpoints_basic, we set comments to 0, then the contrib module takes over and neat things can be done.
Comment #2
nicholasthompsonI agree that would be a better way - however I think, for the sake of consistency, that if we were to move "points for comments per node-type" to a separate module then shouldn't we also move "per node type" too?
This concept is basically an extension on the userpoints_basic idea. Personally - I believe that if userpoints_basic provides granular control for points-per-node-type then it makes sense to also provide points-per-node-type-comment...
Comment #3
kbahey commentedFirst from a conceptual point of view: userpoints_basic is optional. You can write a version that does what you want and disable the userpoints_basic itself. Or you can even take the parts you are interested in, and break each into an advanced/expanded module with more features.
So, let userpoints_basic be what it is: just basic stuff that shows what the API can do, and then write what you want the way you want because your requirements will be different from the next guy's requirements.
Second, regarding the patch itself. I think the consistency argument is fair, and you convinced me. However, from a user interface point of view, wouldn't it be less clutter to have the comment points under the node type points, so they are all in the same place? So, it would be :
Points for posting a page [....]
Points for commenting on a page [....]
Points for posting a story [....]
Points for commenting on a story [....]
Points for posting a article [....]
Points for commenting on a article [....]
Instead of
Points for posting a page [....]
Points for posting a story [....]
Points for posting a article [....]
Points for commenting on a page [....]
Points for commenting on a story [....]
Points for commenting on a article [....]
Once that is done I will commit the patch. We also need the same for 6.x as well.
Comment #4
nicholasthompsonAh I see what you mean now. Would you still like the patch rolled against userpoints_basic?
Comment #5
kbahey commentedYes.
Comment #6
Kirk commentedThis is exactly what I'm looking for. Has there been any progress?
Thanks!
Comment #7
Vuds commentedSubscribing...
Does this have any chance to get a beta version or something like that until the end of this month?
Thanks!
Comment #8
berdirSorry for spamming the participants in this issue. Due to the release of Drupal 7 and the lack of time from the maintainers, I'm closing all remaining 5.x issues for Userpoints.
Feel free to re-open this issue or create a new one for 6.x or even better 7.x if this bug is still open or feature is missing for these versions.