WPIntell

Source evidence

Doesnt work with Calculation fields

Gravity Slider Fields · support · 2020-10-06T11:58:00+00:00

complaintsentiment
highseverity
1.0relevance
14replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 31 rows with source links

19.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

25 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
mikedistras unresolved
Im trying to create a calculator with multiple slider values, however it doesnt seem to work. Does this work with the gravity form calcution functions? I think it should be working with calculation fields. I wonder if there might be a conflict or if some specific configuration is blocking things from proper calculations. Anything show in your browser console? I tested further, and my apologies it does work with calculations, however i did help define where a potential issue is. It doesnt pass information to another input field if its conditional. Eg, a slider that only appears under certain conditions. EG: field-a: radio button with Yes/No option field-b: Slider field – conditional and shows if “field-a” is “yes” field-c: number input – calculation field containing “field-b” output – conditional to “field-a” being “yes”. — I hope that makes sense and happy to add screenshots if unable to recreate? Hi, I noticed there was an update to the plugin, but it didnt seem to fix this issue. Did you manage to recreate? I have this same problem Hi I’m currently having the exact same issue. All my forms stopped working as conditional logics are creating issues. Please provide a solution. Thank you. Any updates on this? I’ve had reports of an issue with a recent update this plugin made which has broken sliders that used conditional logic and calculations. I had created forms in 2019 with Gravity Forms and this Slider and they were working fine up until a recent update. Is there a plan to resolve this, or an easy way to roll back to your previous plugin? You should be able to download an older version of the plugin from his git repo: https://github.com/uamv/gravity-slider-fields Or downloading a previous version at the bottom of the plugin page: https://en-gb.wordpress.org/plugins/gravity-slider-fields/advanced/ Thank you so much for the fast reply. I will give that a shot. nice, thx for the suggestion because i am having the same problem with the conditional logic blocking the input of these sliders. Every visitor has to give their input two times and it is very frustrating so i hope this will work again with the older version The plugin still didn’t work with an older version, so I ended up purchasing a plugin called Gravity Forms Range Slider and it worked great. I’ve finally got to poking with this and I think the issue is that when hidden sliders are initially loaded, they aren’t being assigned a default value and aren’t given a value until the user interacts with them. For now, can you try explicitly defining a default value for the slider(s) on the Advanced tab when editing the field? This should then allow them to populate themselves (or any dependent calculation fields) properly. I’ll try to figure a way to best address this. Maybe an indicator that a field is in a NULL state. I know other users elsewhere have requested that sliders are not auto-assigned a default value, so as to require the user to explicitly set it. This reply was modified 5 years, 6 months ago by uamv . i tried the defining the default value under the advanced tab in cms but it just goes on to the next question (pagination) and in my summary i see it didn’t save the input the user but only the default value (zero in my case) which is even worse because the user gave 2 for an input. if i leave the default value empty the user always need to set his/hers choice two times for it to save so in either case it’s not working like it should. can you let us know if you are planning an update for this? otherwise i have to go search for another solution because this isn’t really user friendly for our visitors.. @thedan1984 is that the one from Hiilite on codecanyon? i was looking at that one but it hasn’t been updated in a while so in wonder if they are actively maintaining it or it either just works and no reason for updating? This reply was modified 5 years, 5 months ago by martijnlindeboom .

Comments

14 shown
uamv 2020-10-07T16:00:00+00:00

I think it should be working with calculation fields. I wonder if there might be a conflict or if some specific configuration is blocking things from proper calculations. Anything show in your browser console?

mikedistras 2020-10-07T16:27:00+00:00

I tested further, and my apologies it does work with calculations, however i did help define where a potential issue is. It doesnt pass information to another input field if its conditional. Eg, a slider that only appears under certain conditions. EG: field-a: radio button with Yes/No option field-b: Slider field – conditional and shows if “field-a” is “yes” field-c: number input – calculation field containing “field-b” output – conditional to “field-a” being “yes”. — I hope that makes sense and happy to add screenshots if unable to recreate?

mikedistras 2020-10-12T08:24:00+00:00

Hi, I noticed there was an update to the plugin, but it didnt seem to fix this issue. Did you manage to recreate?

Tygo 2020-10-15T05:23:00+00:00

I have this same problem

nbmtm 2020-10-18T01:17:00+00:00

Hi I’m currently having the exact same issue. All my forms stopped working as conditional logics are creating issues. Please provide a solution. Thank you.

Tygo 2020-10-22T05:59:00+00:00

Any updates on this?

Dan 2020-10-27T20:24:00+00:00

I’ve had reports of an issue with a recent update this plugin made which has broken sliders that used conditional logic and calculations. I had created forms in 2019 with Gravity Forms and this Slider and they were working fine up until a recent update. Is there a plan to resolve this, or an easy way to roll back to your previous plugin?

mikedistras 2020-10-28T13:06:00+00:00

You should be able to download an older version of the plugin from his git repo: https://github.com/uamv/gravity-slider-fields Or downloading a previous version at the bottom of the plugin page: https://en-gb.wordpress.org/plugins/gravity-slider-fields/advanced/

Dan 2020-10-28T13:07:00+00:00

Thank you so much for the fast reply. I will give that a shot.

martijnlindeboom 2020-11-20T07:23:00+00:00

nice, thx for the suggestion because i am having the same problem with the conditional logic blocking the input of these sliders. Every visitor has to give their input two times and it is very frustrating so i hope this will work again with the older version

Dan 2020-11-20T11:35:00+00:00

The plugin still didn’t work with an older version, so I ended up purchasing a plugin called Gravity Forms Range Slider and it worked great.

uamv 2020-11-20T14:19:00+00:00

I’ve finally got to poking with this and I think the issue is that when hidden sliders are initially loaded, they aren’t being assigned a default value and aren’t given a value until the user interacts with them. For now, can you try explicitly defining a default value for the slider(s) on the Advanced tab when editing the field? This should then allow them to populate themselves (or any dependent calculation fields) properly. I’ll try to figure a way to best address this. Maybe an indicator that a field is in a NULL state. I know other users elsewhere have requested that sliders are not auto-assigned a default value, so as to require the user to explicitly set it. This reply was modified 5 years, 6 months ago by uamv .

martijnlindeboom 2020-12-12T12:05:00+00:00

i tried the defining the default value under the advanced tab in cms but it just goes on to the next question (pagination) and in my summary i see it didn’t save the input the user but only the default value (zero in my case) which is even worse because the user gave 2 for an input. if i leave the default value empty the user always need to set his/hers choice two times for it to save so in either case it’s not working like it should. can you let us know if you are planning an update for this? otherwise i have to go search for another solution because this isn’t really user friendly for our visitors..

martijnlindeboom 2020-12-12T12:06:00+00:00

@thedan1984 is that the one from Hiilite on codecanyon? i was looking at that one but it hasn’t been updated in a while so in wonder if they are actively maintaining it or it either just works and no reason for updating? This reply was modified 5 years, 5 months ago by martijnlindeboom .