Custom Work

Problem:
You are developing a site and want to redirect users for missing translations to a specific URL for each language instead of the homepage. The code you tried is not working.
Solution:
By default, WPML redirects missing translations to the homepage only. For redirecting to custom URLs per language, you might consider third-party services such as Permalink Manager Lite or Redirection. If you require further customization, we recommend using our Contractors service, which is a paid option. You can find more information here: WPML Contractors.

Please note that this solution might be irrelevant if it's outdated or not applicable to your 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 for further assistance.

Problem:
You are using Make.com to automate translations via the WordPress REST API and GPT API for custom localization, but the translated articles are not linking to their original English posts in WPML. The translations object is empty, and manual updates using the WPML API do not establish the connection.
Solution:
Currently, WPML does not fully support creating and linking translations directly through the REST API. You can specify the language using the '?lang=' parameter when creating a post, but additional steps are required to link translations. A custom solution involves:
1. Creating the first post in one language using a standard API POST call.
2. Creating the second post in another language using another API POST call.
3. Linking both posts using a custom endpoint. Here is a code example provided by another user that might help: https://gist.github.com/djoo/5518bcf4ccef93ab83d91787c41e929a
Additionally, you can utilize WPML hooks for more functionalities:

• https://wpml.org/wpml-hook/wpml_set_element_language_details/
• https://wpml.org/documentation/support/wpml-coding-api/wpml-hooks-reference/

Always ensure to have a backup when implementing custom code.

If this solution does not resolve your issue or seems outdated, we 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 further assistance is needed, please open a new support ticket at WPML support forum.

Problem:
You are experiencing issues with language switchers on your site. The PC header switcher does not allow switching back to Spanish, the mobile header switcher opens the flag's image instead of switching languages, and the footer switcher does not work correctly on tablets and phones.
Solution:
For the PC header switcher issue, we recommend adding the following custom CSS to resolve the overlapping issue caused by the "reservation" button container:

You can add this CSS via WP > Appearance > Customize > Additional CSS. For the tablet and phone switchers, please confirm the browser you are using as it appears to function correctly in Safari on iOS devices.

If this solution does not resolve your issues or seems outdated, or if it does not apply to your 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 further assistance is needed, please open a new support ticket at WPML support forum.

Problème : Vous rencontrez un problème avec un grand espace blanc sous le pied de page sur les pages de catégories après la mise à niveau vers WC 9.7.1, qui pourrait être causé par un grand nombre de sous-catégories. Ce problème disparaît lorsque WPML est désactivé.
Solution : Nous vous recommandons de remplacer le code CSS personnalisé par le suivant pour corriger le problème :

Veuillez vérifier si cela résout le problème sur votre site.

Si cette solution ne s'applique pas à votre cas ou semble obsolète, nous vous recommandons de vérifier les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.

Problem:

The client wants to add a floating flag icon in the backend of their website using the DIVI theme to switch languages, similar to the GTranslate feature. WPML does not have a built-in feature or hook to support this.

Solution:

We recommend implementing a CSS workaround to achieve a floating language switcher. You can add the following CSS code to keep the Dashboard language switcher floating:

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 this does not resolve your issue, please open a new support ticket at WPML support forum.

Problem:
The client is using ACF with an additional plugin called ACF Custom Database Tables to store ACF field values in separate tables, which WPML does not automatically recognize. The client needs to know which WPML hooks or filters to use to integrate these custom tables with WPML's Advanced Translation Editor and how to handle incoming translations for storage in these custom tables.
Solution:
Unfortunately, WPML does not provide specific hooks for integrating custom database tables used by ACF Custom Database Tables. We recommend scanning ACF and its addons for new strings at WPML > Theme & Plugin Localization and then translating these strings at WPML > String Translation. If the fields are added to the wp_options table, they can be translated using WPML String Translation, as detailed here: https://wpml.org/documentation/support/language-configuration-files/translate-strings-in-wp-options-table/. For further customization, additional development and compatibility coding might be necessary.

If this solution does not fully address your issue or 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. If further assistance is needed, please open a new support ticket at WPML support forum.