Problem:
The client is trying to translate texts from the APIMO plugin on their website using WPML. Although all translations have been made, the modules do not appear in languages other than English. The client is concerned about whether this issue is due to a misconfiguration of WPML or the APIMO plugin's compatibility.
Solution:
We first suggested ensuring that the APIMO plugin follows the gettext approach for PHP file strings, which can be checked here: https://wpml.org/documentation/support/how-to-use-gettext/.
Upon further investigation, we identified that the shortcode used to display properties,
[apimo type="featured_home" property_selection_types="filter" order_by="published_at_low_to_high" no_of_posts="3" post_limit="3" grid="vertical" view="normal" desktop="3" mobile="1" tablet="1"]
, might not fetch translated properties. We recommended creating a new taxonomy, translating it, and assigning it to the properties. Then, using a new APIMO shortcode that displays properties from this translated taxonomy could potentially resolve the issue.
However, after attempting various solutions, it became clear that the APIMO shortcode does not support fetching translated properties. We advised the client to contact the plugin author for further assistance and suggested joining our GO Global program for compatibility collaboration: https://wpml.org/documentation/support/go-global-program/. Alternatively, using officially compatible plugins listed here might be beneficial: https://wpml.org/plugin/.
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 do not hesitate to open a new support ticket at WPML support forum.
