As the module integrates with views (we can output widgets as views fields) it is likely to have several widgets bound with the same element on one page. Because returning ajax refreshes widgets by ID only the very first widget is being refreshed. The patch below fixes the issue using class rather than id to refresh widgets after voting. However it doesn't solve the problem with id uniqness.

CommentFileSizeAuthor
vote_up_down.patch1.25 KBadr_p

Comments

Status: Needs review » Needs work

The last submitted patch, vote_up_down.patch, failed testing.

marvil07’s picture

marvil07 commented
Version: 6.x-2.4 » 6.x-3.x-dev
Category: bug » feature
Status: Needs work » Postponed (maintainer needs more info)

Thanks for reporting.
IMHO showing the same content more than once on a page is not natural. IIRC that's why we use ids instead of classes to identify the voting widget.

Can you please elaborate why it would be important to support it?

BTW Since until now this would be a feature, and not a bug, I am moving it to 3.x

adr_p’s picture

adr_p commented

Thanks for replying.

In my case I have a page containing several quictabs 'boxes' and views within those tabs. To make a long story short they're simply listing the same content but it's sorted differently in each tab. So it is very likely to have one item displayed more than once on a single page (and this happens very often). Does that make sense to you? Thanks!

marvil07’s picture

marvil07 commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

Now I understand your use case, but I still think that it is not really natural to show the same content more than once.

What I would recommend you is to load those tabs through ajax, so there would be no problem. If you are concerned about speed between changing tabs, maybe caching those views output(a views feature) would be the solution(actually there are many ways to improve that).