D7 port of Advanced Poll

We don't even have a clean D6 release.

any contributions?
any funds?

I am going to need a module similar to Advanced Poll for Drupal 7. I do not have much programming experience, but if nobody else plans on doing it, I'll give it a try myself within a few months (I first need to upgrade my site to Drupal 7).

I think it would be easier to start coding from scratch for the following reasons:

- The present version of Advanced Poll is not integrated very well with the standard node and fields system
- Many of the advanced features, such as different voting systems and write-in choices, I do not need them. They might be added later on through sub-modules.
- Advanced Poll dates back to Drupal 4.7, and Drupal 7 offers lots of new features, and I think it is better to focus on how to use them instead of focusing on how to adapt the old code. Maybe afterwards we can start looking at a possible upgrade path.

The main reason why I have been using Advanced Poll, is its possibility to create electoral lists for each poll.

However, an important feature that I am missing from version 6 of Advanced Poll is to give the creator of the poll the possibility to create the electoral list without having "administer polls" permission". And to have an easy way of mass-adding users to the electoral list. Presently, you can only do this by adding users from a specific role. I would like to include a way to use Views module for defining the electoral list. Something similar to the option of the CCK node reference field: "Advanced - Nodes that can be referenced (View)". Besides, some basic filtering options might be included on the poll editing form using available user fields, for example a taxonomy field indicating country of residence.

Lars, right, i think Advanced Poll has much too many relicts from 4.7, 5, ...
Starting from scratch is a good idea. However we should do this by working on a extensible/modular and clean concept.
The implementation should base on new D7 paradigms and please consider using clean base modules such as e.g. VotingAPI.
http://drupal.org/project/votingapi
For advanced user interaction - if really needed - consider jQuery UI.

If you start with a general core that is not focussing on specific polls, your module might have a big Drupal future. ;-)

Hi Miro, thanks a lot for the ideas. I agree with you. I will get back later when I have an outline. As I mentioned, it may take a few months. First I need to upgrade my site, and also get more familiar with the new APIs and Git.

While advanced poll has a lot of remnants from Drupal 4 and 5, the Decisions module was fully ported to Drupal 6 and has seen a few stable release on D6. If you do not want to start from scratch, it could make sense to start from decisions instead of advpoll.

At the very least, the algorithms in Decisions could be reused instead of being rewritten from scratch... I would love a module that would take the best of the two branches of the fork and make a kickass D7 release, and would gladly give git commit access on decisions to someone that would commit to such a module.

Good luck, whichever way you take!

Subscribing.

subscribe

This title naming is common.

There is also PollField
http://drupal.org/project/pollfield

Given Field API is D7 core, perhaps PollField could become the successor due to its integration as a field.

I've had great success using the decisions module and I think it most closely matches this modules feature set. +1 for working with the decisions module on a collaborative D7 solution.

I notice Decisions is not integrated into CCK as a field? Ouch, big -1 #92145: 2.0 - allow decisions to be attached to other node types

Subscribe.

subscribe

It is practical to be able to see which module an issue is about when seeing the title - in particular for "ports" between major versions, which is happening to almost every other module. Nice to be able to tell them apart.

DanielTheViking, I see no reason to do right that in the title...
All issue lists have the module name in a separate column.

We should NOT repeat the module name for all issues... Following your rule, ALL issues would need to containt the module name in its title. Ugly!

#16: No exactly. This is a good practise for only "Port Module X to D7" type of posts.
When any of us visit our dashboard here at d.o., it is not practical to have a number of active threads popping up in the activity lists under "Your posts" and "Your issues", if they are all using the same title without mentioning which module the port is about.

#17 - hear, hear! Yes, my issue list is full of posts that I have no idea what they are until I open them. I for one very much appreciate the module name in the title, most especially for modules needing a port to D7.

I suggest to add a ticket to change the output format.
The lists i use to work have all separate columns with the project names. I'm strongly againgst the redundancy and the display is even worse if that column is in the output. things start to wrap without any reason.

Can't follow your description.
Go to dashboard, check the issue widget, klick "more" on the bottom of it. And you'll have a perfect view on your issues.

(And i maintain a lot of issues and modules...)

Switching BACK! Sorry, can't agree...

Looks like http://drupal.org/project/pollfield will be the way forward
#1266336: Modernize Poll module
#61285: Remove poll module from core

subscribe

I hope to see it ported to D7 soon! subscribe...

Note there's some new D7 voting module on its way.
http://drupal.org/sandbox/sumsi/1074206
http://drupal.org/node/1073998

subscribe...

Good news, I've started work on the D7 build. Bad news, it may be a few weeks before I have a build ready to share with the community. I can promise that it will happen within 2 months as it is needed for a project at my workplace.

I'm using the recommended method of creating the content types as CCK from the start in the installation script and depending upon time and inclination once we have a stable build, I may look at back-porting this into 6. I am also going to make Ranking Poll its own sub-module so that people can choose to have one or both installed. My company finds that there are a few too many content types to manage sometimes so having a choice is nice.

We're also moving global configuration items such as cookie voting and voting mode into the node. More choice is always better.

In the meantime, thanks for your patience.

Very happy to hear that, I am sure D7 version will be much better. Thanks for this good news!

subscribe

I've just committed the first complete build of D7 Advanced Poll. It may take a few hours for the tar/zip files to be generated but I'll add the version to the list of available dev modules as soon as it becomes available.

One issue that I'm currently working on (discovered it last night while I was testing) is an issue with the JS in the ranking poll plugin. As it stands right now, if more than one ranking style poll is displaying on a page, only one will render properly. I'm fairly certain I know what's causing it and should have a fix today or tomorrow.

I'd be hugely appreciative of your feedback and suggestions. This is my first public module contribution and I'm sure there may be cases where I did not do something 'the Drupal way'.

Thanks everyone for your support and patience.
Michele

Thank you very much for the update.

Thank you mishwick. I started reporting issues on the D7 version. Hope to fix them soon because this module is too awesome not to have a stable release!

Sweet, thank you for helping with the bug reports! I'll get started on these over the weekend. I'm kinda puzzled about the language issue as I was careful to pass the language variable but I'm sure it's something I didn't understand about how this feature works. I definitely need the module to work in a multilingual environment!

It looks like the other issue has something to do with the way I'm rendering form elements. That's something that changed from 6 to 7 and I must have done it incorrectly. If anyone has any insights about either issue let me know.

Thank you!
Michele

Great, so follow-ups go into separate new issues for the 7.x branch.

Agreed, for D7 version I'd prefer to follow perisdr's approach so that there is a separate ticket for each issue - then I can roll a patch for testing, get verification and then roll it into the build after the ticket is closed.

There is an advpoll group that was used for discussion (http://groups.drupal.org/advanced-poll) - we could conceivably move general discussion there instead of in an issue.

General update - The issues that were cropping up with 1in8 were a bit more extensive than my initial patch. Since I had multiple fixes, rather than rolling lots of patches, I went ahead and created a new version. 7.x-2.x will address 1516442, 1516498, 1516448 as well as the Javascript issue I identified with multiple ranking polls not rendering properly when displayed on the same page.

It can take up to a day for a new tar/zip to be created. As soon as I know it's available I'll post it and update the related bugs.

Thanks all for your support and patience.
Michele