YES/NO element problem after upgrade to 3.9

[beatty_t]

I created a post for the ratings issue here: https://fabrikar.com/forums/index.p...-to-affect-yes-no-and-ratings-elements.50201/

 

[keianrad]

I have same problem after updating to 3.9. both yesno and radiobutton (group option) elements don't work. Is there any solution to fix it?

I am using warp 7 framework.

 

[sob_k]

Yes, read this:

Hmm, in which case it would most likely be this commit:

https://github.com/Fabrik/fabrik/commit/1cbe3de75a397b230cdcff1da26bce036186bcdc

Out of interest, try editing that file on your site, plugins/fabrik_element/radiobutton/radiobutton.js, and uncomment that line I commented out in the commit (remove the //). Then set "Debug JS" in the global Fabrik options (button top right of any top level backend Fabrik admin page), to force loading uncompressed JS, and see if that fixes it.

 

[keianrad]

didn't work for me.

Yes, read this:

 

[cheesegrits]

Is there a free Warp 7 template I can test with?

-- hugh

 

[keianrad]

https://yootheme.com/themes/master2

Is there a free Warp 7 template I can test with?

-- hugh

 

[keianrad]

friendly bump

 

[keianrad]

friendly bump

 

[lousyfool]

@keianrad:
In the template settings, "Bootstrap" section, have you checked "Disable Bootstrap"?
Make sure it's unchecked.

 

[keianrad]

No, it is unchecked.

@keianrad:
In the template settings, "Bootstrap" section, have you checked "Disable Bootstrap"?
Make sure it's unchecked.

 

[lousyfool]

No, it is unchecked.

Hmm, have a URL then? "Don't work" is a bit generic...

 

[keianrad]

Click here to see the website.

Thank you for your help.

Hmm, have a URL then? "Don't work" is a bit generic...

 

[lousyfool]

Please check your browser console: you have an "Unexpected token ," error in the form. Get rid of that first?

 

[lousyfool]

... Get rid of that first?

There you go... guess that did it!

 

[keianrad]

No, I just restored the backup to the previous version to fix the issue temperately. I will try to work on it on my local.

That error is related to a form autofill plugin.

There you go... guess that did it!