By parajeff on
Have Drumm's Karma and Recommended Nodes (now listed as Recommended Posts) modules been upgraded by anyone to Drupal 5.x? Both would be very handy for a discussion site I'm setting up, but I've run into problems trying to upgrade them myself.
I know there is a recommended posts view floating around -- but it doesn't seem to have the same functionality. Drumm's module allows you to set a "half-life" for how many hours a recommendation has full point value. That allows the list of recommended posts to dynamically change over time and auto-update.
Comments
new karma module
There is a new karma module at http://groups.drupal.org/node/4087
I am the author of that module...
Hi,
I am the author of the "new" karma module.
I would like to emphasize that my module:
- Does not use the votingapi, although it does interface with them
- It can do a lot, but it only allows you to add karma for *comments*, and not for *nodes*. This is for two reasons: 1) Keep the code sane, simple, and efficient 2) Focus the karma on the *comments* to a node, rather than the node itself
There are plenty of modules out there which deal with voting on nodes (fivestar, for example). I consider comments very differently.
Sometimes I think that I could after all change the module so that it allows voting on nodes as well. However, if you install the module and see how it works, you will soon realise that it would mess up completely the module code-wise AND (more importantly) in its philosophy.
I am waiting for comments to see if I should indeed release the module as a contributed module. Nobody has answered my post here yet: http://groups.drupal.org/node/4087 . So I am assuming there is no actual demand for it...
Bye,
Merc.
Excellent module!
Merc,
Waiting for posts to be answered anywhere on drupal.org often seems to be an exercise in futility. I had tried contacting Drumm directly about his modules before posting this question asking about them -- no response to the private contact or the public post.
Then, christefano posted about your new Karma module in this thread and also in the thread you had posted at groups.drupal.org (that, btw, is why I think nobody answered. I don't think most people go hunting for things in the groups yet).
All that aside, I think the module is exactly what I'm looking for, and I'm sure a lot of other people will feel the same way if they know that it exists. I'd vote for posting it as a contrib module. Thanks for putting it together.
I'll let you know how it goes on the test install I'm putting together, and also (assuming things go well) let you know when the site goes live.
Now...anyone have a functioning Recommended Posts module for 5.x that works like Drumm's 4.x one?
Thanks again for the responses to this thread.
OK!
Hi,
OK, I've put the module in the repository and created a project.
The only problem is that I am waiting for the Userpoint module author to approve a patch that resolves a bug in the Userpoint module (if a vote doesn't need moderation, the transaction is not logged). Until then, the Userpoint side of the module is not actually usable (the module uses the trail to avoid huge trouble in case a user re-votes for a comment).
Drumm responded to my message, and pointed me to the Userpoint group. Yes, I was a little disappointed by the lack of response there, but hey.
Have you downloaded the module and tested it? What do you think?
Alright, I will try and finalise the project tomorrow. I am not sure what I should do to make it actually show up in the list of modules - I will try and find out tomorrow!
Bye,
Merc.
Submitted...
Hi,
It was raining here today. So, I ended up working on Saturday morning (!).
I've done it: the module is now:
http://drupal.org/project/simple_karma
However, it hasn't been promoted to the list of modules. AND, the script hasn't created the development release yet either!
Parajeff, you have managed to download it already, right? If not, please wait approx 10 hours, and the developer's snapshot will be created.
I also have 6 more modules to commit - including node_article.module, which is *major*. However, well, now I know how CVS works, which means that I am more comfortable with releasing the other modules.
Bye!
Merc.
Thanks...
Yes, I've already downloaded the module and will be installing it and checking it out on a test Drupal 5.1 install this weekend. I'll let you know how things go -- and I'll be installing a number of other modules as well and checking to make sure everything plays nicely together *gr*
I'm also curious about the node_article module you mentioned. I did a quick search, found the info you had posted elsewhere, and it sounds interesting. What are the other 5 modules you mentioned? Also related to your online magazine?
Thanks again for answering my post, and for the work you have done on getting a Karma module up and running.
The other modules
Hi,
OK - please let me know how simple_karma goes!
Node_article is also production-ready. But I still haven't written the basic documentation etc. It's a module specifically per magazines, and it's the next one I am gona put online (once simple_karma is out).
The others?
simple_pdf - OK, this is not duplicating anything :-D This module simply generates PDF files (with cache enabled, meaning that you only generate the PDFs once [and yes, the cache is cleared if the node is modified]) using HTMLDOC. This is the next one going up.
node_issue - to make a magazine's issue. Again, it's thought for magazines, with issues, sections in each issue, and a placement within that section. It works beautifully.
fsm_print - gives the print preview of a node. It's a simplification of the "print" module that comes with Drupal. I did it because I didn't agree with the complexity of the print module - I thought it was trying to do too much. And, it's not supported - I wanted something small, powerful and supported (by myself!). I feel uneasy about releasing it because there's strong duplication
figure_per_node - again, duplication. In Free Software Magazine we already have about 6000 image files. In 1 year, we'll have about 20000. In Drupal, I couldn't figure out a way of storing images so that 1) They wouldn't change their name unexpectedly 2) wouldn't be stored in a big directory that would eventually explode. Also, I needed very precise constraints (what type of files could be uploaded, and how big they were). So, I wrote it. SImple, but efficient.
diff_simple - again, Duplication! The diff module that comes with Drupal now doesn't do word-for-word comparison anymore, and I don't think it uses the best comparison engine. So, I wrote my own (based on the old diff module). I also simplified it - some authors are not able to compare version 2 with version 9; all they want (and can) do is comparing between two subsequent versions. Which is exactly what this module does.
The last three modules... I don't know if it's fair to release them. Figure_per_node, probably yes. But the others... hummmm... I will want to check with the other developers first. I will not enter arguments if they start talking about me patching their existing modules etc. I might just link them from node_article, since they are magazine-oriented modules.
Bye,
Merc.
Thanks!
Sounds like great work. Thanks for committing Simple Karma -- and for the teaser of what's to come.