0 is not a number error in Multi RadarGraph

Help Desk ›› Bugs and Troubleshooting ›› 0 is not a number error in Multi RadarGraph

Formidable Forms

April 16, 2025 08:19:49

Poncke

Topics: 1

Messages: 3

Hello,

I've been using Formidable Forms in combination with E2Pdf to generate PDFs based on form entries. This setup has worked flawlessly for several months. However, I recently noticed an issue with multi-radar graphs: they are no longer rendering correctly.

The error message I'm seeing is along the lines of:
"0 is not a number" or "3.5 is not a number" — the specific number varies, but the error remains consistent.

This issue only occurs when using field IDs to reference calculated values. When I input static numbers, the charts display as expected. To troubleshoot, I’ve already tried creating a new form and template from scratch but the error persists.

I’ve reached out to Formidable Forms support to check if there have been any changes in how calculated values are stored but it seems to not have changed.

Also i can display calculated field id's in the remainder of the template just fine. It's specifically the graph that's giving an error. Also the graphs in my previous templates that worked bugged out, without being changed.

I have tried the following setups:
Governance=> [frm-field-value field_id=967 user_id=current]|3
&
Governance=> [967]|3

----------------------------------------------------------

Any insights or assistance would be greatly appreciated.

Thank you,

April 16, 2025 09:57:35

E2Pdf

Topics: 7

Messages: 3614

Support

Hello,

With default settings, the correct usage should be:

Governance => [967]|3

* The spaces should be set correctly.

Could you please:

1. Copy and share here the value that is currently set in your Graph (the one that is expected to work), and attach a screenshot of the properties where the selected area is visible (as on the attached screenshot).

2. Try creating a temporary textarea, copy and set the value of the Graph (that is used) into it, and check the rendered output. Would it work if you set the same values manually?

3. Does the issue occur when you export data using 'E2Pdf' → 'Create PDF'?

We would really appreciate your feedback at WordPress.org!

April 16, 2025 10:22:58

Poncke

Topics: 1

Messages: 3

Hello,

Thank you for the response.
I downgraded both E2Pdf and Formiddable forms untill i found the one that was causing the issue.
Apparently Formiddable was causing in when installing their 6.18 version. Their 6.17.1 version works fine. Even when using the latest 1.28.01 E2Pdf version.

I checked their changelogs to figure it out but it was too vague so i'll be contacting their support for further assistance.
I'll be keeping version 6.17 for now.

I appreciate your time, and thanks.

April 16, 2025 10:31:57

E2Pdf

Topics: 7

Messages: 3614

Support

Thank you for the update. If you would have a time, please keep us updated.

We are currently attempting to replicate the issue using the latest version 6.20, but so far we have not been successful. If you’d like, you can send us a backup of the E2Pdf Template along with the corresponding Formidable Forms backup to [private] . This will help us verify whether the issue is on our side or if an update is needed to ensure compatibility.

We would really appreciate your feedback at WordPress.org!

April 16, 2025 10:35:48

E2Pdf

Topics: 7

Messages: 3614

Support

P.S. As an option to verify, you can still use the "textarea" in the E2Pdf Template to see how the values are rendered. To determine whether the issue is on our side, try using the same value in the "Success Message" or "Formidable Forms View" and check if there's any difference.

We would really appreciate your feedback at WordPress.org!

April 16, 2025 10:58:35

Poncke

Topics: 1

Messages: 3

Apparently the problem is because values need to be stored within number fields now instead of hidden or text fields. I tried changing this but to no avail. Instead of saying '4 is not a number' its now just ' is not a number' < without number.

Also i could see the number when i used it in the success message, and anywhere else in my template. It seems like formiddable automatically saves everything in hidden/text fields as a string, even if it is a calculation. So now you have to use number fields instead. But those dont work either when i went back to the most recent version of FF.

Also i send you the template/form i used to test this.