Show last authors
1 {{content/}}
2
3 HTML templates are used by [[actions>>doc:Formcycle.Designer.Workflow.Actions.WebHome]] of type [[response page>>doc:Formcycle.Designer.Workflow.Actions.HtmlResponsePage]] and can be displayed to the user after a form has been submitted.
4
5 Initially several system templates are available, which are created automatically when a new client is created. They cannot be deleted. See also [[error messages>>doc:Formcycle.SystemSettings.ErrorMessageTemplates]].
6
7 HTML system templates are mainly used for system messages such as informing the user about error during login etc. Their content can be changed as required. It is also possible to use placeholders within the response page, these can be [[form placeholders>>doc:Formcycle.UserInterface.Variables||anchor="sec_form_placeholder" target="_blank"]] or [[system placeholders>>doc:Formcycle.UserInterface.Variables||anchor="sec_system_placeholder_html" target="_blank"]] offer for example an attachment of a process as download.
8
9 {{figure float="right" image="1_en_TemplatesHTML.png" width="300"}}{{/figure}}
10
11 == Available templates ==
12
13 The following system templates are available.
14
15 * **Authentication failed**
16 The login was not successful.
17
18 * **Authorization failed**
19 The authorization was not successful.
20
21 * **Authorization required**
22 If the requested form is verified and the current user is not signed in, this text block will be displayed.
23
24 * **Bad Request**
25 A wrong data type or a faulty request was sent to the server.
26
27 * **BOT detected**
28 An attempt was made to send data illegal (e.g. trough automated bots).
29
30 * **Data not found**
31 The requested data set could not be found. This crops up, when you try to open an established process with the wrong process ID.
32
33 * **Double opt-in email sent**
34 The form data has been successfully submitted and an e-mail with the opt-in confirmation link will be sent.
35
36 * **Double opt-in verification failed**
37 The opt-in was not successful (e.g. because the opt-in link was not called within the specified time period).
38
39 * **Double opt-in verification successful**
40 The opt-in was successful.
41
42 * **File upload size exceeded**
43 The files sent by the user exceed the maximum allowed total size.
44
45 * **General Error**
46 Possible error message while opening or sending the form.
47
48 * **Information**
49 Contains the information of the system, which are gained via the button //information//.
50
51 * **Invalid Data**
52 The sent form data are invalid. Wrong form data were sent to the server.
53
54 * **Invalid double-POST**
55 The form data sent is invalid because it has already been sent to the server.
56
57 * **One time submission error**
58 The form data could not be submitted because the field defined as the unique identifier has the same value as in an already received form (e.g. the same e-mail address is used).
59
60 * **Participation password or login required**
61 To access the form, entering a password or logging in as a user is required.
62
63 * **Participation password required**
64 A password must be entered to access the form.
65
66 * **Resource not found**
67 The requested resources could not be found, possibly because of a wrong or incomplete link.
68
69 * **Resource offline**
70 The requested resource is not online (yet).
71
72 * **Sending Failed**
73 The form data could not be submitted.
74
75 * **Submission successful**
76 The form data was submitted successfully.
77
78 == Resetting templates ==
79
80 System templates can be reset to their initial content by clicking on the corresponding //Reset// button. All changes will be lost!
81
82 == Internationalization of HTML templates ==
83
84 {{figure float="right" image="2_en_InternationalizationHTML.png" width="300"}}
85 The //Source// button opens the editor. The contents of the templates for the individual languages are defined in separate elements with a lang attribute with the abbreviation of the language as value.
86 {{/figure}}
87
88 The system templates contain an English and a German version of the corresponding message as standard. Internationalization is achieved using //lang// attributes attached to certain HTML elements.
89
90 After selecting one of the existing end pages, you can view its structure by clicking on the //Source// button. In the editor window that opens you can see that the individual languages are always available in a separate {{code language="none"}}<div>{{/code}} element with the language as attribute (e.g. {{code language="none"}}<div lang="en">{{/code}}). More languages can be easily added by adding another {{code language="none"}}<div>{{/code}}- element with the corresponding language abbreviation in the //lang// attribute on the same level as the existing languages and then inserting the desired content for that language into it.
91
92 Note that the entire content of the template will be displayed if the language used to submit a form does not match any of the defined languages.
Copyright 2000-2022