0

When enabling Antibot on a Webform rendered through Guntenberg, I can not submit the form.

  1. Create a "Custom Webform" block type with a single entity reference field for Webforms.
  2. Create a block (of type "Custom Webform") that references a "Booking" webform
  3. Go to the setting of my "Basic Page" content type and allows users to include the webform block

However, when I enable Antibot on the webform and try saving the form, I get the error:

You have reached this page because you submitted a form that required JavaScript to be enabled on your browser. This protection is in place to attempt to prevent automated submissions made on forms. Please return to the page that you came from and enable JavaScript on your browser before attempting to submit the form again.

I've tried enabling Ajax with no success. I suspect this is a caching issue: when I edit the label of a input field, I have to flush all caches to see the changes reflected.

Currently, exploring lazy loading the block.

2
  • I suspect this is a caching issue: when I edit the label of a input field, I have to flush all caches to see the changes reflected. So you are missing two things, the antibot javascript library and the cache metadata of the webform. I suspect the render pipeline in your setup is loosing all metadata at some point. What if you use a webform block directly instead of a block type? What if you place the block in the block layout instead of Gutenberg? – 4k4 May 5 at 7:36
  • I've seen Gutenberg fixed a lot of issues but they never tagged a new release. Try the latest dev version. – 4k4 May 5 at 7:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.