| ... |
... |
@@ -42,7 +42,7 @@ |
| 42 |
42 |
|
| 43 |
43 |
=== Session cookie settings === |
| 44 |
44 |
|
| 45 |
|
-{{figure image="system_general_session_cookie_de.png" clear="h3" width="600"}} |
|
45 |
+{{figure image="system_general_session_cookie_en.png" clear="h3" width="600"}} |
| 46 |
46 |
If possible, we recommend you make the settings for the session cookie as strict as possible and require HTTPS. |
| 47 |
47 |
{{/figure}} |
| 48 |
48 |
|
| ... |
... |
@@ -60,8 +60,15 @@ |
| 60 |
60 |
|
| 61 |
61 |
=== Generated protocol entries === |
| 62 |
62 |
|
| 63 |
|
-WIP |
|
63 |
+{{figure image="system_general_generated_protocol_entries_de.png" clear="h3" width="600"}} |
|
64 |
+ These settings let you enable or disable certain types of protocol entries. |
|
65 |
+{{/figure}} |
| 64 |
64 |
|
|
67 |
+; Add protocol entry when an automatic form submission by a bot was detected |
|
68 |
+: {{formcycle/}} tries to detect attempts by machines (bots) to submit forms automatically. When a bot was detected, the submission is blocked. If this option is enabled, a processing [[protocol entry>>doc:Formcycle.UserInterface.Protocol]] is created. |
|
69 |
+; Add protocol entry when attempting to submit a form with an invalid submit button |
|
70 |
+: You can add [[buttons>>doc:Formcycle.Designer.Form.FormElements.Button]] to a form that allows users to submit the form. Within the workflow, you can [[check whether a certain buttons was pressed>>doc:Formcycle.Designer.Workflow.Events.SubmitButton]] and run certain actions depending on which button was pressed. Starting with version 7, it is possible to validate whether the submit button actually existed in the form, which helps prevent form records from being manipulated. If this option is enabled, a processing [[protocol entry is created>>doc:Formcycle.UserInterface.Protocol]] when a form was submitted with an invalid submit button. |
|
71 |
+ |
| 65 |
65 |
== Limits == |
| 66 |
66 |
|
| 67 |
67 |
=== Form and file cache === |
