Are you going to fix this problems in version 3 of the plugin? I am using translatepress and really stuck with the donor-dashboard. TranslatePress cannot pickup any gettext strings nor the JS nor the pot, it also not working properly in the multistep donation form.

I spent days trying the code snippets php / java trick from https://wordpress.org/support/topic/issue-translating-givewp-plugin/ but is not working at all for me even I follow exactly the instructions.

I am not a programmer, my only hope is that you make this work as it should be, just picking up the pot file. Please please fix this in the new version!

Please add full compatibility with WPML (including JS strings)

hi all,

after working with GiveWP for a few months now, i think i've finally figured out how to properly translate things for a multilingual site. I share that here for all other users who have this + for the GiveWP devs, because some things still need to be fixed in the GiveWP code to make full translation possible.

There are basically 4 different types of translations:

Each requires a different translation approach.

.1. Your pages, forms, form categories and form tags

For this you can use popular translation plugins like Polylang and WPML. We use Polylang, because it is lighter and faster for the site, but it also has less options than WPML.

.2. Fixed strings in the core GiveWP plugin and free addons

There is this great initiative called Translate Wordpress. https://translate.wordpress.org It is a platform where volunteers work on central translations of strings in free Wordpress plugins. GiveWP core is in here, and so are a few free addons. You can see all GiveWP plugins and addons that are on here on this link (in this case for the Dutch language, but if the plugin is in there for Dutch, other languages can be added too): https://translate.wordpress.org/locale/nl/default/wp-plugins/?s=givewp

The GiveWP core translation area is here: https://translate.wordpress.org/locale/nl/default/wp-plugins/give/

In the translation areas for GiveWP core and the addons that are also in the list above, you can suggest translation with just a Wordpress.org login. It's very easy. Your suggested translations are then checked by translation admins and approved.

In principle, all FIXED strings (so strings that you as the site admin can NOT modify) should be in here. If they are not, something is going wrong at GiveWP's end, e.g. they might not have labelled a string as translatable. If that is the case, you should contact the GiveWP helpdesk about that and enter a bug report.

There are a few differences between the dev and stable branches, but they should sync regularly, and it is the stable branch that automatically syncs to your Wordpress installation.

Finally, if you want to CHANGE the translation for your own site, you can use the Loco Translate plugin to make a copy of the central translation file. Make sure to save this new file as "custom" (the central file will be stored as "system"). Don't copy over all the translations. The cool thing is, this way, the strings that you amend in the custom file overrule the translations in the system file. A great explanation of how to do is can be found here: https://localise.biz/wordpress/plugin/custom-translations

.3. Fixed strings in the premium GiveWP addons

Unfortunately, premium GiveWP addons are not on the Translate Wordpress platform. For these, you are dependent on the translation file(s) that the plugin developers provides you with for the addon. Usually, these are quite limited, if there are any, because plugin devs just don't have the resources to make all these translations.

The solution here is to make your own local translation file. This can be done again with the Loco Translate plugin. Again, choose "custom" as the file type because if a central translation every becomes available and you have stored it as "system", it will be overwritten. You can find all the plugins by going to Loco Translate in your WP backend and then clicking "Plugins" in the submenu.

So far so good, this is all possible with GiveWP. With the next item it becomes a bit trickier though.

.4. Strings that can be set by the WP site-admin in the WP backend, either for GiveWP core or for any of the addons

These strings cannot be centrally downloaded (because you as the admin set them) and Loco Translate does not offer translation for them. The solution here is to use the dynamic strings translation features in the translation plugin you use to translate pages and forms, e.g. Polylang or WPML. Their guidance URLs about such strings are here:

The main limitation here is that the plugin developer, GiveWP in this case, has to label and query these dynamic strings correctly, so that Polylang and WPML 'know' that these are dynamic strings that are translatable. This is currently not the case yet for many dynamic strings in GiveWP (almost all), at least not when you use Polylang (i don't know for WPML). This concerns any terms that can be defined in the WP backend for the site frontend, both for GiveWP core and for all the addons, and also for things like emails sent from the site. This is the one remaining major feature that GiveWP needs to implement to make their plugin 100% working for multi- or bilingual sites.

So far my insights from the past weeks/months. Please add if you have additions or think i got something wrong! Feel free to contact us also here: www.giveforgood.world/en/contact-us Happy to answer any questions or help.

best,

Rik

some other items for which it would be great if they were multilingual:

I use Translatepress.

Another item to make GiveWP multilingual: we have a dual-language site. Our main language is English, secondary Dutch. Currently, when one of our users requests an email access link for their Donor Dashboard, the link they get in the email takes them to the English-language Donor Dashboard, even if the link was requested on the Dutch Donor Dashboard page. There is currently no way to change this in GiveWP.

yes, desperately need the form to be translated by Polylang. as my reader only reads Chinese

also: being able to translate the URL slug of the individual form pages using the multi-step form

to add to this: displaying combined totals is the most important feature. Also missing is: