The client is using different forms for each language version of a page, embedded via shortcodes from the Spotler/Mailplus plugin. The Dutch version of the form is overriding key parameters in the form action, affecting its submission.
Solution:
We recommend the following steps to address the issue:
1. Ensure that each language version of the page uses the correct form shortcode. Add them manually if necessary. 2. If preserving URL arguments through WPML settings does not resolve the issue, consider using custom code to maintain the correct form settings upon submission. 3. As a backup, implement a JavaScript snippet to modify the form action after the page loads. 4. If the problem persists, consider switching to a different form plugin that is more compatible with WPML. For more information on compatible form plugins, visit https://wpml.org/plugin-functionality/form/.
If these solutions do not apply to your case, or if they seem outdated, please open a new support ticket. We also 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. For further assistance, you can contact us directly through our support forum at WPML support forum.
The client is using ACF Pro to set up a custom post type (CPT) called 'Case Studies' and needs to translate the URL slug for different languages, aiming for a structure like '/references/case-studies/{cpt-title}' for English.
Solution:
We recommend following these steps:
1) Navigate to WPML >> Settings >> Slug Translations. 2) Enable the option: 'Translate base slugs of custom post types and taxonomies (via WPML → Taxonomy translation)'. 3) Scroll down to the Post Types Translation section. 4) Click on 'Set different slugs in different languages'. 5) Enter the translated slug for each language and save the changes. 6) Go to Settings >> Permalinks and click 'Save Changes' (no need to modify anything). 7) Clear all types of caches (plugin, browser, server, CDN, etc.). For further guidance, refer to our documentation on translating page slugs and translating slugs for custom post type archives.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also 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. For further assistance, you can contact us directly through our support forum.
Problem: Estás intentando traducir la palabra 'Buscar' al inglés en las páginas de tu sitio web, pero no has podido hacerlo porque la implementación de esta palabra fue realizada a través de código personalizado que no está configurado para ser traducible. Solution: Necesitas contactar al autor del código personalizado y pedirle que registre el texto 'Buscar' para traducción. El autor puede consultar nuestra guía de hooks multilingües para obtener más información sobre cómo hacerlo: https://wpml.org/documentation/support/wpml-coding-api/wpml-hooks-reference/
Si esta solución no resuelve tu problema o si la información parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos verificar los problemas conocidos en https://wpml.org/known-issues/, confirmar que tienes instaladas las últimas versiones de los temas y plugins, y verificar la versión del arreglo permanente. Para más asistencia, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
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.