Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi, just upgraded from 1.5 to 1.7, and I seem to be getting stuck on "Saving vote..." after the AJAX call. I have seen the problem with jQuery 1.7 and 1.8. The vote gets registered, but the widget no longer refreshes afterwards. in the console I see the following:
"event.returnValue is deprecated. Please use the standard event.preventDefault() instead."
It does not seem to be related to either:
https://drupal.org/node/1865510 or https://drupal.org/node/2232031 (occurs even without nginx)
or
https://drupal.org/node/1809340 (since this was reported fixed in 1.6)
Comment | File | Size | Author |
---|---|---|---|
#8 | rate_widget_id_class_mismatch.patch | 650 bytes | etiennechataignier |
#4 | rate-js-2266371.patch | 561 bytes | mpaler |
Comments
Comment #1
agapito78 CreditAttribution: agapito78 commentedHi,
Did you get any solution for this issue?
Thanks!
Comment #2
jOksanen CreditAttribution: jOksanen commentedHaving same issue.
Comment #3
mpaler CreditAttribution: mpaler commentedsubscribe
Comment #4
mpaler CreditAttribution: mpaler commentedTry this...
Comment #5
sgoelz CreditAttribution: sgoelz commentedThanks for the patch. That worked for me.
Comment #6
maximpodorov CreditAttribution: maximpodorov commentedThe patch works, but its format is not quite correct (extra directory names).
Comment #7
thomas1977 CreditAttribution: thomas1977 commented@ mpaler
Could your patch be committed to a dev release (for a full module download)? Thanks :-)
Just ran into this problem as well.
Best,
Thomas
Comment #8
etiennechataignier CreditAttribution: etiennechataignier commentedThe patch posted below is a workaround.
The real problem comes from the misuse of drupal_html_id() to build the DIV widget.
Attached is a patch which is better with rate logic.
Comment #9
newsec CreditAttribution: newsec commentedConfirm bug.
#8 solve problem.
Comment #10
newsec CreditAttribution: newsec commentedComment #11
thomas1977 CreditAttribution: thomas1977 commentedAny news on a new release that fixes the issue (prob based on #8)?
Comment #12
rpayanmThe #8 work for me perfect!
Comment #13
mr.alinaki CreditAttribution: mr.alinaki commentedMet same problem yesterday. Patch from #8 worked for me.