Posted by braggadoshis on August 27, 2009 at 7:01pm
Jump to:
| Project: | Fivestar |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
This subject has gone on for two years, yet we have not received a solution to the multiaxis problem. I personally am halting production on a site until I can find out for sure what is going on with this feature. And I am talking about multi-axis rating live on the node, not by attaching a review to it. So in all honesty, how much does someone need to get paid to completely update fivestar to allow multi-axis rating? Or simply make another voting module with this capability. Joomla has a multi-axis addon, so I don't think it is impossible. There are two many users here who need that functionality, so lets just get it done.
Comments
#1
+1
#2
braggadoshis: I'd suggest hiring a developer to correct bugs in the 2.x version of the module. ezra-g is currently co-maintaining the module, it'd be great to fund efforts to get it completed. I don't currently have time to adequately develop this module, unless you can hire Lullabot to make time available for me to do the development. It doesn't matter how many people "want" a feature if they don't do anything about it.
#3
So who wants to step up to the plate on this? I'm willing to contribute funds to make it happen.
Nate(?) any estimates on time/budget needed for this so we have a ballpark target?
Cheers
#4
Learning from (hopefully) fixing #561622: Allow multiple votes per user per target I would like to add that the axis from fivestar_fields (http://drupal.org/node/457886) should be taken into account too.
@chlobe: What is your/the list of requirements?
#5
Fivestar is a building block. To have fully featured system would mean you hire someone to integrate different blocks together. And turning Fivestar into big monster that provides fully featured system would be against Drupal philosophy and would bring only problems. Simple example: some people use nodecomments for reviews, other use nodereference, third use module XYX. You can't simply integrate it together so it works for all people, and if you wanted, you wouldn't be able to make it with reasonable efforts. So we have here building block that although doesn't provide fully featured system out of the box, at the same time doesn't limit your possibilites - what you can do with it.
If you want to make such system, you would need to build additional module on top of Fivestar, so you don't hurt people that use Fivestar as building block. Also, I see nothing "critical" here, especially because feature requests can't be critical. "Critical" status is for bug reports.
I suggest to build your own system, and to provide meaningful bug reports and patches. Don't simply say "we don't have full system". You should say something like this: "Feature X doesn't work", "Feature Y is not flexible enoough", etc. That way you advance Fivestar as building block even more, for everyone's benefit.
#6
Apparently this version has it but I don't like the way the axis title is presented to the user and it has a few bugs: http://drupal.org/node/459660
#7
Why create a new module when http://drupal.org/node/459660 have multi-axis rating, although not recommended on a production site?
As a general rule, Drupal community don't particularly like having numerous modules doing the same thing. Also, the first thing required for us when asking for a new CVS account is to look for duplicates. So innovation is often stopped directly at the gate.
I believe that the Fivestar module should jump in the wagon and ship with a production-ready multi-axis rating system.
A good news would have been: http://drupal.org/project/criteria_rating, which was supposed to have multi-axis rating. But quicksketch [http://drupal.org/node/274805#comment-901420] opposed to it and requested the module developer not to create another "Fivestar" module. Incidentally, the Criteria Rating module is references in the Using Drupal book. :-(
So where are we now? Do we need to build a fund, a bounty, a chip-in? If so, how can we set it up properly. I would contribute as well as probably a few of my clients!
What is the best action plan?
#8
The best route of action is probably to directly fund ezra-g or chx. Chip-ins usually fall flat on their face. Everyone always expect other people to pay for things in the Drupal world. ezra-g works for for http://www.gvssolutions.com, financing some time through them might be the safest approach, because they may be able to clear Ezra's schedule and allow him to work on it. chx works for Now Public, though they're not a development firm, chx is currently working on the Drupal 7 port. Another option is doing the same thing through Lullabot http://www.lullabot.com/contact/work, though my time situation is pretty dire right now. Either way you should be anticipating somewhere in the mult-thousands dollar range, considering this will take 20-40 hours of work (or more, just a guess).
Completely alternatively, you can hire your own developer or develop it yourself, then simply file a patch to the queue. ezra-g or I will review it as time allows.
#9
quicksketch is right but I just wanted to correct that Growing Venture Solutions website is actually http://growingventuresolutions.com/contact . Thanks!
#10
Sorry 'bout that ezra. :-)
I'd love to see this move forward.
#11
I've contacted GVS and asked for their estimation of the price. I am a student and cannot afford the full price of such a project, but if there are enough people that will contribute some money in order to complete it, it might actually happen.
- Eli Baskin.
elibaskin@gmail.com
#12
@quicksketch, or you can simply make the alpha release mentioned on #6 appear on the project page.
It will drive more attention, increase testing and make more people contribute code.
Also, the CVS code that you get when following instruction on http://drupal.org/project/fivestar/cvs-instructions for 2.x is actually 1.19, not 2.x on #6. This could be fixed so people that want to contribute to 2.x will do it against CVS and not the [probably] outdated #6.
Asking Criteria Rating project to stop development at http://drupal.org/node/274805 lead us to a world without options for multiaxis. I'm asking him to make a formal first release at http://drupal.org/node/274805#comment-2662322
Thank you
#13
@aviram Inviting people to use alpha software tends to lead to a lot of corrupted installs. You CANNOT DOWNGRADE from 2.x back to 1.x after you've run the updates. Combined with 2.x being not entirely stable, I don't think encouraging use of 2.x at this point is a good idea.
I'm really sorry we ended up in this position, but I still think we'd be better off if we had developers collaborating instead of working on new projects. I'm very open to granting maintainership to more developers as long as they are capable and aren't going to break more things than they fix. I was begging for help months ago. See #506700: Fivestar module needs a co-maintainer (for 6.x).
#14
@quicksketch, I understand but I found 2.x very hidden and difficult to find in the releases and CVS.
My plan was to write and contribute the improvements I needed on 2.x, specially on the axis title part. I did most of it but got stuck in some points that were too much for my young Drupal development knowledge.
Thats why I still believe that making it more visible will drive the attention of contributors more talented than me. And I'm sure that if you call it 2.x-alpha or something, people will take the README file (where downgrade issues would be documented) more seriously than usual.
#15
After 3 years of development I've transferred ownership of Fivestar and ceased maintainership. ezra-g is now the owner of the Fivestar project. You guys stress me out. :P
I still encourage the merging of Fivestar and Criteria rating. Especially now that there is even less "resistance" than before. Adding multiaxis rating to Fivestar makes the functionality available to tens of thousands of existing installations, rather than requiring a module change.
#16
Thanks for all your work so far quicksketch.
#17
Subscribing, +1 for multiaxis rating!
greetings, Martijn
#18
Subscribe
#19
+1 for multiaxis rating, and a tie-in to fivestar extras to rate users on multiple axes.
#20
Not sure it this would help spawn some ideas here, but... http://drupal.org/node/499470#comment-3402940
#21
I have been playing around with the 2.x version of Fivestar to get multiple widgets to display on the same node for multiple users to vote but get it to work. Is there some sort of documentation on how to set up the 2.x's multiaxis?
EDIT: Sorry, found where to work with it. They have to be enabled first here - admin/content/node-type/node_type/fivestar. Look at the secondary tabs, totally missed it.
Then they can be called in the node.tpl.php files like so:
<?phpprint fivestar_widget_form($node, 'vote');
print fivestar_widget_form($node, 'professionalism');
print fivestar_widget_form($node, 'understanding');
?>
#22
#23
@Taxoman this issue is for the 6.x branch.
The 7.x branch already has pretty good multi-axis support. I'll be back-porting some of the work to the 6.x branch.
#24
I'm going to closed this issue. This seems more like a rant to me.
If there's an issue please either change the title to reflect the issue/and or feature request .
Thanks.
#25
#26
Hi all, the nodereview module provides a good basis for this. i needed similar functionality and modified the module to fit my needs, meaning the there are multi axes embedded on a page that are hard coded. unfortunately my example site isn't live on the web yet. i haven't had time to work on the node review module to make it properly work for the community... however, donations would help :)
that said, i do have a video tutorial on my site walking through how i created the version to fit my needs - http://www.torontowebsitedeveloper.com/drupal-video-tutorials/custom-eme.... you can also get the code from the video on the tutorial page (i'm out of town and dont have it on my laptop so i couldn't attach it here...)
pete
#27
Hi, still interested in the code, or if you got time to make a properly working for the community, even better!
Greetings, Martijn
#28
i'll try and work on it this weekend and post a patch with the changes to the node review module making it community ready.
pete
#29
Hi all,
just posted a patch to the nodereview module which enables embedded multi-access reviews. You can check it out here:
http://drupal.org/node/1141788#comment-4552604
The nodereview module is integrated with fivestar so it should achieve what you are looking for.
#30
This will be my last post here but for anyone interested, we've updated the node review module to provide this functionality. It'd be great to get some feedback on it.