2 radio fields on same page with same values

[Stu]

Hi Bruce/Folks,

I've got a popup form with two radio fields on it, and each of those fields have the same set of values (see screen 1).

When you load up the page with firebug running, you get:

Code: [Select]

Error: cannot call methods on button prior to initialization; attempted to call method 'widget' (see screen 2).

Googling this led me here, https://forum.jquery.com/topic/uncaught-error-cannot-call-methods-on-button-prior-to-initialization-attempted-to-call-method-widget - the answer on this seems to be saying it's something that jquery can't handle.

Any ideas how I might be able to get around this?

EDIT: Am thinking I could try using different values in the second radio field, although that won't be ideal (I'll have to manually change them back on saving the record).

Stu

[attachment deleted by admin]

[Bruce]

Hi Stu,

I think I'd need to see an example to comment. The fact that the radios have the same _value_ is not the problem (there are endless radios with yes/no for example.)

The error you are seeing is usually because of something else wrong in the code - specifically some javascript that is out of order. So I suspect it has nothing to do with them being the same (you could change one to prove that theory) and a lot more to do with some script you are doing - or is being done for you - when the popup opens.

cheers
Bruce

[Stu]

Hi Bruce,

Apologies, my post wasn't clear .. The link talks about having the same "name" value being the problem.

I'll try and figure out more then if you think it's another script (is a generic file popup form from a browse, this particular nettalk system doesn't have any custom js files).

Stu

[Bruce]

I think names can be duplicated, as long as the id's are unique - but do they have the same name? That would seem somewhat counter-productive to me in this case....

cheers
Bruce

[Stu]

Hey Bruce,

Not sure - they are generic nettalk radio fields (ie, it's not me setting the name).

The field names that are using the two radio sets definitely have different names.

Stu

[Bruce]

I suspect we're rapidly approaching example time - I'm not sure I 100% understand what is going on.

cheers
Bruce

[Stu]

Yeah, it's a bit of a complicated one. I've just done up an example, and narrowed down what was going on.

Am going to change what I'm doing, because I think my own logic is bad - but here's what it was.

If you put a Radio field AND a string (or other field) on the form FROM THE SAME DATA FIELD, that's where you get issues.

IE, I want radio options, but then if the user clicks on "Custom" I want them to be able to enter their own value in that field.

This is where you get the javascript error.

I've attached the example.

** My guess is that at some stage the field name rather than the field equate is being used - but that's just a guess.

HOWEVER:

I don't like my logic to use the same field to put in a custom value. Am going to add another field that holds the custom value (with the original field being the "context").


[attachment deleted by admin]

[Bruce]

I agree - not a great pattern - but thanks for narrowing it down.

Cheers
Bruce