Any chance that there will be a Drupal 7 version of this module?

Comments

chipcleary’s picture

Thanks for the interest!

Yep, I am planning to create a D7 version. As a head up, it is likely to be a month or so before I get it out (maybe sooner but we'll see).

docco’s picture

Glad to hear that a D7 version is on it's way. I'll be on the lookout too!

chipcleary’s picture

FYI, there is a first cut at the D7 version here.

However, it requires two modules which are not currently released and must be built from patches:

Once those are released, I'll do some more testing and release this. So, you are free to try it out and all feedback welcome. At the same time, you may well also want to wait until some of the modules on which I depend are firmed up.

konon’s picture

I'm trying to create a site like stackexchange on Drupal 7. Without your module, the Answers are useless for me :)

chipcleary’s picture

Just a heads up ... the two modules noted in #3 above are still not released. So, I remain on hold here.

Michael-IDA’s picture

Hi Chip,

Can you add a statement at the top of the project page that this module is DOA for D7 due to dependencies? (e.g. please save those that are interested the frustration of trying to install until it might work.)

Thanks,
Sam

ridicter’s picture

I agree with Sam-Inet. I was under the impression I would have a working version since aup is inbeta, but it requires vud_node, which doesn't even exist. I downloaded the dev version of vote up/down for D7, but I ended up getting tons of errors.

drush en aup
The following extensions will be enabled: aup, voting_rules, userpoints_rules, userpoints, token, submitted_by, entity, entity_token, rules, php, best_answer
Do you really want to continue? (y/n): y
array_flip(): Can only flip STRING and INTEGER values! entity.inc:178 [warning]
array_flip(): Can only flip STRING and INTEGER values! entity.inc:354 [warning]
WD php: EntityMalformedException: Missing bundle property on entity of type [error]
taxonomy_term. in entity_extract_ids() (line 7409 of
/Applications/XAMPP/xamppfiles/htdocs/growlife_v3/includes/common.inc).
Cannot modify header information - headers already sent by (output started at [warning]
/Users/guadarichter/drush/includes/drush.inc:596) bootstrap.inc:1221
EntityMalformedException: Missing bundle property on entity of type taxonomy_term. in entity_extract_ids() (line 7409 of /Applications/XAMPP/xamppfiles/htdocs/growlife_v3/includes/common.inc).
Drush command terminated abnormally due to an unrecoverable error. [error]

chipcleary’s picture

Apologies for giving the wrong impression. I have taken the beta version down because it depends on other modules for which production versions are not yet ready.

FWIW, the d7 version of AUP does actually work (at least in my environment), however, as said above, it does require an unhappy process of installing a version-in-progress of vote up/down as described above.

vogelsang’s picture

What about using the drupal.org/project/rate module instead of Vote Up/Down? The rate module is in a stable D7 version.

I am not sure how much work that will go into changing from vote up to rate. I will start looking into the code of the answer modules today.

Edit: Nevermind. Achivements doesn't have integration with rules.

ildruido99’s picture

as just told, this module requires vud_node but it's impossible to find.. :(
any solutions?
thanks!

chipcleary’s picture

Please see comment #3 for the current state of vud_node.

giorgio79’s picture

+1 for Rate instead of Vote Up / Down, also Vote Up Down node wont happen:

"Posted by marvil07 on January 12, 2012 at 8:30pm
Status: needs work » postponed
As mentioned on comment 17, the real reason I am not applying this changes is because I want to move to "the field way", which is basically use vud_field as the base for all."

chipcleary’s picture

Status: Needs work » Fixed

Resolved ... by moving to the Rate module instead of Vote Up/Down. A D7 version is now available.

Thanks to @vogelsang and @giorgio79 for the suggestion.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.