At the moment, TranslatePress works with GiveWP, but there are several bugs/errors. This post is to ask for these bugs to be resolved.
Current bugs:
Bug 1. Auto-translation of the Donor Dashboard
This is possible and it actually works, but the URL calls for the wrong (base language) language parameter. GiveWP support noted: "The iframe URL in the Donor Dashboard still uses the default language attribute. You can check this by opening the Donor Dashboard iframe URL in a new window, viewing the code, and checking the lang parameter in the HTML tag."
I contacted TranslatePress about this and they said:
"We're only filtering the home_url() to add the language parameter, mainly because filtering the site_url() can have negative side-effects. The best way would be to use home_url() instead of site_url() if possible. The solution GiveWP provided could also work on a per project implementation (not something we'll add directly in TranslatePress)."
Status: No solution yet.
Bug 2. Two terms on the donation forms that don't get translated ("Choose amount" and "Add your details")
Status: No solution yet.
Bug 3. Editing of translations in iframes
Normally, after TranslatePress has auto-translated a text on our site, I can then manually edit the translations. Within the iframes (multi-step donations forms + dashboard), this is not possible at the moment, so we are stuck with the (often incorrect) auto-translations.
Status: No solution yet.
Bug 4. Next Gen 3.0 forms
The Next Gen forms are not auto-translating at all, nor can we edit the translations with TranslatePress manually (!). This makes the 3.0 forms unusable for us. Also see: https://feedback.givewp.com/next-gen/p/translatepress-compatibility
Status: No solution yet.
For GiveWP staff, see support requests #150016 and #136775