Thread Starter
frigid
(@frigid)
Update: The issue seems to be with calculated fields, which, if their dependent data fields were empty, would export as “0”, but now apparently don’t export at all.
Hi @frigid,
I hope you are doing well today!
Thank you for the nice words about our plugin. Please share an export of the form and the page link with us, so that we can check further.
You can find more info on how to export the form here : https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#import-export
After exporting, please share the code using a service such as https://pastebin.com which is free to use.
Please always make sure to use such service to share the code and don’t post the code here directly as it will most likely be unusable.
Kind regards,
Zafer
Thread Starter
frigid
(@frigid)
Thank you for the prompt reply Zafer @wpmudevsupport15!
The export is available here for a limited time. The issue seems to be with calculated fields {calculation-2} thru {calculation-5}. As I mentioned above, when the inputs for these calculations are blank, the fields appear not to export at all (not even as blank/empty), whereas in v1.18.2, they export as ‘0’.
Page link
Hi @frigid
I imported and checked the form but I admit I’m not quite sure how to test it.
You mentioned that “inputs for these calculations are blank” case but those calculation fields are never blank if they are visible – they are at 0 value initially until some choice is made in the select field that’s used for calculation.
On the other hand, those select fields are set as “required” so the form cannot be submitted with no selection made there and that gets me a bit confused if it comes to exact steps to replicate such submission (that I could then export to test export itself).
Can you give us example of what choices (aside from non-related fields like name etc) should we make in the related form fields to generate submission that will then be affected by export issue?
Also, before doing that, try a small “trick” on a form: in those calculation fields edit formulas to multiply select field by one. For example,
If in calculation-2, the calculation is set to just select-2, edit it to make it select-2*1 and so on.
Kind regards,
Adam
Thread Starter
frigid
(@frigid)
Hi Adam @wpmudev-support8,
Thank you for your reply. You note that “those calculation fields are never blank if they are visible”. However, they are generally not visible.
One of the first fields on the form lets the user select how many people (from 1 to 5) they wish to include in the registration. Fields for additional people are hidden. So for instance, if # of people = 1, then the fields for Person 2 to Person 5 are hidden. For each person, a subset of their fields are required if that person is included, so, for example, those fields for Person 2 would be visible (and required) only if # of people > 1.
I did try the trick of calculation-2 = select-2 * 1, and also tried calculation-2 = select-2 * 1 + 0, but the export still seems to omit this field, though, like I mentioned previously, in v1.18.2 this field exports as ‘0’ under the example conditions described above.
Hi @frigid,
I replicated the problem using your form, but when using a test form with the specified replication steps, the issue could not be reproduced.
I have brought this to the notice of our Second Level Support team to take a closer look at the issue and we’ll update you here once we have more feedback on this as soon as possible.
Kind Regards,
Nebu John
Thread Starter
frigid
(@frigid)
Hi Nebu John (@wpmudevsupport14) / WPMU Dev Support,
It’s been a few weeks, so I thought I’d check in. Any updates?
Thank you,
Frigid
Hi @frigid
I’m sorry for keeping you waiting but, I’m afraid, I don’t have much yet. It’s been tested more on our end and turned out to be a new/not-known-yet bug.
Unfortunately, it seems there’s no “patch” for it possible currently without fix directly in plugin core so the initial report (that my colleague submitted to our Second Level Support) has been converted to a full bug reports for our Forminator Team and they are investigating it.
The fix should be included directly in plugin in one of upcoming releases but I don’t have ETA yet.
Kind regards,
Adam
Thread Starter
frigid
(@frigid)
Thank you Adam @wpmudev-support8 – the update is appreciated. Happy to be able to provide feedback that can help your team improve their product, and glad to hear a fix is in the pipeline…we’ll keep an eye out for the fix in upcoming releases.
Thread Starter
frigid
(@frigid)
Confirming this remains unresolved in the latest version, 1.23.3, per end-user testing. Will continue to wait patiently. Thank you for keeping it on the update roadmap.
Hi @frigid,
Unfortunately, the developers are still working on a solution for this issue. Once they have a fix, we will update the plugin’s changelog with more information.
I am extremely sorry about the inconvenience caused by this.
Kind Regards,
Nebu John
Thread Starter
frigid
(@frigid)
No worries Nebu John – (except for this issue, of course) we really like this plugin and are thankful for all the work your team puts in to make it so useful!
Thread Starter
frigid
(@frigid)
Plugin version 1.24.1, released today, includes a whopping 62 listed fixes. I can confirm a fix for this issue is not one of them, but thank you for keeping it on the update roadmap.
Hi @frigid,
Unfortunately, a fix hasn’t been released yet. I can confirm our developers are already aware of the issue and we’ll be looking at remedying the issue asap. While we cannot provide a specific timeline yet for the fix, you can get updates on our progress by subscribing to our roadmap at https://wpmudev.com/roadmap/.
Once new versions are released, any pertinent changes will be described in the changelog, which you can find at:
https://wordpress.org/plugins/forminator/#developers
Seeing that this issue has been acknowledged and is being addressed, we’re marking this as resolved for now. However, if you have any queries, please don’t hesitate to ask. Thank you for your understanding.
Best Regards,
Nithin
Thread Starter
frigid
(@frigid)
Thank you for the response Nithin, as well as the additional information. I am encouraged to hear the developers are still aware of the issue and will be looking at a remedy shortly. In the meantime, I have reverted the status of this issue to “not resolved” so that it accurately reflects the current state.
-
This reply was modified 2 years, 9 months ago by
frigid.
