Title: frigid's Replies | WordPress.org --- # frigid [ ](https://wordpress.org/support/users/frigid/) * [Profile](https://wordpress.org/support/users/frigid/) * [Topics Started](https://wordpress.org/support/users/frigid/topics/) * [Replies Created](https://wordpress.org/support/users/frigid/replies/) * [Reviews Written](https://wordpress.org/support/users/frigid/reviews/) * [Topics Replied To](https://wordpress.org/support/users/frigid/replied-to/) * [Engagements](https://wordpress.org/support/users/frigid/engagements/) * [Favorites](https://wordpress.org/support/users/frigid/favorites/) Search replies: ## Forum Replies Created Viewing 14 replies - 1 through 14 (of 14 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [2 years, 3 months ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/page/2/#post-17385149) * Our preliminary tests confirm the fix is effective with version 1.29.0. Thank you for your attentiveness to our concerns, and for your persistence in bringing this matter to a satisfactory closure. * Your great product just got better!! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [2 years, 5 months ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/page/2/#post-17271214) * Thank you for volunteering that update Zafer! It is welcome news, even with the caveat. Will keep fingers crossed that in short order this one will finally be put to rest. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [2 years, 6 months ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/page/2/#post-17198188) * FYI, issue still present in version 1.28.0 – no response required for now though, unless you have an ETA for a fix or require further information from our end. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [2 years, 7 months ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/page/2/#post-17130015) * I have conducted further testing with the latest Forminator version (1.27.0), and the problem seems to be with the name field. Namely, when a name field is in “multiple” mode and hidden, and the multiple sub-fields are empty, a single empty field is exported even though the headers reflect each of the multiple sub-fields. This causes subsequent data fields to be misaligned with respect to the headers. * Example, where first data row is a model with all fields non-empty, second data row is observed (incorrect) behavior with empty name fields, and third data row is expected (correct) behavior with empty name fields: * ```wp-block-code ID Name - First Name Name - Last Name Hobby 1 John Smith Coding 2 Coding 3 Coding ``` * A workaround might be to use multiple name fields in “single” mode rather than a single name field in “multiple” mode, but, since data should always correctly align with the headers, this is still a bug. - This reply was modified 2 years, 7 months ago by [frigid](https://wordpress.org/support/users/frigid/). - This reply was modified 2 years, 7 months ago by [frigid](https://wordpress.org/support/users/frigid/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [2 years, 9 months ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/page/2/#post-16945168) * You would not mark a bill as having been paid before it has been paid. Likewise, it is poor form to mark an issue as resolved before it is resolved. I would be happy to update this thread myself once I’ve confirmed resolution. However, until then, this issue should properly remain in “not resolved” status. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [2 years, 9 months ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/#post-16941467) * 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](https://wordpress.org/support/users/frigid/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [2 years, 11 months ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/#post-16795982) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [3 years, 1 month ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/#post-16657986) * 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! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [3 years, 1 month ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/#post-16653207) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [3 years, 2 months ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/#post-16495813) * Thank you Adam [@wpmudev-support8](https://wordpress.org/support/users/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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [3 years, 2 months ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/#post-16487914) * 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 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [3 years, 3 months ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/#post-16415246) * Hi Adam [@wpmudev-support8](https://wordpress.org/support/users/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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [3 years, 3 months ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/#post-16409227) * Thank you for the prompt reply Zafer [@wpmudevsupport15](https://wordpress.org/support/users/wpmudevsupport15/)! * The export is available [here](https://www.dropbox.com/s/0iwgdq7y56tgu9w/forminator-bfsc-member-registration-2022-23-form-export.txt?dl=0) 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](https://skatebing.org/club-ice/bfsc-membership-registration/) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Export issue in v1.22.1](https://wordpress.org/support/topic/export-issue-in-v1-22-1/) * Thread Starter [frigid](https://wordpress.org/support/users/frigid/) * (@frigid) * [3 years, 3 months ago](https://wordpress.org/support/topic/export-issue-in-v1-22-1/#post-16408314) * 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. Viewing 14 replies - 1 through 14 (of 14 total)