Problema: El cliente informó que después de un hackeo, WPML estaba mostrando errores continuos de que no encuentra archivos y preguntó si es normal tener ciertos archivos PHP en la estructura de WPML, específicamente en wp-content / languages / plugins. Solución: Confirmamos que es normal encontrar estos archivos PHP en las ubicaciones mencionadas. Si continúas experimentando errores o si la información proporcionada parece desactualizada o no aplicable a tu caso, te recomendamos revisar los problemas conocidos y verificar que tienes instaladas las últimas versiones de los temas y plugins. Si el problema persiste, no dudes en abrir un nuevo ticket de soporte en nuestro foro de soporte.
Problem: The client was experiencing an issue where neither the English nor the French version of their site was working, displaying an 'Error establishing a database connection'. Solution: We asked the client to update their credentials in the support ticket as the previous credentials were removed from an older ticket. This step was necessary to allow us to investigate the issue further. If you're experiencing a similar problem, we recommend checking your database connection settings and ensuring that your credentials are up to date. Additionally, it might be helpful to verify that your server is properly configured to handle database connections.
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 open a new support ticket.
Problem: The client was experiencing an error message after updating WPML, stating that the WordPress REST API must be enabled, despite it being accessible. The issue was compounded by hosting restrictions that blocked certain countries, potentially affecting the REST API's functionality. Solution: 1. We advised the client to contact their hosting provider to check access permissions to their site. 2. We suggested temporarily disabling any restrictions, flushing any cache, and then checking if the issue was resolved. 3. We recommended that the client ask their hosting provider to whitelist wpml.org and ate.wpml.org. 4. We confirmed that it was acceptable to temporarily activate plugins that might be blocking communication with our servers, but to be aware that these could be causing the issue. 5. We clarified that WPML needs to communicate with our servers for managing translations and updates, which is normal for large WordPress plugins. It's not necessary to remove all restrictions, just those that prevent communication with WPML servers.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 persist, please open a new support ticket.
Problem: The client is working on translating a site into traditional and simplified Chinese and plans to use Google Fonts Noto Sans TC and Noto Sans SC. However, Google Fonts do not load reliably in mainland China due to most of the fonts.googleapis.com and fonts.gstatic.com domains being blocked, resulting in slow loading or broken text rendering. Solution: We confirmed that Google Fonts indeed do not work reliably in China. To ensure fonts load properly for a Chinese audience, we recommend self-hosting the fonts. The client has already downloaded local .ttf versions of Noto Sans TC and Noto Sans SC, converted them to .woff2 format using Google Webfonts helper - A Hassle-Free Way to Self-Host Google Fonts, and uploaded these as custom fonts in the Avada theme. This approach is suitable for audiences in China.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, feel free to contact us through the WPML support forum.
