Closed (fixed)
Project:
Vote Up/Down
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
12 Jan 2012 at 15:03 UTC
Updated:
24 Feb 2012 at 22:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
drewish commenteddb_query_rewrite() no longer exists. Let's modernize vud_user_votes(). Switched to DBTNG query, and returning a build array rather than a string.
Comment #3
drewish commentedWhoops didn't roll that against the right repo.
Comment #5
drewish commentedOkay for real this time...
Comment #6
marvil07 commented@drewish: Thanks for the effort here.
The real reason I was not really looking at this was #1360572: Roadmap for D7 of Vote up/down, and there vud_node would be kind of disappearing, and in fact that menu callback should no be on vud module, but instead on vud_node, since it's specific to it.
Sorry, but postponing until the two issues before 7.x-1.0-beta1 are ready.
Comment #7
Luna Vulpo commented@dresh your patch helped. Thanks.
Comment #8
marvil07 commentedI have removed this feature from D7.
This is the ind of things views can do it really better for us, I'm attaching an example view for reference. BTW this is about querying voting_api data, so not really vud specific, and if something specific is required voting_api views should really be enough to do it.
Comment #9
klonosSome modules include an example view in such cases. Users can simply enable the view and tweak it instead of having to build their own from scratch. This helps to provide a more out-of-the-box experience. Can we do that too?
Is it at least documented someplace (README.txt or documentation here in d.o)?