For more context, I tried making the Stripe field use a “Fixed” price, and it worked without issue. So it seems like it’s not reading the variable price calculation field for some reason.
When I submitted the form with a Fixed price, I noticed something interesting in the notification email:
Total Assessment/Coaching Costs (this is a hidden calculation field)
Error: Detected unknown or invalid string identifier: select.
Total Boarding Costs (this is a hidden calculation field)
Error: Missing calculable subterm. Are there empty brackets?
Total Cost ($ CAD) (this field is visible, is used for the Stripe payment, and adds the top two together)
Error: Detected unknown or invalid string identifier: select.
Update: I restored a backup to staging, and can confirm everything worked flawlessly on version 1.12.1.1.
So I have restored 1.12.1.1 on the live site, and updated the staging site to use 1.13.3. Please test on this staging site (and not the live site mentioned above): https://staging.wayoflifedogtraining.com/checkout/
-
This reply was modified 5 years, 8 months ago by
Jan Dembowski. Reason: Short link expanded
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
@sunnyt13 Do not use short links in these forums, that has been abused in the past and is expanded when found. I have expanded yours.
Hello @sunnyt13 ,
Could you export form and share it with us so we can check it closer? Please use code tag or https://pastebin.com/ service to share the export code.
kind regards,
Kasia
Hi @sunnyt13
Thank you for the form.
I was able to replicate the issue using your form on the 1.13.x version and I can confirm it works on 1.12.x
I’ve pinged the developers to take a closer look at this problem.
We will let you know when hearing back from the developers.
I suggest keeping the 1.12x on the live website until we find what is causing the trouble.
Best Regards
Patrick Freitas
Hi @sunnyt13
I hope you are doing well.
We received confirmation from developers, it is a confirmed bug and we are already working on a fix.
Kindly keep the live site on the previous version and keep the eyes on staging website updates. We are already working on an update for this issue.
Best Regards
Patrick Freitas
@wpmudev-support2 Great, thank you!
I did also notice a bug on 1.12.1, which I obviously can’t yet test on 1.13 to see if it still persists. I made a quick video for you:
Hi @sunnyt13,
Thanks for sharing the video. I tested it out on my system with your form export code shared in here:
https://pastebin.com/GKGNpgZp
And I wasn’t able to replicate the issue in version 1.12.1.1. Since the given form export didn’t have multi-steps, I manually added the page breaks and re-tested again but I was able to make the submission without any issue.
I do see the fields are different in the checkout section in your video when compared to the above give export.
Could you please double-check whether the above export code works without any issue on your side? If you are still noticing the similar issue, please do re-share a new export code so that we could further test and see what’s being missed.
Looking forward to your response. Have a nice day ahead.
Kind Regards,
Nithin
Hello there,
I am also having the same issue with the Stripe payment. I have noticed that the error only occurs when one of the fields in the calculation formula is empty.
I wanted to ask whether there is a way to downgrade forminator to 1.12.x so that I don’t encounter the bug?
Kind regards,
John
@wpmudevsupport11 Hey Nithin,
My apologies. I had made a couple small tweaks to the form since sharing the original export. Here’s the updated export: https://pastebin.com/zAUttFaT
All I did was add the pagination (which isn’t related to either of the bugs), and change the visibility condition on the field with the error to a different select field (this caused the bug).
Let me know if there’s anything else.
Btw @highwelleducation, you can download a previous version of the plugin on this page https://wordpress.org/plugins/forminator/advanced/ at the bottom.
@sunnyt13 Thank you so much. When I exported my original form to 1.12.x it still didn’t work but when I remade the form from scratch it worked perfectly.
Kind regards,
John
Hi @sunnyt13
I took a closer look at you form (the recently shared one) and I see that the payment amount is set with a calculation field that is based on other two calculation fields. This part is fine but then those two calculation fields are partially based on fields that are only conditionally visible.
This, unfortunately, might cause issues with calculations. It’s a bug that’s already known to developers and they are working on the fix. It’s not really directly related to Stripe but can affect it if the calculation result is wrong (e.g. 0 or some unexpected value that’s not “properly formatted” for Stripe needs).
I don’t have an ETA on the fix but our developers are already looking into it.
Kind regards,
Adam
Hello, is there any quick way to fix this?
I’ve already lost hundreds of bucks on PayPal because of this bug and my form is live!!! any fixes??
