Ever since the last update, we started getting this error randomly when submitting posts from the front end:
Invalid Request. Please try again.
No errors are logged in any of my logs.
We are using the frontend shortcode on a custom post type page (the custom post type is a frontend user dashboard). It has been working well for a few months and we just started getting these errors recently since the last update.
From the new version 4.0.0, MB Frontend Submission uses table
wp_options to store form config and errors with the option key
mbfs_key. Please check the frontend form on your site if it has this hidden field https://monosnap.com/file/M01XVOw9JKsR1ZGxlOTPgPOtWuwQ5n
Or you can share your page URL, I will help you to check it.
Thank you. I am still having this issue.
I found the mbfs_key hidden field in my form, however I searched the wp_options table for it and for "mbfs_key" and couldn't find anything.
Do I have to manually enable logging for the form?
If a user logged in and submits a post, does the issue still happen?
This form is only visible to those that are logged in.
Please share your site credentials and details of the page via this contact form https://metabox.io/contact/, I will check the issue on your site.
User filling out the form has the Editor role. Can that be the reason why we are always getting this error?
Also, the form shortcode is on a "Private" page. Any ideas?
This issue happens when a user submits a form twice or more with Ajax enabled and it has been fixed in the new update. Please update MB extensions to the latest versions, clear all caches and check this issue again.
Thanks. We are using the latest version and not using ajax, and still getting the error. Could it be because the user submitting the form has the Editor role? (The error doesn't seem to happen with admin role)
Hello, we are experiencing the same problem.
I am not sure if this is relevant for the original poster of this ticket, but We found at least one way in which you can trigger this error.
The error does not occur when editing an existing post with the front-end-submission form.
The error also happens when you do this on two separate devices.
So when two devices "simultaneously" render the front-end-submission form, only the first one that gets submitted will work, the other one will receive the error.
Hope this helps in solving this issue.
However, if I should submit a new ticket for our specific problem please let me know.
@Leerpodium This is probably the cause of the issue, as we have multiple authors using the frontend form in different browsers.
Any solution to this @Long Nguyen?
Thanks to Tako, I'm able to produce the issue and escalate this to the development team. Hopefully, it will be fixed soon.
Thanks Peter and Tako.
Looking forward to a fix.
Just to let you know, that some of our clients are experiencing this issue a lot, because they work in a Metabox powered environment with classes of students together. Could you provide us with an update regarding this issue and an estimate if/when this will be resolved? With that information we can manage expectations of our clients better. Thanks!