Hi Jelle_S
Jquery update module will clash with our validation functionality in CCK User reference, Node reference field.
Case:
I created Poll CCK, in that i added a User reference field named as Author with Unlimited Number of Values option. When i create Poll content with Default value it will create Poll content. I adding some Five Authors in Author field it will show some Exception and also Poll content won't created. Following is the Exception i got, based on this exception i think Jquery update will cause this issue.
uncaught exception: [Exception... "Could not convert JavaScript argument arg 0 [nsIDOMDocumentFragment.appendChild]" nsresult: "0x80570009 (NS_ERROR_XPC_BAD_CONVERT_JS)" location: "JS frame :: http://localhost/sample/sites/all/modules/jquery_update/replace/jquery.m... :: anonymous :: line 12" data: no]
Can you please create and check CCK User reference field for your one of the CCK's. And adding some values to that field it won't allow you to create that content.
I attached the Issue screenshot. If you have time, please guide me on this.
Thanks & Regards
Sarav.
Comment | File | Size | Author |
---|---|---|---|
#5 | user_reference_field.jpg | 116.64 KB | sarav.din33 |
Issue.jpg | 45.89 KB | sarav.din33 |
Comments
Comment #1
Jelle_SCould you disable Clientside Validation but leave jQuery Update enabled and check if the error still occurs? Just to make sure this is a Clientside Validation bug and not a jQuery Update, User Reference or Node Reference bug.
Comment #2
sarav.din33 CreditAttribution: sarav.din33 commentedHi Jelle_S,
I just disabled the Clientside validation module and leave Jquery update enabled, and Create content using Poll CCK. Content got created and also no error occured. I think the error occured due to the Clientside validation module. Can you please guide me on this.
Thanks & Regards
Sarav.
Comment #3
attiks CreditAttribution: attiks commentedComment #4
Jelle_SOk, this appears not to be just a user reference problem. Any field with unlimited values (dynamically adding fields to the form) will cause this error. Once an extra field value is added (creating a new field in html code that was not there on page load) and the form is submitted this error appears. Chrome reported it as DOM Exception 8 (aka NOT_FOUND_ERR). I'm not sure what causes it and I'm not sure how (and how fast) I can fix this. But I will have a look in to it when I find the time.
Comment #5
sarav.din33 CreditAttribution: sarav.din33 commentedHi Jelle_S,
Thanks for you reply. I think Jquery update module will cause these errors. I attached a screenshot, it will help to understand the problem.
There are already some HTML is loaded for this Author field. Eventhough our validation won't work on this field. After adding some more values in the field also won't validate that field.
I think some clashes between Ahah field and Jquery update module. When ever you have time please look in to this issue.
Thanks & Regards
Sarav.
Comment #6
Jelle_SFixed in the latest dev. It was indeed a Clientside Validation error will test for 7.x too with the references module.
Comment #7
Jelle_SReferences now supported in 7.x as well
Comment #8
sarav.din33 CreditAttribution: sarav.din33 commentedHi Jelle_S,
Can you please tell me whether did you fix the bug in 6.x-1.x-dev or 7.x-1.x-dev. I tried 6.x-1.x-dev, today i downloaded and enabled it, still i got that error.
Thanks & Regards
Sarav.
Comment #9
Jelle_SI fixed it in both dev versions. It will take drupal.org at least 12 hours to update the development snapshots. So you can wait for that or get it directly form git:
Comment #10
sarav.din33 CreditAttribution: sarav.din33 commentedThanks a lot for your reply. I will try the latest dev version.
Thanks & Regards
Sarav.
Comment #11
sarav.din33 CreditAttribution: sarav.din33 commentedHi Jelle_S,
Thanks a lot for this fix. I just now download it and used it. All things are working fine.
Thanks & Regards
Sarav..
Comment #12
attiks CreditAttribution: attiks commented