Not WPML issue

Problem:
The client wanted to list only in-stock and visible products on the WooCommerce translations queue page.
Solution:
We explained that filtering in-stock and visible products is a WooCommerce configuration for the frontend and does not fall within the capabilities of the WPML plugins. The client managed to achieve the desired view by selecting only in-stock items under WooCommerce --> All Products. This solution is specific to WooCommerce settings and not a feature controlled by WPML.

If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. 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:
If you're experiencing a fatal error stating 'Cannot use object of type stdClass as array' in sitepress-multilingual-cms/classes/localization/class-wpml-download-localization.php, it might be due to a conflict with Duplicator Pro plugin. This occurs because the translations_api filter should return an array, but Duplicator Pro sometimes returns an object, causing WPML to treat it incorrectly.
Solution:
We recommend deactivating Duplicator Pro to see if the issue resolves. If it does, you can apply a temporary fix by modifying the code in wp-content/plugins/duplicator-pro/src/Utils/Translations.php. Replace the problematic line with the following code:

return $this->getTranslations($args['slug'], $this->apiUrl);

With:

$translations = $this->getTranslations($args['slug'], $this->apiUrl);<br />// Ensure we return an array, not an object (WordPress expects array)<br />if (is_object($translations) && isset($translations->{ $args['slug'] })) {<br />    return $translations->{ $args['slug'] };<br />}<br />return is_array($translations) ? $translations : [];

We also suggest reporting this issue to Duplicator Pro support for a permanent fix. If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket at WPML support forum.

Problem:
The client reported that a specific product was not appearing correctly on their website, even though other products were fixed. The issue persisted in both the translated and primary language versions of the product page.
Solution:
We first suggested deactivating the WPML plugin to determine if the issue was related to WPML or another plugin. After deactivation, the problem still occurred, indicating a potential conflict with another third-party plugin. We then recommended deleting the problematic product and recreating it from scratch. After recreating and retranslating the product, the client should check if the issue still persists.

If this solution does not resolve the 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 problems continue, please open a new support ticket at WPML support forum for further assistance.

Problema:
El cliente notó una diferencia en el precio de renovación de su suscripción a WPML, observando un aumento significativo comparado con el año anterior y tenía dudas sobre la correcta aplicación de los precios listados en la página de WPML.
Solución:
Primero, confirmamos el tipo de cuenta del cliente, que es Multilingual Agency, cuyo precio está listado como 199€ en nuestra página de precios. Luego, solicitamos al cliente que confirmara la cantidad exacta que se le había cobrado para verificar si correspondía con el precio actual. Además, aclaramos cualquier confusión y ofrecimos asistencia adicional para futuras consultas.

Si la solución proporcionada no resuelve tu problema o si la información parece desactualizada o inaplicable a tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más ayuda, visita nuestro foro de soporte.

Problem:
The client is experiencing a persistent 502 Bad Gateway error when editing their website with Elementor while WPML is active. Despite all plugins, themes, and WordPress core being updated, and various PHP versions (8.0 to 8.4) tested, the issue persists. The error disappears when WPML is deactivated.
Solution:
We recommend the following steps to diagnose and potentially resolve the issue:
1. **Increase PHP memory and execution time limits**: Adjust the

wp-config.php

file to increase the memory limit and execution time. This can help accommodate the resource demands of using Elementor with WPML.
2. **Enable WordPress debug mode and review logs**: Modify the

wp-config.php

to enable debugging and check the

debug.log

for specific error messages after reproducing the 502 error.
3. **Clear OPcache**: Clearing the PHP OPcache can help if old or corrupted cache files are causing issues, especially after changing PHP versions.
4. **Manually reinstall WPML**: Perform a clean reinstall of WPML to eliminate any potential corruption. Ensure to backup your site before proceeding.
5. **Conduct a plugin conflict test**: Deactivate all plugins except WPML and Elementor, and then reactivate them one by one to identify any conflicts.
If these steps do not resolve the issue, it may be due to a deeper compatibility problem between WPML, Elementor, and recent PHP versions, particularly concerning the handling of nullable types. In such cases, further detailed investigation by our support team may be necessary. 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 the problem persists, please open a new support ticket for personalized assistance at WPML support forum.

Problema:
El cliente experimentaba problemas con los enlaces del menú que aparecían como URL simples (p.ej., https://metamate.es/?p=123) en lugar de por nombre de entrada en las traducciones al inglés e italiano. Además, el selector de idioma no funcionaba correctamente, mostrando solo el idioma principal y no los secundarios a menos que el usuario estuviera logueado.
Solución:
Primero, se identificó que las páginas en los idiomas secundarios estaban configuradas como borradores en lugar de estar publicadas. Publicar estas páginas solucionó el problema de los enlaces del menú. Para los enlaces aún incorrectos, se recomendó actualizar las traducciones de dichas páginas y asegurarse de que las URL estuvieran correctas. Para el contenido duplicado, se proporcionó una guía sobre cómo convertir una traducción en un duplicado, disponible en https://wpml.org/documentation/translating-your-contents/displaying-untranslated-content-on-pages-in-secondary-languages/#how-to-convert-a-translation-into-a-duplicate.
Para mejorar el SEO, se sugirieron dos guías:

• https://wpml.org/es/documentation-2/proyectos-relacionados/wpml-seo/
• https://wpml.org/es/documentation-2/seo-multilingue/

Si la solución proporcionada no resuelve tu problema o si parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins.