Problem: You have a custom plugin with a custom post type. When the site's current language is set to a non-default language, such as Dutch, and you create a custom post type, it is only associated with the current language. You tried using
'lang' => 'all'
in WP_Query parameters without success. The issue is that when performing a WP_Query for the custom post type, only records in the default language are shown, filtering out records in other languages. Solution: To include custom post types in all languages in your WP_Query, you need to use the
suppress_filters
argument in your query. Here's how you can modify your WP_Query: 1. Set
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 our support forum.
Problem: El cliente intenta publicar contenido en varios idiomas y enlazar traducciones usando la API desde Make.com con WPML, pero encuentra que WPML no tiene una API REST oficial para crear y enlazar traducciones directamente. Solution: Si estás experimentando este problema, te recomendamos: 1. Crear el contenido en el idioma principal usando la API REST estándar de WordPress. 2. Crear las traducciones como nuevos posts y relacionarlos con el post original utilizando un meta personalizado o desarrollando un endpoint personalizado en tu sitio que utilice las funciones internas de WPML para enlazar traducciones (por ejemplo,
wpml_add_translations
). Este tipo de integración requiere desarrollo personalizado, ya que WPML no ofrece directamente un mecanismo en la API REST para hacerlo automáticamente. Si necesitas asistencia adicional, puedes consultar con nuestros contratistas certificados que podrían ayudarte a desarrollar esta funcionalidad a medida.
Es posible que esta solución sea irrelevante si está desactualizada o no se aplica a tu caso. Te recomendamos revisar los problemas conocidos, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins. Si el problema persiste, te sugerimos abrir un nuevo ticket de soporte.
The client wants to show the default language in the /en/ subdirectory on their site. Although the page loading works with this structure, the internal links for the original language do not include the /en/ directory, which breaks the internal linking structure.
Solution:
We recommended the client to first resave the Language URL settings under WPML >> Languages >> Language URL format, then go to Settings >> Permalinks and resave those settings as well. After these steps, it's crucial to clear all types of caches to check if the issue persists.
If internal links still do not reflect the /en/ directory, we suggested editing the homepage in English and making minor content changes to see if the links update accordingly.
If this does not resolve the issue, using a plugin like Better Search Replace was advised as a last resort, with a strong recommendation to take a full site backup before attempting this.
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 problem persists, please do not hesitate to open a new support ticket for further assistance.
Problem: You need to set different labels and URLs for each language in the 'Return to the shop' snippet in a WooCommerce site using WPML. Solution: We recommend using one of the WPML hooks to dynamically change the URL based on the current language. You can use the
wpml_current_language
hook to detect the current language and then set the URL accordingly. Here is an example of how you can implement this:
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. If you still need assistance, please open a new support ticket.
Problem: The client is trying to use one menu for all languages on their site using WPML, but the main documentation method is not working. They are only translating one page into 40 different languages and want the same main English navigation buttons for all languages. Solution: 1. We suggested checking if all content linked by the menu is translated, as WPML should automatically handle menu translations once the linked content is translated. More details can be found here: Translating Menus Documentation. 2. If the automatic translation is not suitable, we provided a custom code snippet to force the use of the English menu across all languages. Add the following code to the site's functions.php file:
Replace 'Main Menu' with the actual menu name and ensure the theme location matches your theme’s menu location. 3. An alternative is to hardcode the menu in the header.php file, but this method lacks support for WordPress menu management features.
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. If further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: You are using the Xstore theme on your WordPress site and have uploaded custom fonts. While these fonts work perfectly on the original domain, they do not display correctly on the translated domain, reverting to default fonts like Times New Roman. This issue is also visible in the backend theme editor. Solution: We recommend checking the admin texts where theme option terms are typically saved. For instance, if your custom font is 'Jost', search for 'Jost' in the admin texts. Once found, add it to the string translation table. Ensure that the string for the font name is consistent across all languages. This approach should help in correctly displaying your custom fonts on the translated domains. If this solution does not resolve the 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 the problem persists, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.