Problem: The client was experiencing an issue where strings translated using the
__('...');
function were not translating correctly for some languages, despite working previously. The issue was observed on a live site, while a local development site with outdated plugins did not exhibit the problem. Solution: We first confirmed that the client was using the gettext method for adding code inside their theme and translating strings via WPML > String Translation. We then suggested regenerating custom MO files from the WPML > Support > Troubleshooting page. Upon further investigation, we discovered that the client's theme was missing the text domain definition in the style.css file. After adding the required text domain and rescanning the theme's strings, we removed and re-translated a specific string to ensure WPML generated a fresh translation file, resolving the issue.
If this solution does not apply to your case, or if it seems outdated, we recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should the problem persist, please open a new support ticket.
Problem: The client reported a bug in WPML version 4.7.6 where an error occurs when clicking the '+' button on a page with custom fields. The error message displayed is: 'Uncaught TypeError: array_keys(): Argument #1 ($array) must be of type array.' This issue was linked to the handling of XML configurations for serialized custom fields. Solution: We identified that the XML file for the custom forms was misconfigured. Specifically, the 'optinText' field was expected to directly provide a text value for translation, but it was actually stored inside an array. To resolve this, we adjusted the XML configuration to correctly map the 'optinText' field as follows:
After modifying the XML and clearing any existing translation jobs for this form, the error was resolved, and the translation process proceeded without issues. We recommend the client to apply this XML configuration change and verify the results.
If this solution does not apply to your situation, or if it seems outdated, please check the related known issues and confirm that you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: You are encountering a PHP warning related to the WPML plugin, specifically an 'Undefined array key "REQUEST_METHOD"' error. This issue occurs in non-browser contexts such as WP-CLI commands, scheduled cron jobs, or when custom code triggers certain WPML functions outside of a normal page load. Solution: To address this issue temporarily, you can modify your custom code to set the 'REQUEST_METHOD' in the $_SERVER superglobal before WPML functions are called. Here is how you can do it:
<?php<br />$_SERVER['REQUEST_METHOD'] = 'GET';<br /><br />// ... rest of the script.
We have already reported this issue to our developers, and a fix will be included in future versions of the plugin.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are using Tutor LMS with WPML for a bilingual English and Swedish site, and you're facing issues with translating dashboard slugs like 'purchase_history', 'my-profile', 'enrolled-courses', etc. into Swedish. The page content loads correctly, but the page title displays 'Page Not Found' in Swedish, while English works fine. Additionally, after updating the Tutor LMS plugins, the sidebar menu in Swedish started working, but clicking the inner tabs redirects to a 404 page. Solution: We have identified that the issue with the page titles not displaying correctly in Swedish and the 404 errors when clicking on inner tabs are caused by your custom code. We recommend testing your site with a default theme, such as Hello Elementor, to confirm if the issue persists without the custom code. If the problem is resolved with the default theme, it indicates that the custom code is causing the translation and redirection issues. For further assistance, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins.
If this solution does not apply to your case or if it becomes outdated, we highly recommend opening a new support ticket. You can do so at WPML support forum.
The client is using WPML on a WordPress site and is facing issues where the translate icon 'pen' is disabled with a message 'You can only edit translations assigned to you' for custom role accounts. They need to enable the translate icon and resolve the translation assignment issue.
Solution:
First, ensure that all WPML plugins are up-to-date. For updating, backup the site and navigate to WP > Plugins > Add new > Commercial Tab..
To address the issue of the disabled translate icon, if a translation job is assigned to one translator, it cannot be accessed by another unless the assigned translator resigns from the job. For setting up local translators and language pairs, check How to Set Up Local Translators and Language Pairs.
To allow non-admin users (custom role) to manage translations, add the following code to your theme's functions.php file:
function wpml_custom_assign_capability() {
$users = get_users();
foreach ($users as $user) {
if (!in_array('subscriber', $user->roles) && !in_array('admin', $user->roles)) {
if (!user_can($user, 'wpml_manage_translation_management')) {
$user->add_cap('wpml_manage_translation_management');
}
}
}
}
add_action('init', 'wpml_custom_assign_capability');
Additionally, add this filter to allow users with the 'editor' role and the 'translate' capability to translate:
add_filter('wpml_user_can_translate', function ($user_can_translate, $user){
if (in_array('editor', (array) $user->roles, true) && current_user_can('translate')) {
return true;
}
return $user_can_translate;
}, 10, 2);
If issues persist, we recommend opening a new support ticket for further assistance. We also advise 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, please visit our support forum at WPML Support Forum.
Problem: El cliente desea tratar el idioma portugués como un WooCommerce separado en su sitio, pero enfrenta dificultades ya que WPML no soporta configuraciones de multitienda directamente y desea saber cómo podría separar este idioma manteniendo las traducciones. Solution: Nosotros, como equipo de soporte de WPML, aclaramos que no es posible lograr una configuración de multitienda directamente con WPML, ya que nuestros plugins solo permiten una configuración de URL de idiomas. Sugerimos la creación de una solución personalizada que cae fuera del alcance de nuestro servicio de soporte. Para duplicar el sitio y mantener las traducciones, recomendamos utilizar plugins como Duplicator o All-In-One WP Migration, teniendo en cuenta que las traducciones se almacenan en la base de datos del sitio y no se perderán al migrar. Además, proporcionamos enlaces para gestionar idiomas en WPML, como ocultar idiomas que no se utilizan (ocultar idiomas en portada) y cómo eliminar completamente un idioma del sitio (eliminar un idioma completamente). También se puede cambiar el idioma por defecto en la configuración de WPML siguiendo las mejores prácticas descritas en nuestro foro (mejores prácticas para cambiar el idioma por defecto).
Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos en problemas conocidos de WPML y asegurarte de que tienes instaladas las últimas versiones de los temas y plugins.
