lspr
Forum Replies Created
-
The forms are now functioning well, from my dashboard I can see the new version was released yesterday.
Hi Patrick,
Thank you for your suggestion, but we’ve already tested this solution. The issue specifically occurs in live mode, not test mode – which is probably why it worked in your test. This was previously identified by your team as a known bug that will be fixed in the upcoming release.
Our main concern right now is timing – when will the new version with this fix be released? This is affecting our business operations as clients cannot make card payments on our forms.
Could you please give us an estimated release date for the version that contains this fix?
Could you please let us know approximately when the new version will be released? This is quite urgent for us as we’re currently facing a difficult situation:
When we remove the visibility conditions as suggested, it creates a new problem – users who choose the invoice payment option can’t submit the form at all, even though they aren’t using the Stripe payment field. We need both payment options (invoice and credit card) to work properly for our clients.
Is there perhaps a temporary workaround we could use until the new version is released that would allow both payment methods to function?
find the link to the form export below:
https://justpaste.it/j5v44@joelo246 we are experiencing the same problem and it’s very concerning how unsupportive @wpmudevsupport13 has been these past few days.
They need to fix whatever bug it is ASAP
It’s been over 24 hours, and we still haven’t received a response or solution to the issue with our booking forms. This is very disappointing, as it’s costing us business.
After further troubleshooting on my end, I’ve noticed the problem started after the last plugin update on January 22nd. Before that, payments were being processed seamlessly through Stripe on the booking forms. This suggests the issue might be linked to changes introduced in that update.
We urgently need a resolution to restore functionality and avoid further business losses.
Yet to get any response on this!
This issue is directly affecting our ability to process bookings, which is impacting our business operations.
As mentioned earlier, the problem does not appear to be related to the Stripe Restricted key but may be linked to a recent update Stripe made on old form fields being deprecated and introducing new ones. We urgently need your team to investigate this from your end and provide a resolution or guidance as soon as possible.
Your prompt assistance in resolving this matter is highly appreciated.
Thank you for your response and for providing the link to reconnect Stripe. However, the issue we are experiencing is unrelated to the Stripe Restricted key integration. We implemented the Stripe Restricted key some time ago, and it has been functioning correctly without any issues since then.
Based on my investigation and communication with Stripe’s support team, it seems the issue may be related to a recent update involving deprecating a previous form field and introducing a new one. I am unsure if this is affecting Forminator’s functionality, but I believe it could be worth reviewing on your end.
The guide you provided has already been followed, and since the payment fields were working well until recently, I suspect the root cause may lie elsewhere. Could you please investigate further and confirm if the recent changes from Stripe are impacting the Forminator plugin?
I look forward to your feedback and any additional assistance you can provide.
That solved the problem, Thank you.
Hello Adam,
Thank you for your prompt response and for looking into this issue.
Regarding your questions:
- Recent changes: Yes, there were changes made to the booking forms recently. Between the end of June and the first week of July, I added some form fields for a 25% discount promotion we’re currently running. It’s worth noting that we’ve implemented similar discount fields in the past without disrupting the form’s appearance or functionality.
- https://pastebin.com/b6n7T1k0. I’ve done as you requested and this is the pastebin link. Kindly note that this is not the only booking form on our website with this issue, most of the booking forms are also like this.
Thank you
Hi Kasia,
No, it hasn’t been resolved, I have limited technical knowledge to run the SQL query, It would be helpful if you could fix it from your end.
I have sent several messages regarding this to WordPress support.
Kindly let me know if that is possible.Hello,
The above-mentioned tables are present and there are data in those tables.
For the server logs, I’m unable to access it to find any specific errors.Hello
Is it possible to have multiple forms that have some common features and others that have their own unique fields?
The forms have already been created. However, we want to apply some changes across all forms (rather than individually), whilst retaining some other fields which are specific to each form.