Noch kein Mitglied? Hier registrieren, um das Forum zu nutzen, News einzureichen, zu kommentieren oder Seiten in der Galerie einzustellen.
Vanilla 1.1.2 Forum von Lussumo. Weitere Informationen: Dokumentation, Community.
und habe da ein paar Probleme folgende Phrasen kann ich nicht wirklich sinngemäß übersetzten. Ich weiß ungefähr was gemeint ist aber nicht 100%ig. Wäre toll wenn mir jemand helfen könnte:
This will use the form field called email to supply the email address to send the message to. Set to 1 to activate send direct. Defaults to 0
Prevents eform from sending emails e.g. no-reply@mydomain.com Set to 1 to disable emails. Defaults to 0
Sets the name of the form field to use as a selector to select a single email from the comma (,) delimited emails assigned the &toparameter. This selector field will act like a numeric index to select an email. It will start at 1 for the first email and ends at N for the last email in the list.
For example: &to =`sales@me.com,support@me.com,billing@me.com` &mailselector=`topic`
On the web form the topic fields is actually a dropdown menu. when the user selects a topic from the list the value 1,2 or 3 will be sent to eForm which will then be used to select one of the three emails assigned to the &toparameter. This email address will be the address used to send the email to.
This will use the form field called email to supply the email address to send the message to. Set to 1 to activate send direct. Defaults to 0
Prevents eform from sending emails e.g. no-reply@mydomain.com Set to 1 to disable emails. Defaults to 0
Sets the name of the form field to use as a selector to select a single email from the comma (,) delimited emails assigned the &toparameter. This selector field will act like a numeric index to select an email. It will start at 1 for the first email and ends at N for the last email in the list.
<select name="adressat">
<option value="1">Hans Müller</option>
<option value="2">Franz Meier</option>
<option value="3">Horst Schlämmer</option>
</select>
...&mailselector=`adressat` &to=`hans.mueller@domain.de,franz.meier@domain.de,horst.schlaemmer@domain.de`...
As eForm does not parse the complete form 1st time around you will have to have the same placeholders in the form template so the form can receive the values. So for example: [!eForm &sessionVars=`jobID` ... !]and <input type="hidden" value="[+jobID+]" />
As eForm does not parse the complete form 1st time around you will have to have the same placeholders in the form template so the form can receive the values. So for example: [!eForm &sessionVars=`jobID` ... !]and <input type="hidden" value="[+jobID+]" />
# &protectSubmit(optional) defaults to 1 (on)
Protects against submitting a form multiple times with the same data. Submitting the form becomes disabled after the first successful submit while the value from key form fields remains the same. This is achieved by setting (and comparing) a session variable with an md5 hash from these key fields. Which fields are compared depends on the value of &protectSubmit.Possible values are 0 (off), 1 (all 'required' fields are used) or you can set a comma separated list of field names. To ensure that the session variable works separatedly for different forms the session variable name is based on &formid ({formid}_hash).
# &submitLimit (optional) off (0) by default
Enforces a time limit (in minutes) between form submits. After the form has been submitted successfully it can not be submitted again for &submitLimit minutes irrespective of the form data. When used in combination with &protectSubmit submitLimit takes precedence, meaning that when the time limit has expired the form can be submitted again regardless of the setting of &protectSubmit (it will unset the session variable). As with &protectSubmit this parameter uses a session variable with a variable name based on &formid.
&protectSubmit(optional) defaults to 1 (on)
Protects against submitting a form multiple times with the same data. Submitting the form becomes disabled after the first successful submit while the value from key form fields remains the same. This is achieved by setting (and comparing) a session variable with an md5 hash from these key fields. Which fields are compared depends on the value of &protectSubmit.Possible values are 0 (off), 1 (all 'required' fields are used) or you can set a comma separated list of field names. To ensure that the session variable works separatedly for different forms the session variable name is based on &formid ({formid}_hash).
&submitLimit (optional) off (0) by default
Enforces a time limit (in minutes) between form submits. After the form has been submitted successfully it can not be submitted again for &submitLimit minutes irrespective of the form data. When used in combination with &protectSubmit submitLimit takes precedence, meaning that when the time limit has expired the form can be submitted again regardless of the setting of &protectSubmit (it will unset the session variable). As with &protectSubmit this parameter uses a session variable with a variable name based on &formid.
Sadly eForm will silently ignore a snippet that does not exist due to the way $modx->runSnippet handles snippet return values.
&snipFolder (new in 1.4.4) (optional)
For those that want to keep different versions of eForm active. You can now save all of eForm's files in a different directory and set the &snipFolder accordingly. You can for instance save version 1.4.4 in the 'assets/snippets/eform/1.4.4' folder and set &snipFolder=`eform/1.4.4`. The value of &snipFolder is added to the basic snippets folder 'assets/snippets/'.It should not include a closing slash (/)!
The default behaviour is handy for instance if you are storing a document id and want to be sure no one can tamper with the id. the field would look like this:
<input type="checkbox" name="myColors[]" value="Red" eform_options="Colors::1" />
Sadly eForm will silently ignore a snippet that does not exist due to the way $modx->runSnippet handles snippet return values.
&snipFolder (new in 1.4.4) (optional)
For those that want to keep different versions of eForm active. You can now save all of eForm's files in a different directory and set the &snipFolder accordingly. You can for instance save version 1.4.4 in the 'assets/snippets/eform/1.4.4' folder and set &snipFolder=`eform/1.4.4`. The value of &snipFolder is added to the basic snippets folder 'assets/snippets/'.It should not include a closing slash (/)!
The default behaviour is handy for instance if you are storing a document id and want to be sure no one can tamper with the id. the field would look like this:
Datentypen
Du kann folgende Datentypen setzen, die anderen werden automatisch gesetzt (Radio und Checkboxen welche sind, String für die Textbox und Listbox für Select)
Standard Validation: Alle Felder werden die benötigt werden, werden gecheckt (ob sie leer sind)
● string – Keine spezielle Validation außer das überprüft wird ob sie leer ist (wenn das Feld als required
gesetzt wird
● date – Überprüft ob es ein valides Datum ist (basiert auf der PHP Funktion strtotime())
● integer – Überprüft ob es sich um ein Nummer handelt
● float – Überprüft ob es sich um eine Float Zahl handelt.
● email – Überprüft ob es sich um eine E-Mail Adresse handelt (benutzt ein simples REGEX)
● file – (für Datei uploads) – Überprüft ob die max. Upload Größe überschritten worden ist, überprüft noch nicht um welchen Dateityp es sich handelt.
● html – Das selbe wie string nur wird am ende die \n zu einem <br /> Tag konvertiert
Bei den Listboxen, Checkboxen und Radio Felder musst du keinen Datentyp angeben, eForm erkennt dies automatisch. Es validiert die Werte laut der oberen Liste.
1 bis 14 von 14