renderingOptions.honeypot.enable

Option path

TYPO3.CMS.Form.prototypes.<prototypeIdentifier>.formElementsDefinition.Form.renderingOptions.honeypot.enable

Data type

bool

Needed by

Frontend

Overwritable within form definition

Yes

form editor can write this property into the form definition (for prototype 'standard')

No

Mandatory

Yes

Default value (for prototype 'standard')
 1Form:
 2  renderingOptions:
 3    translation:
 4      translationFiles:
 5        10: 'EXT:form/Resources/Private/Language/locallang.xlf'
 6    templateRootPaths:
 7      10: 'EXT:form/Resources/Private/Frontend/Templates/'
 8    partialRootPaths:
 9      10: 'EXT:form/Resources/Private/Frontend/Partials/'
10    layoutRootPaths:
11      10: 'EXT:form/Resources/Private/Frontend/Layouts/'
12    addQueryString: false
13    argumentsToBeExcludedFromQueryString: {  }
14    additionalParams: {  }
15    controllerAction: perform
16    httpMethod: post
17    httpEnctype: multipart/form-data
18    _isCompositeFormElement: false
19    _isTopLevelFormElement: true
20    honeypot:
21      enable: true
22      formElementToUse: Honeypot
23    submitButtonLabel: Submit
24    skipUnknownElements: true
Description

Enable or disable the honeypot feature.

Attention

If you want to use a (static) site caching - for example EXT:staticfilecache - you should disable the automatic inclusion of the honeypot.

Within your form definition:

type: Form
identifier: fooForm
label: 'foo'
renderingOptions:
  honeypot:
    enable: false
renderables:
  ...

Within your form setup:

TYPO3:
  CMS:
    Form:
      prototypes:
        standard:
          formElementsDefinition:
            Form:
              renderingOptions:
                honeypot:
                  enable: false

See forge issue #83212 for more information.