Changes for page Datenbank-Authentifikator


From version 4.1
edited by MKO
on 20.07.2023, 19:52
Change comment: There is no comment for this version
To version 1.1
edited by MKO
on 01.06.2023, 14:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,7 @@
1 1  At least {{formcycle/}} version {{version major="7" minor="4" patch="0"/}} is required to use the database authenticator.
2 -
3 3  {{content/}}
4 4  
4 +
5 5  The paid //Database-Authentikator-Plugin// provides a possibility to perform a login to a form via a database query. Here, an HTML page incl. validators, error texts and the actual connection to the database can be specified. After sending the HTML page, the input of the login page is provided as a placeholder for the database query. There is also the possibility to allow the "login" nevertheless if a database record is not found. In this case, only the data from the login page is available in the form. Furthermore, it is possible to define a login lock, which temporarily blocks the login based on one of the input fields when multiple incorrect attempts are made.
6 6  
7 7  
... ... @@ -44,6 +44,7 @@
44 44  ; Database query
45 45  : Defines the actual database query to determine a record based on the login page input. These inputs are available via placeholders in the form of {{code language="none"}}[%<html-name-attribute>%]{{/code}}. As soon as a database row is returned by this query, the login is considered successful.
46 46  
47 +
47 47  ; Allow login without found database entry
48 48  : If this option is active, the login is also allowed without a found database entry. In this case, only the data of the login page are available as user attributes.
49 49  
... ... @@ -79,7 +79,7 @@
79 79  
80 80  === Validation ===
81 81  
82 -For client-side validation of inputs, the library [[Parsley.js>>https://parsleyjs.org]] is provided by default. This makes it possible to use attributes on the input fields, e.g. to require them to be filled in or to force a certain format. The submit button only gets activated after all input elements have been validated successfully. For a more detailed list of Parsley.js's capabilities, see the corresponding [[documentation>>https://parsleyjs.org/doc/index.html]].
83 +For client-side validation of inputs, the library [[Parsley.js>>https://parsleyjs.org]] is provided by default. This makes it possible to use attributes on the input fields, e.g. to require them to be filled in or to force a certain format. The validation is bound to the events "keydown" and "focusout" by default. Furthermore, the submit button only gets activated after all input elements have been validated successfully. For a more detailed list of Parsley.js's capabilities, see the corresponding [[documentation>>https://parsleyjs.org/doc/index.html]].
83 83  
84 84  === Further attributes ===
85 85  
... ... @@ -99,10 +99,9 @@
99 99  
100 100  ; data-show-type
101 101  : Allows to define an input type at a password field, which can be switched to by an eye symbol. This allows to switch to a readable representation of the input.
102 -:
103 -; data-custom-tooltip
104 -: Allows specifying the ID of an HTML container whose content is used as a tooltip for element with this attribute.
105 105  
104 +
105 +
106 106  === Styling (CSS) ===
107 107  
108 108  For the styling of the login page, the plugin already provides standard definitions for the layout as well as for input elements, the login button and errors. If required, these can be overwritten within the configuration of the login page in an HTML style tag. The following classes are also available within the HTML:
... ... @@ -119,6 +119,7 @@
119 119  ; errors
120 120  : Defines a DIV container for displaying errors.
121 121  
122 +
122 122  === Internationalization ===
123 123  
124 124  In the configuration of the page title, the page body as well as in the error messages the client-specific I18N variables can be used. These can be passed in the form of the placeholder {{code language="none"}}[%I18N.<value>%]{{/code}} and will be replaced according to the language in which the form is opened. Maintenance of these variables can be found [[here>>Formcycle.UserInterface.FilesAndTemplates.I18nVariables]].
... ... @@ -191,20 +191,6 @@
191 191  
192 192  == Version history ==
193 193  
194 -=== 1.1.0 ===
195 -
196 -* Standard validation events (Parsley) removed from the form. These can now be attached to the actual HTML element in a more flexible way.
197 -* Added Tippy.js for tooltips
198 -* Adding a mechanism that automatically generates tooltips for elements.
199 -* JavaScript callback for running script before the internal added (preInitLoginPage())
200 -* Minor adjustments to the internationalization mechanism
201 -* Minor CSS adjustments
202 -
203 -=== 1.0.1 ===
204 -
205 -* Modification to the transfer of the used form language within the authenticator
206 -* Support of client-specific placeholders within the configuration of the login page extended
207 -
208 208  === 1.0.0 ===
209 209  
210 210  * Initial release