New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| Please note that they depend on %sPHP Session Extensions%s, which are enabled by default. | You have to log in to add a translation. | Details | |
Original untranslated
Please note that they depend on %sPHP Session Extensions%s, which are enabled by default.
Please note that they depend on %sPHP Session Extensions%s, which are enabled by default.
ReferencesYou have to log in to edit this translation. |
|||
| Use commas as separator. Do not use include the dots in the extension. | You have to log in to add a translation. | Details | |
Original untranslated
Use commas as separator. Do not use include the dots in the extension.
Use commas as separator. Do not use include the dots in the extension.
ReferencesYou have to log in to edit this translation. |
|||
| CC Message | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| Multi-Part Form | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| Auto Confirmation Message | You have to log in to add a translation. | Details | |
Original untranslated
Auto Confirmation Message
Auto Confirmation Message
ReferencesYou have to log in to edit this translation. |
|||
| Admin Message | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| Core Form | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| Form Messages | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| cformsII allows you to insert one or more customly designed contact forms, which can send the submission via email. | You have to log in to add a translation. | Details | |
Original untranslated
cformsII allows you to insert one or more customly designed contact forms, which can send the submission via email.
cformsII allows you to insert one or more customly designed contact forms, which can send the submission via email.
ReferencesYou have to log in to edit this translation. |
|||
| Accessing %1$s {custom variables} %2$s in the final form differs from how you would reference these in individual forms; e.g. %1$s{Email}%2$s would become %1$s{cf_form_Email}%2$s (for form 1) or %1$s{cf_formN_Email}%2$s (for form N). | You have to log in to add a translation. | Details | |
Original untranslated
Accessing %1$s {custom variables} %2$s in the final form differs from how you would reference these in individual forms; e.g. %1$s{Email}%2$s would become %1$s{cf_form_Email}%2$s (for form 1) or %1$s{cf_formN_Email}%2$s (for form N).
Accessing %1$s {custom variables} %2$s in the final form differs from how you would reference these in individual forms; e.g. %1$s{Email}%2$s would become %1$s{cf_form_Email}%2$s (for form 1) or %1$s{cf_formN_Email}%2$s (for form N).
ReferencesYou have to log in to edit this translation. |
|||
| If you are using multiple input fields with <strong>the same</strong> recorded field label, e.g: | You have to log in to add a translation. | Details | |
Original untranslated
If you are using multiple input fields with <strong>the same</strong> recorded field label, e.g:
If you are using multiple input fields with <strong>the same</strong> recorded field label, e.g:
ReferencesYou have to log in to edit this translation. |
|||
| All supported input fields are listed below, highlighting the expected formats for their associated Field Names. | You have to log in to add a translation. | Details | |
Original untranslated
All supported input fields are listed below, highlighting the expected formats for their associated Field Names.
All supported input fields are listed below, highlighting the expected formats for their associated Field Names.
ReferencesYou have to log in to edit this translation. |
|||
| Your form does not look like the preview image or your individual changes do not take effect? Check your global WP theme CSS! It may overwrite some or many cforms CSS declarations. | You have to log in to add a translation. | Details | |
Original untranslated
Your form does not look like the preview image or your individual changes do not take effect? Check your global WP theme CSS! It may overwrite some or many cforms CSS declarations.
Your form does not look like the preview image or your individual changes do not take effect? Check your global WP theme CSS! It may overwrite some or many cforms CSS declarations.
ReferencesYou have to log in to edit this translation. |
|||
| Please see the <a href="%s">Styling page</a> for theme selection. | You have to log in to add a translation. | Details | |
Original untranslated
Please see the <a href="%s">Styling page</a> for theme selection.
Please see the <a href="%s">Styling page</a> for theme selection.
ReferencesYou have to log in to edit this translation. |
|||
| Accessing %1$s {custom variables} %2$s in the final form differs from how you would reference these in individual forms; e.g. %1$s{Email}%2$s would become %1$s{cf_form_Email}%2$s (for form 1) or %1$s{cf_formN_Email}%2$s (for form N). | You have to log in to add a translation. | Details | |
Original untranslated
Accessing %1$s {custom variables} %2$s in the final form differs from how you would reference these in individual forms; e.g. %1$s{Email}%2$s would become %1$s{cf_form_Email}%2$s (for form 1) or %1$s{cf_formN_Email}%2$s (for form N).
Accessing %1$s {custom variables} %2$s in the final form differs from how you would reference these in individual forms; e.g. %1$s{Email}%2$s would become %1$s{cf_form_Email}%2$s (for form 1) or %1$s{cf_formN_Email}%2$s (for form N).
ReferencesYou have to log in to edit this translation. |
Export as