Closed (fixed)
Project:
NodeReview
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
12 Aug 2009 at 19:08 UTC
Updated:
28 Mar 2011 at 06:17 UTC
Jump to comment: Most recent file
Comments
Comment #1
junedkazi commentedIf a user has already added a review he cannot add a new review for the same node .
Comment #2
Equ commentedDeleted.
Comment #3
Equ commentedComment #4
Jan van Diepen commentedWe were struggling with the same issue. We wanted a single user to be able to review a node twice. It is for a competition that stretches over multiple rounds. Each round the same node has to be reviewed, possibly by the same person.
We rewrote the module to have a so-called "nodereview type". The nodereview type holds the axes. Each nodereview type can be assigned to one or more node types. That also means we can assign different nodereview types to the same node type. Without making any changes to the access system a user is able to review a node multiple times using different nodereview types.
Access to the nodereview (type) configuration has been moved from "content management" to "site configuration".
It also needed some major changes to the database schema. At the moment we are working on an update path for that. So for now you can not use old data. Instead you'll have to do your configuration from the start.
Please give it a try and feed us back some information. It would be highly appreciated.
Comment #5
Jan van Diepen commentedAdded the update path. There is one thing to remember. Nodereview does not enforce the tags to be unique. Yet they are used to identify results in votingapi. That is why we replace the actual tag in votingapi tables by the corresponding aid. For performance reasons we can only update when the tags are unique. So after checking the uniqueness of the tags we either update the votingapi tables or not. If the votingapi tables are not being updated you will be notified through an error message. Best way of doing the update is to make sure the tags are unique and rerun the 6105 update. The update has to be run, otherwise your results will not be showing in your earlier reviews.
Still, feedback will be greatly appreciated.
Comment #6
batje commentedThis should bump the issue up a bit. If you can, please review Jan's code.
Comment #7
Crell commentedA full module submitted in the issue queue is not at all useful. Please submit a patch, not a new module.
As noted in #1, one-review-per-user is a design decision. An option to do otherwise would still need to allow one-per-user as an option.
Comment #8
Ela commentedsubscribing
Comment #9
Jan van Diepen commentedI posted the requested patch on Allow multiple reviews per node. I wanted to start a new discussion thread so I created an new (duplicate) issue.
Comment #10
gausarts commentedSubscribing. Thanks
Comment #11
danielhonrade commentednew discussion on multiple reviews has been created to http://drupal.org/node/702126