Skip to content
WP Provider Translate Academy

Translate contact forms and GiveWP donation forms

WP Provider Translate translates the contact forms and GiveWP donation forms on your site along with the rest of the page: labels, placeholders, buttons and help texts. The message a visitor sees after sending a form is translated too, and visitors stay in their language after they send it. What visitors type into a form is never sent for translation.

Contact forms

A form on your page is translated like the rest of the page. That includes:

  • Labels, help texts and buttons, such as “Your name” and “Send”.
  • Placeholders, the grey example text inside a field.
  • Choices in drop-down lists, checkboxes and radio buttons.

There is nothing to set up for this, whatever form plugin you use.

Messages after sending a form

Many form plugins show a message without reloading the page, such as “Thank you, your message has been sent” or “Please fill in this field”. WP Provider Translate translates these messages when they come back to a translated page, from the translations your site already has. Other values in the plugin’s answer, such as names and numbers the form needs to work, are left as they are.

A message that your site has never translated shows in the original language. Elementor Pro forms avoid this: their messages are translated together with the page, before anyone sends the form. See Elementor Pro forms.

Visitors stay in their language

When a form sends the visitor to another page afterwards, such as a “thank you” page, they arrive on that page in the language they were using. This works for contact forms, newsletter sign-ups and other forms, and for WooCommerce forms such as add to cart. See WooCommerce.

GiveWP

GiveWP donation pages are translated like any other page, so donors read your appeal in their language. What donors type, such as their name and address, is never sent for translation.

Payment providers tell GiveWP when a donation is paid, fails or renews by sending a notification to your site. GiveWP gets these notifications on a translated address exactly as on your main address, with no redirect, so donations and recurring donations are recorded in every language.

Payment notifications and form webhooks

Payment providers and some form services send information to your site in the background (often called webhooks or notifications). WP Provider Translate never redirects these, also when they arrive on a translated address (such as /de/…), on a page with a translated address, on a page that is not available in that language, or on a language with its own domain. A redirect would lose what was sent. Only ordinary page views are ever redirected.

One exception: with a domain per language, the WordPress login and wp-admin always move to your main domain. A login form sent on a language domain moves along with everything it contained, so the login still works.

Good to know

  • What visitors type stays private. Form entries, the page a visitor sees after sending a form, and anything shown only to logged-in users are never sent for translation. See Privacy and what is sent.
  • Changing a translation. Form labels and messages can be corrected like any other text. See Correct and review translations.

Troubleshooting

  • The message after sending a form is in the original language. Your site has no translation for that message yet. If it keeps happening, report it with WP Provider Translate → Report a problem, or ask your developer to add the message with the filter below.
  • After sending a form, the visitor lands on a page in the original language. Check that the form was sent from a translated page and that the page it leads to exists in that language. A page that is not available in a language leads to that language’s home page.
  • A payment or donation is not recorded. WP Provider Translate leaves payment notifications untouched. Check your payment provider’s notification address in its dashboard and in your plugin’s settings.
For developers
  • The wppt_page_texts filter adds texts a page shows only after a visitor acts, such as a form’s messages, so they are translated with the page, before anyone sees them.

Details in Developer filters and actions.