Hello, @paulmcrobb
This case usually occurs when conditions or formulas use:
1) Non-existent fields (for example, you created a field, added it to the formula, and then deleted this field without removing it from the formula)
2) In case of a conflict of conditions (one condition contradicts another)
3) When using 0 as a field option.
For a more accurate analysis, could you please send us a calculator file and we will check this case on local servers.
Best regards.
Of course, thank you so much for your attention.
Cannot upload exported file here, what email address should I send it to?
Hi, @paulmcrobb
The calculator is exported as a text file. You can save this file (usually they weigh no more than a 1mb), for example, in Google Drive or any other file-sharing service, and send us a link from where we will extract this file.
Best regards.
Ah, thank you, done this now, please find below the link:
Link to Text File
With reference to your points that typically cause this type of error:
1) Non-existent fields (for example, you created a field, added it to the formula, and then deleted this field without removing it from the formula)
This is not the case, the calculator was in fact working before the last update elsewhere on my site.
2) In case of a conflict of conditions (one condition contradicts another)
There are no contradictions, just very simple add up fields.
3) When using 0 as a field option.
All of the sliders offer the option to select zero but not are st there by default. It breaks on the sliders before I can move them to zero anyway.
Thanks for all your help here.
Paul
Hi, @paulmcrobb
We are engaged in the process of debugging and studying all possible variations of the initialization of such cases. This took a little longer than expected, we apologize and hope for your understanding. We will let you know about the success ASAP.
Best regards.
Hi again, @paulmcrobb
I have good news. Our development team has found the cause of this case and has already solved it! The fixed version has already been sent to the QA department to check all scenarios, and as soon as all the stages of testing are completed, we will release an update with a fix. We apologize for the inconvenience. (As a workaround, you can roll back the free version of the plugin to 3.1.10 since this version does not contain this issue. You can do this with the WPRollback plugin, but still, I would advise you to wait for the update.)
Best regards.
