Stable for Drupal 7!

Hi,

Yes you can embed it to the node, there are still some field mystery issues on D7 which I can't pass through the last time I touched the D7 port, I hope anybody out there can help out. Unfortunately, I am still busy on other modules that are currently for our current projects. This is an exciting module, I hope I can touch on this again soon. Sorry for the delay.

daniel

Hello, any chance for a stable release soon ? Thanks and all the best.

I looked at the issues and there are no bug reports for 7.x. It would be great to post them so that they can be worked on and others can know what issues the module has to evalute if they can use it or not :-). We need this functionality for a site and might be able to provide fixes to bugs.

Hi cesarmiquel

I filled in 3 new bug reports for Drupal 7.x
I don't have time for now to fix them. If you do have time, don't hesitate to have a look!

I don't know how it was back then but I tested this module out a few days ago and don't even know where to start in regards to reporting issues because the whole thing is so unstable. I can list them one by one, but I think any good developer will have plenty to fix before I even try.

For anyone who doesn't need all the bells & whistles, there is a simpler version that's already quite stable & very actively maintained. I asked the maintainer if he can look into the two features of this module that I really need (Fivestar & Comments), so I'll end up using whichever module he decides to add them to.

Ok after having looked at every review module for Drupal 7 including Reply & Reviews, I realize that NodeReview has the best potential to become the most powerful Amazon-style review system with Fivestar & comment support.

It's unstable with errors, but core features do work. So I'll go through the issue queue and post what I think are the most urgent ones that if fixed can enable this module to finally have a proper release, at least as alpha. Thanks to everyone who have done a wonderful job porting it to D7 so far. I hope a sympathetic developer can give it a little bit more love that it really deserves.

Hey Jay,
that sounds great, I worked on the d6 version to get the embedding reviews going and would be willing to help out on the D7 version. There were a lot of issues in the initial port and I wasn't sure there was a lot of interest in the d7 version so never really got into it.

Yaworsk, I really want this module for my D7 startup, Collectiboard (which can be a perfect showcase for people to preview the module before downloading and using it themselves). The way it already works as an Amazon-style review system with Fivestar & comment support is exactly how I want it.

I'm not skilled enough to do this myself, but I'm a very good beta tester and willing to provide timely feedback if that helps (starting with h3rj4n's patches). I also write good content regarding Drupal (http://jayl.ee/blog/2012/10/22/how-to-use-launchrock-with-drupal is a good example) and want to eventually write a blog post for Drupal's ultimate review module, so I was hoping for at least an alpha release.

Awesome, sounds like a great way to get going on this. As patches are tested, confirmed, etc., I'll apply them and focus on some solutions myself so we can at least have a stable version.

I think it's almost there. The module itself is still working on my environment with all the patches attached ;) I haven't tested it with third party modules (fivestart for example).

There is still a lot to be done but that won't be in the way of a stable release. For example, all the db_query should be rewriten to db_select and some functions can be replaced by voting_api functions. Those wont mess up the release.

I guess at least the following patches should be fixed before continuing to a final release:

• #1992726: Notice errors when module isn't configured right.
• #1992736: One Review Per User
• #1387256: Reviews tab was showing for every content type
• #1580796: Make nodereview work with Display Suite
• #1514442: When saving a review with multiple axes, the first axe values override the other axes' values
• #1514448: Average Review Rating field is empty
• #1994708: Feedback on admin form submit
• #1994308: Limit the queries done by module

I default apply the following patches to make the module work (let's say an alpha release):

• #1992726: Notice errors when module isn't configured right.
• #1994708: Feedback on admin form submit
• #1387256: Reviews tab was showing for every content type
• #1580796: Make nodereview work with Display Suite

Thanks h3rj4n for coming back. It looks like I got some reviewing of multiple patches to do this weekend. I'll also go back to my notes and figure out what I think needs to be fixed before I can start using this module. Then I'll report back what I find.

I'm not a fan of how this module stores its data. It uses a content type to save the ID of the review, but the actual review is in a custom table. By using a content type to store the ID it requires that the title is set.

I think it's better that the nodereview defines it's own entity type to save all the things it needs. My guess is that the Drupal 7 branch is just a copy of the 6 branch with only some modifications to make it work for Drupal 7. It isn't optimised for Drupal 7. I want to rewrite the module but dunno if it's possible for my current project but it's definitely something that needs to be done.

Yeah but making the module based on entities would make it take like another year instead of say another month. Don't you think it's better to make it stable first, then start working on a 2.x branch with an upgrade path?

Another thing to consider is that there's something about entities that I don't think works with comments from Drupal core: https://drupal.org/node/1968062 (#5)

But there might be an alternative (Artesian Forum is also trying to be the new version of Advanced Forum that's based on entities): https://drupal.org/node/1129070

Had some time again and started looking at the code... didn't even know where to begin with the 7.x-1.x version so I started with a clean entities based version. I've committed it as 7.x-2.x-dev.

Right now, it has a node review entity type set up and node reviews are fieldable. Still needs a lot of work, specifically:

- need to link node review entities to nodes
- need to handle deleting node reviews when a node is deleted
- need to do the aggregation if there is a numeric rating field
- need to create a default listing of reviews or something on the node

There'll be a lot more to do but I think this is the best way to go about things. Entities are definitely where drupal is going and this way, there is already integration with views, rules, etc. right out of the box thanks to entity api.

I'll try to find time to beta test (I'm extremely busy at the moment) as I've been waiting forever on this module vs. a couple of alternatives (https://drupal.org/node/1968062, #5). One reminder I have for you is to try to keep the reviews commentable (mentioned in #14). Or maybe Field Comments might work with this module too (I haven't tested it out yet).

Every time I come back to this module, I keep scratching my head trying to figure out where I left off & where to start again (there are some interconnected bugs that keep throwing me off). But I'll try my best to come back and contribute as a good beta tester shortly.

yeah, I know that feeling... that's why I just went ahead and starting working on a new version which leverages entities, was too hard figuring out where the module was at / where I left off...

There's not a whole lot to review right now on the new dev 2.0 version as the node review type isn't connected with actual nodes yet...

Yaworsk, I just tested out 7.x-2.x-dev. It looks like it's in its very early stages, so I thought I'd give my 2 cents as to how I think this module should work in theory:

1) Title & Review fields that's commentable with basic Fivestar integration (meaning no axis because it's too complicated).
2) Optional: Let website administrator decide whether to moderate the submitted reviews or not.
3) Optional: Notify content author (and/or website owner) that a review has been left.
4) Optional: "X out of Y found this review helpful", meaning it would be awesome if the review itself can also be reviewable (Plus 1, Rate & Vote Up/Down are good candidates).

