• Resolved brihen

    (@brihen)


    I am using the free version of Calculated Fields Form.

    I have had a function that worked until about a week ago, since the submit button appeared it no longer works. I removed the submit button (as it was not needed & the function was supposed to dynamically evaluate) and now nothing happens even though I have all the following selected:

    Ticked – Enable autocompletion , Dynamically evaluate equations associated with calculated fields, evaluate the equations in the onchange & keyup events.

    The user selects a diameter & metal type. I use a drop down for the metal type to be selected and assign a number to each.

    I have the following formulas, I am wondering if you can’t do this calculation in the free version anymore, as my other forms with more basic calculations are working.

    PREC((41)/(fieldname6 POW (fieldname3,2)*fieldname5),2)

    PREC(((fieldname6* POW (fieldname3,2) /4)1fieldname5),5)

    PREC((PREC(((fieldname6* POW (fieldname3,2) /4)1fieldname5),8))*1000,4)

    where fieldname6 = Pi ; fieldname3 = diameter & fieldname5 = density.

    thanks

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author codepeople

    (@codepeople)

    Hello @brihen

    Could you please provide the link to the page that contains the form to check it in action? The editor in the WordPress forum is modifying the pieces of code in your entry.

    Best regards.

    Thread Starter brihen

    (@brihen)

    https://www.nockers.co.za/useful-tools/

    I notice that today the one is working that wasn’t working yesterday (Flat wire & strip), but Round wire is still not working.

    AWG conversion & Imperial conversion have always been working.

    Thanks

    Plugin Author codepeople

    (@codepeople)

    Hello @brihen

    Your equation in the fieldname5 field has a parser error. For example, in the equation:


    IF(fieldname8==1,8300, IF(fieldname8==2,7930, IF(fieldname8==3,7250, IF(fieldname8==4,7800, IF(fieldname8==5,8800, IF(fieldname8==6,8000, IF(fieldname8==7,8960, IF(fieldname8==8,8900, IF(fieldname8==9,8100,0))))))))

    The number of open parenthesis ( is different to the close parenthesis )

    Also, if you want to round the result with five decimal places only if the result is not an integer number, you must pass true as an extra PREC operation parameter:

    PREC(((fieldname6 * POW(fieldname3,2)/4)*1*fieldname5),5, true)

    Best regards.

    Thread Starter brihen

    (@brihen)

    Thank you very much, it is working now ??

    teleanu

    (@teleanu)

    I kinda have the same situation.
    I opened the form to uncheck Submit button (put it to display – NO) and after saving I got some display issues.

    I checked and the problem for me is in Calculated field.
    In original I have: https://i.imgur.com/k7xSpgG.png
    In the one that displayed error after unchecking Submit button, even if I add back the first 2 values from the list of 3, after I save it gets back and set as this: https://i.imgur.com/EDOKPBa.png

    If I put value<=3500 && value>1 like it was… why I get value1 after Save
    and for 2nd value…. I put value<=4250 && value>=3501 and I get value=3501 after Save

    the one working, cloned by me in the past but is with Submit button that appeared after the update:
    angler.ro/?cff-form=8

    the one that doesn’t work anymore but was on the website fine and running, but when removed the Submit button, it broke

    angler.ro/?cff-form=6

    form 6 should get fixed by accepting the values from first picture. values that existed and worked in that format from 2022 till today.

    Plugin Author codepeople

    (@codepeople)

    Hello @teleanu

    The issue is not caused by the submit button, but the equality operator.

    In JavaScript the equality operator is the double symbol “==”, the “=” is used for assignment.

    In the dependency rule (https://imgur.com/EDOKPBa), you entered value=3501 but the correct one is value==3501

    The first conditional rule has a syntax error as well. You removed the comparison operator. The correct is value>1

    Best regards.

    teleanu

    (@teleanu)

    Hello @codepeople

    Maybe I haven’t explained well.
    Before the update I used this formula:

    value<=3500 && value>1
    value<=4250 && value>=3501
    If value is Greater than or equal to 4251

    Exactly in this format and worked super well. In fact, it still works in the duplicate form that I have and for which I haven’t removed the submit button and saved it.

    I want to obtain exactly what I have with bold in the updated version.
    Don’t know how to explain it different.

    Form no. 8 uses exactly what I marked with bold in above comment angler.ro/?cff-form=8
    Form no. 6 messed everything after I removed Submit button and Saved the form.

    Plugin Author codepeople

    (@codepeople)

    Hello @teleanu

    I checked your Form 6 again and the first conditional rule in the calculated field has a parser error. You entered value1 but the correct one is value>1

    Best regards.

    teleanu

    (@teleanu)

    But I don’t want to be value>1
    I want it to be:

    value<=3500 && value>1

    and for 2nd value I want it to be:

    value<=4250 && value>=3501

    This is how I had it from day 1 when I installed the plugin in 2022.

    check form 8. that is what I want but without the submit button.
    But if I go in form 8 and deactivate submit button, the plugin will transform form 8 in the same thing as form 6.

    • This reply was modified 7 months ago by teleanu.
    Plugin Author codepeople

    (@codepeople)

    Hello @teleanu

    My apologies for the delay in responding to your question. We have detected the issue cause and released a plugin update to fix it. Please install the latest plugin update and reenter the conditional rules.

    Best regards.

    teleanu

    (@teleanu)

    @codepeople appreciate the fast fix. Working like a charm.
    Thank you!

    Plugin Author codepeople

    (@codepeople)

    Hello @teleanu

    Thank you very much for letting me know that everything is working fine.

    Best regards.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Dynamically evaluate not working since update’ is closed to new replies.