ericH-23

Problem:
The client needed guidance on how to disable automatic translation for specific fields like the title and description in a job listing, and also inquired about the implications of setting a custom post type job_listing to "Translatable - use translation if available or fallback to default language" versus "Translatable - only show translated items".
Solution:
To exclude the post title from the translation editor, we recommended following the workaround provided in this forum post. However, this involves custom code, and if the client is not comfortable implementing it, we suggested contacting one of our certified partners, which can be found here: WPML certified partners.
Regarding the translation settings, using the fallback setting "Translatable - use translation if available or fallback to default language" will disable the automatic translation feature. This feature only works with the setting "Translatable - only show translated items", which also means that a job added in a secondary language won't appear in the job list when switching back to the default language, nor will the language switcher show other languages.

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 or visit our support forum.

Problem:
The client is trying to always retrieve the English slug names of a taxonomy for CSS purposes in different languages using the WPML plugin. They are using the

wpml_get_translated_slug

filter but are encountering issues where the slug is not consistently returned in English across different language settings.
Solution:
We advised the client to ensure they are using the correct parameters with the

wpml_get_translated_slug

filter. For retrieving the English version of a taxonomy slug, the code should look like this:

$tmpcss = apply_filters('wpml_get_translated_slug', 'job_listing_type', 'job_listing_type', 'en', 'taxonomy');

Additionally, we suggested checking the WPML > Settings > Taxonomy Translation to ensure that the English slug is correctly copied to other languages. If issues persist, we recommended testing the problem on a clean WordPress installation to isolate the issue. Further assistance with custom code, which is beyond WPML support scope, could be sought from certified WPML contractors, available here: https://wpml.org/contractors/

Please note that this solution might be outdated or not applicable to your specific case. 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. If the issue persists, please open a new support ticket at WPML support forum.

Problem:
The client was unable to find and translate the string "Group by:" in the Buddyboss group using WPML's string translation. Additionally, the client mentioned issues with the translation of a time-related string "vor 2 Monate (bearbeitet)" which should be "vor 2 Monaten (bearbeitet)", and the inability to translate the file upload feature in the timeline.

Solution:
1. For the "Group by:" string, we suggested that it might be coming from the Spacesengine plugin, which is not multilingual at the moment.
2. Regarding the file upload translation issue, we advised the client to wait for Buddyboss's feedback as they had already reached out for support.
3. For the time-related string, we acknowledged that living with "Monate" might be acceptable for the client.
4. We instructed the client to open a sandbox site and replicate the problem with only WPML and the Buddyboss plugin installed for further investigation.
5. Buddyboss mentioned that the "Uploading" is in a javascript file and cannot by translated as a string.

If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we recommend opening a new support ticket. We also highly recommend checking 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 need further assistance, please visit our support forum.