Closed (won't fix)
Project:
Advanced Poll
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Nov 2007 at 12:04 UTC
Updated:
3 Feb 2013 at 20:09 UTC
When using Mozilla i get an jquery-error saying "m has no property". I've tracked the problem to the line advpoll-vote.js:27
$(data.response).insertBefore(thisForm);
I don't know why so I solved it by creating a new node before adding it to the tree.
var rdiv = document.createElement('div');
$(rdiv).html(data.response);
$(rdiv).insertBefore(thisForm);
/Thomas
| Comment | File | Size | Author |
|---|---|---|---|
| advpoll-jquery.diff | 743 bytes | Nimstad |
Comments
Comment #1
anders.fajerson commentedWhich version of Mozilla are you using? I can't replicate this on Mozilla 1.7.2. Most likely there is a another module interfering with the JavaScript. Try turning all other contrib modules off.
Comment #2
Nimstad commented1) I can't turn everything of right now.
2) Three different Mozilla users had the same effect. I'm using 2.0.0.9. Not sure what the other have.
3) It worked when I tried the latest version of JQuery but that's highly unrecommended.
Comment #3
ChrisKennedy commentedYou get this error after voting?
Have you customized the theming of advpoll nodes at all?
Comment #4
Nimstad commentedYes. I get the error after i clicked vote and after the result is retrieved from the server in the ajax setup in advpoll-vote.js. The error is in jquery.js(). It could probably be due to a parsing error of the html node to be inserted (['response']).
Yes. I have themed the framing of the poll, but I havn't changed the actual poll nodes. Please note that the code works if I just creates a new div and insert the html-output to this node before inserting it to the tree.
Also, please note that the original code works if I upgrade jquery.js to a later version.
Comment #5
pomliane commentedThis version of Advanced Poll is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.
This issue has been automagically closed by a script.