Problem: You are working on a site under development and trying to translate custom Ninja Form fields using WPML, but you couldn't find any documentation on how to do this. Solution: We have resolved this issue in the latest version of the plugin. Please ensure that you update your plugins. After updating, use the following filter to set the configuration for Ninja Forms:
This code snippet should help you configure the translation settings for your custom fields in Ninja Forms.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still face issues, please open a new support ticket.
Problem: The client is working on a site under development and has successfully registered strings using the
wpml_register_string
hook. They need to insert translations for these strings programmatically as part of a migration involving hundreds of posts and multiple translations. However, the API documentation lacks information on how to do this. Solution: We recommend translating the xliff file that WPML uses for segmenting values and then re-inserting it. This approach is robust for custom coding scenarios. Alternatively, you can use the native editor to insert translated content and link it to the original content using our hooks. The wpml_set_element_language_details hook might be particularly useful in this case. For more detailed information, please refer to our extensive developer documentation:
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket at WPML Support Forum.
