The client is unable to translate the footer of their website using WPML, despite having successfully translated the header. They are using the 7Up Theme.
Solution:
If you're experiencing this issue, we recommend checking if the Footer post type is set to be translatable. You can do this by navigating to WPML>>Settings>>Post Type Translation. Ensure you perform a site backup first, then set the option for the Footer post type to Translatable – only show translated items and save the changes. Afterwards, attempt to translate the Footer posts to see if the issue is resolved.
For more detailed guidance, please refer to our documentation on translating custom posts: Translating Custom Posts.
If this solution does not apply because it might be outdated or not suitable for 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: You are experiencing an issue where string translations revert to previous versions even after clearing the cache in WPML and the W3 Total Cache plugin, and deactivating the latter. The server does not have cache functions. Solution: The issue might be related to how textdomains are loaded in your theme or plugins, especially with the changes introduced in WordPress 6.7. We recommend checking if your theme or any plugins are using an outdated method to call textdomains. You should discuss this with your theme's developer. For more details, see the discussion on WordPress support.
If this solution does not apply to your case, or if it becomes outdated, we highly recommend checking related known issues at WPML 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.
Problem: You are managing translations in the backend of your WordPress site and notice a discrepancy: the translation queue shows no translations, yet a notification indicates that one translation is waiting for review. Clicking on the notification leads to a screen with no translations. Solution: We recommend following these steps to resolve the issue: 1. Navigate to WPML -> Support -> Troubleshooting. 2. On the troubleshooting screen, sequentially press the following buttons, waiting for each process to complete before proceeding: - 'Disable cache for language switcher templates' - 'Clear the cache in WPML' - 'Remove ghost entries from the translation tables' - 'Fix element_type collation' - 'Set language information' - 'Assign translation status to duplicated content' - 'Set language information' - 'Fix terms count' - 'Fix post type assignment for translations' Then, recheck to see if the issue persists.
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 the problem continues, please open a new support ticket at WPML support forum for further assistance.
Problem: After reinstalling WPML, the client encountered an error where a necessary folder for storing .mo files was not being created, and thus, the folder was not writable. This issue persisted even after the hosting company attempted to intervene by increasing site memory and manually adding the folder. Solution: We recommended manually creating the folder path for WPML's .mo files using an FTP program or through the admin control panel. This step ensures that the folder exists and can be checked for the correct writable permissions. Additionally, we suggested running a troubleshooting tool available at WPML's troubleshooting page to resync translations and verify if automatic translation functions correctly after these adjustments.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your current setup, 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. Should the problem persist, please do not hesitate to open a new support ticket with us for further assistance.
Problem: The client was unable to open the Elementor editor for a translated page/template, resulting in a 403 Forbidden error and an uncaught TypeError. Solution: The client said he had found a folder named /he/ on the server. Removing this folder solved the problem. If this solution is 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 issues persist, please open a new support ticket at WPML support forum.
Problem: In the Spanish version of a multilingual webshop, the client is unable to set display conditions in Elementor for the Spanish category 'JUEGO TABLAS'. Despite the taxonomy hierarchy being synchronized, only Slovenian categories are available for selection. Solution: We discovered that the issue was due to the use of an outdated 'Products' widget in Elementor, which was deprecated since version 4.1.3. We recommended switching to the 'Products Grid' widget. After making this change, the client should verify if the translated archive displays correctly by checking the front end.
If this solution does not resolve the issue or seems outdated, we highly recommend checking related 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 experiencing two main issues with a translated contact form. First, the dropdown options in the form are not fully displayed in the translated version. Second, the link to the privacy policy page is not correctly pointing to the translated version of the page. Solution: 1. For the dropdown options not displaying correctly, ensure that the options are correctly added and formatted in both the default and translated forms. You might need to update the default form to match the format shown in this demo, and then resend the form for translation. 2. For the incorrect privacy policy link, the link should be translated through the Translation Editor. In the Translation Editor, find the paragraph where the link is added, unlock the field with the lock icon, update it with the translated page link, and save the translation. If these steps do not resolve the issues or if the solution seems outdated, 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.
Problema: Estás intentando activar la licencia de WPML para tu sitio web y encuentras que tu sitio no puede conectar con la API de WPML. Solución: Primero, verifica si el problema se debe a una configuración del servidor o a un plugin o tema de terceros que podría estar bloqueando la comunicación con nuestros servidores. Te recomendamos que contactes con tu proveedor de hosting para que revisen posibles bloqueos en el servidor que afecten a los plugins de WPML. Además, existe otra forma de registrar WPML automáticamente usando PHP, aunque no podemos garantizar que esta solución siga siendo efectiva. Puedes encontrar más información aquí: Registro automático de WPML usando PHP. Es importante que tu sitio pueda conectarse con nuestros servidores para mantener el plugin actualizado.
Si la solución proporcionada no resuelve tu problema o parece no ser relevante debido a actualizaciones o diferencias en 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 temas y plugins. Para más asistencia, visita nuestro foro de soporte en español.
