Form submission error

Hi @optimus1k

Hope you are doing fine.

I checked a similar setup on my lab site and it seems to be a bug in the plugin. It has been reported and it’s exactly as you say – if the form is filled-in correctly from the start, payment will work but if there are validation errors, payment will not work fine and form needs to be reloaded and filled-in again.

The only workaround for this for now is to downgrade the plugin to version 1.23.3, please make sure you create a backup of the site before making any adjustment, in case you need to revert any changes. If downgrading is not possible, i t will be necessary to wait until the bug fix is released. The development team is already working on a solution already but I don’t have an ETA yet.

Kind regards,

Luis

Hi,

Thanks for your response. How do I downgrade the plugin because I struggling to find the option for that.

Hi @optimus1k,

I hope you are doing well today!

You can download pervious versions of the plugin from the Advanced View section which you can see on https://www.ads-software.com/plugins/forminator/advanced/
Please scroll down to the “PREVIOUS VERSIONS” section and download the one required. Then you can upload it through your WordPress dashboard.

Kind regards,
Zafer

Hi,

Thanks for your response, I’m doing that now.

Hi,

After downgrading the plugin, is there a way to have my form imported back in?

Thanks

Hi again @optimus1k,

After downgrading the plugin, is there a way to have my form imported back in?

Normally, we don’t suggest importing forms created with the new version of the plugin to the older version which might create some issues due to incompatibility.

However, plugin interface will allow you to import your form and it will work normally unless you have not used any few feature (such as new type of form field/payment gateway etc.)

Kind regards,
Zafer

Hi

Thanks so much, it worked perfectly.

Hi again @optimus1k,

We are happy to hear that the issue has been resolved and marking this thread accordingly.
Please let us know in case you need further help.

Kind regards,
Zafer

This issue may have been resolved regarding a workround, but the bug is still outstanding on the latest version, 1.25.0. The fix given here is to revert to an older version, which may have other outstanding bugs that need fixes. Can I suggest it should remain ‘unresolved’ until the proper fix is available. Please advise when the latest build has been properly fixed for this as it is a significant issue for us.

Thanks

Richard Adams (UK)

Hi @adamsrw,

I hope you are doing well today!

We totally understand your concern, however, since the bug was acknowledged, reported and tasked to be fixed, we are marking this as resolved.

Please note that our Forminator team work on multiple fixes at the same time so we can’t update every topic informing you that the issue was fixed but you will find it at the changelogs https://www.ads-software.com/plugins/forminator/#developers. Therefore, making this as resolved for now is totally fine. Note, marking the topic as resolved doesn’t close comments, if you have any further questions about this issue feel free to let us know.

Kind regards,
Zafer

Thank you for your reply, and I accept that you are following your established procedures regarding the status of issues raised. I can confirm that the recommended workround of reverting to version 1.23.3 has resolved the issue for us, so I guess we will have to stay on that version until we find out it has been fixed properly in a later build. I have worked in major software development projects in the past, and I would just say that we never flagged an issue as ‘resolved’ until the final update was available, we had an interim status of ‘Fix Available’ where a temporary workround was available, before a full product release. We also gave every issue an identification number, so that the Release Note/Changelog could identify exactly which issues were now cleared fully. Your version 1.24.6 Changelog includes a comment ‘fix: Issues with Form Submission errors’ but it is not the issue that we are discussing here. .
.
This plugin is an excellent addition to our website, and has functionality not available in other similar plugins, and we are reluctant to remove it and try and find another one with equivalent functionality. I am just disappointed that such a fundamental error was not present in an earlier build but has been introduced somewhere in the last few months.

How do I know when this issue is fixed? How long do I have to stay on a build that is 4 months old, when a later build might fix other issues that I might find (none identified as yet)?

• This reply was modified 1 year, 6 months ago by adamsrw.

@adamsrw please consider to open your own support topic.

this topic is resolved, so closing it