The plugin has built-in support for the use of “multilingual strings” which gives you the ability to define things like field titles in multiple languages.
Take a look at this article for the details: Localizing Participants Database
Thank you for your response! I am working through the WPML documentation, and I wonder if the best way to display the content of a particular record’s field is to create new fields for each of the different languages. Then, I should be able to create a conditional statement in the shortcode template to check for the current language and display the content from the appropriate field. The only piece I am stuck on is accessing the current language from the shortcode template.
WPML’s documentation says that I should use this filter to retrieve the current language – $my_current_lang = apply_filters( ‘wpml_current_language’, NULL ); But, I assume that I can’t call this filter from the PD shortcode template. Any thoughts on how I could access this information from the shortcode template?
Thank you again for your help!
You have full access to all WordPress functions in the templates, so getting that value should not be a problem.
Okay. I must just have an issue somewhere else. Thank you so much for your help! If I come up with a good solution, I’ll post it back here when I work it out.
Hi. I’m also trying to translate the form created with Participants Database with WPML. I read somewhere that back in 2017 Participants Database was not compatible with WPML. Is this still the case? I cannot figure out which strings I have to translate to change the text displayed in the form, for example.
Thanks for your help!
There are two types of strings that are translated: strings that are built into the plugin, and strings that are configured by the user.
Strings that are built into the plugin get their translated values from the translation files. So, if a string of that kind is not translated, you may need to edit the translation file to get the right translation. Many of the translation files included with Participants Database are incomplete.
Strings that you configure (such as field names) must use a “multilingual string” format that builds all the translations into a single string, which is then filtered according to the currently selected language.
You can find more information on that here:
Localizing Participants Database