I really think this module should be an Amazon-style review system. Else we might as well just use Reviews, which does almost everything (including Fivestar integration) except support comments (and it's not based on entities either).

As for #14 regarding entities & comments & #16, here's what I found out about Field Comments:

1) It does work with 7.x-1.x-dev (but needless to mention, we don't need it because the reviews are already commentable).
2) It does NOT work with 7.x-2.x-dev, because it only works with content types (which version 1 is and version 2 is not). And since version 2 is based on entities, you might want to keep it as a content type if you're not sure you can keep the reviews commentable (since this module might take care of this for entities). Or if it's based on node entities, then I think the reviews will most likely still be commentable.

FYI, I really suck at grasping the concept of entities, so I hope what I wrote even makes sense. My point is, please keep the reviews commentable (no other alternative supports this).

@yaworsk: As you said in #15 you started a complete rewrite of the module, did you consider to not just review nodes but all entities? If so, renaming/moving the module to entity_review would be more descriptive.

Reviewing users for example would be very useful for communities. At least I am looking for a solution to review both, nodes and users with 1 to 5 stars and an optional statement. It would be great if it could simply attached to existing voting solutions. For example someone is using 5 stars voting for long time and want to extend voting it with an optional short comment. Would be nice if it will work by just enabling the module without the need to migrate past votes.

@osopolar - yup, i definitely had the same thought about both, reviewing any / all entities and renaming the module... I think we will probably go that route. The more I think about it, the more I think it might be best to add a dependency for the entityreference module to this and require users to add that as a field for any review. That way we could link our review entity to any entity...

Additionally, I've noticed that Review module was recently developed / released. I think it offers some very similar functionality and would make sense to link the development of both modules since each is so similar. We'll see what that developer thinks...

With regards to your second point, I'm not entirely sure I understand. I think there would definitely need to be some type of migration for past votes - we would need their values to become review entities otherwise our module would have no idea how to handle them... Maybe I'm misunderstanding what you are looking for?

Osopolar, #6 might already do what you're looking for: Reply -> https://drupal.org/node/1992660 (#1) -> http://inkfreakz.com/users/admin -> He's not using Fivestar, but judging from the fact that he's using another rating module (probably one of #18) to go with it, I think it can also be used with it.

My usecase is: Rate an entity (with one to five stars) and leave a verbal evaluation - like on ebay. I.E.: ***** (five stars) | This module rules. I thought I could use NodeReview for this purpose. I did not test the module yet, but I guess its not what I am looking for, as it creates a review (entity) and later other user can vote the review.

I'll check the Reviews module together with #2066787: Ratings Field.

I don't think Reviews is based on entities. Reply is, and I remember now that it does work with Fivestar: https://drupal.org/node/1968062 (#5)

P.S. Don't underestimate Reply just because a stable version is not out yet. It's stable as hell already, and the developer has been working on it constantly. It's just a matter of time before an alpha version gets released.

Ok, I stumbled upon a major discovery: Reply actually does pretty much everything we've all been talking about so far. But I realize why a stable version is not out yet, because I got a bunch of error messages when I tried to take full advantage of everything this amazing module can actually do. Here's a test example:

http://temp.jayl.ee/node/13 -> Reviews with ratings & comments (not from core, but Reply sort of has its own comment system) as well as whether they were helpful.
http://temp.jayl.ee/user/1 -> You can do the same for users!

All I needed were Reply, Fivestar & Rate (7.x-2.x-dev). Reply & Rate obviously need a lot of work, but the point is that the potential is definitely there. So yaworsk, I hope you can collaborate with Reply's developers. I'll be active as a beta tester wherever needs help to get a stable version out. I'm just happy that I finally made some real progress on trying to figure out how these modules should all work together.