-
Hi Team,
Thank you for the alpha release! I’m testing the new Form Block in GenerateBlocks Pro 2.6 and running into a submission issue I wanted to report.
**Environment:**
– GenerateBlocks Pro 2.6 (alpha/RC)
– GenerateBlocks 2.3.0 alpha
– Test URL: https://www.lesvoz.org/2027/06/21/prueba-formulario/**Issue:**
When submitting the form (with all required fields filled in), I click Submit and the form always returns the generic error message : “Something went wrong, please check your details and try again”.**What I found in DevTools:**
– Network tab: No POST/submit request is ever sent. The only request that fires is a GET tosecurity?formId=8789&postId=8937, which returns status 200.
– Console: No JavaScript errors related to the form itself (only unrelated noise from Cloudflare Insights being blocked by my ad blocker/tracking protection, and a jQuery Migrate notice).It looks like the form’s client-side validation is failing silently before it ever attempts to send the actual submission, since no submit/process request appears in the Network tab at all.
**Spam Protection settings on this form:**
– Honeypot: ON
– Token freshness: ON
– Origin check: ON
– Turnstile: OFFI tested this both in preview mode and on a publicly scheduled post (same result in both cases), so it doesn’t seem to be preview-related.
Happy to provide more details, screenshots, or test further if helpful. Thanks for all the work on this release!
-
Hello,
Can you please update to the current RC versions currently available and try again? At the time of this post the latest RC versions are these:
If it still doesn’t work, can you go into the form edit mode, copy the block and paste it either here on in the private sections of the reply?
-
Hi team,
Following up on my previous report (sent ~4 days ago during the alpha/RC phase), I’ve now confirmed the root cause of the form submission error after updating to GenerateBlocks Pro 2.6.0 final.
**Environment:**
– GenerateBlocks Pro 2.6.0 (final release)
– GenerateBlocks 2.3.0
– WordPress 7.0
– Wordfence (firewall disabled), WP Fastest Cache, Cloudflare**Bug: Forms fail on scheduled (future-dated) posts**
When a Form Renderer block is placed inside a post with “Scheduled” status (future publish date), the security token endpoint returns a failure and the form never submits.
**Steps to reproduce:**
1. Create a post and set its publish date to a future date (status: Scheduled)
2. Place a Form Renderer block inside that post
3. Visit the post URL (accessible via direct URL even if not listed publicly)
4. Fill in all required fields and click Submit
5. Form returns the generic error: “Something went wrong, please check your details and try again”**What DevTools shows:**
– Network tab: only a GET request fires to:
/wp-json/generateblocks-pro/v1/forms/security?formId=XXXX&postId=XXXX
– That GET returns status 200 but with this JSON body:
{ "success": false, "message": "Unable to issue token." }
– No POST request is ever sent — the form fails before attempting submission
– No JavaScript errors in Console**Confirmed workaround:**
Placing the exact same form inside a published page works perfectly — the token is issued correctly and the form submits and delivers to email.**Conclusion:**
The security token endpoint appears to reject posts with “scheduled” (future) status, only accepting posts with “published” status. This makes it impossible to test forms on scheduled posts before they go live.**Additional note:**
The Spam Protection toggles (Honeypot, Token Freshness, Origin Check) appear locked/greayed out in the form editor — it’s not possible to disable them individually for testing purposes.Happy to provide additional details or run further tests. Thanks for the great work on this release!
-
Hi there,
Thanks for reaching out!
If you are referring to the post when it’s still in the scheduled state, then the form doesn’t work is expected and normal.
Based on my testing, when the post is published after the scheduled time, the form is ready to use and performs normally.
- You must be logged in to reply to this topic.