Hi,

First of all I want to thank you for this module. I use it since Drupal 6 and it rocks! :-)

Found one issue with rate widgets and I really don't know if it is a bug or a feature: if page contains two or more the same rate widgets (for example, on the node top and node bottom) and I rated a content using one of those widgets, only current widget gets new html code, all others stays unchanged. But this are the same widgets! And if I click on the another widget, I may get confusing results, because the state of the rate gets back without any visual confirmation (because it missed reload of widget html code).

I attached a patch that affects all same widgets on the page, and not only one that was clicked.

CommentFileSizeAuthor
#2 rate-replace-all-affected-widgets-2145197-2.patch1.16 KBSpleshka
#1 rate-replace-all-affected-widgets-2145197-1.patch874 bytesSpleshka
rate-replace-all-affected-widgets.patch907 bytesSpleshka
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Spleshka’s picture

Spleshka
he/him
Primary language English
Location UAE
CreditAttribution: Spleshka commented
FileSize
rate-replace-all-affected-widgets-2145197-1.patch874 bytes

Sorry, duplicated }); in a patch.
Attached a correct one.

Spleshka’s picture

Spleshka
he/him
Primary language English
Location UAE
CreditAttribution: Spleshka commented
FileSize
rate-replace-all-affected-widgets-2145197-2.patch1.16 KB

After a small research I figured out that we don't need to invoke Drupal.attachBehaviors() for all js function. We need only to add ajaxified behavior to a newly added rate links.

So new patch is attached.

Spleshka’s picture

Spleshka
he/him
Primary language English
Location UAE
CreditAttribution: Spleshka commented

Any progress in this issue?

Spleshka’s picture

Spleshka
he/him
Primary language English
Location UAE
CreditAttribution: Spleshka commented

I am affraid to ask, but does it make sense to review this issue, or we should just close it?

mdixondesigns’s picture

mdixondesigns CreditAttribution: mdixondesigns commented

Hi there, I'm having a very similar problem...

I have a view that is using fields to display nodes (let's call them playlists). Each playlist has two voting widgets (node top & node bottom as you've suggested above). If I vote using the "node top" rate widget first, everything works as expected and the two seem synced just fine. However, if I vote using the "node bottom" rate widget first, the vote seems to be registered, but it gets stuck on "Saving Vote..." and the "node top" does not update with it.

I tried applying the patch in #2, but it didn't resolve my issue.

Any thoughts?