Problem: The client reported issues with long delays when saving translations on a page, and the footer not translating correctly despite following provided instructions. Solution: 1. For the issue of delays when saving translations, we recommended refreshing the page as demonstrated in the screen recording: https://go.screenpal.com/watch/cZlwDAneqqk. 2. Regarding the footer not translating, we corrected the string translation to point to the correct language Footer template ID via the WPML String Translation interface.
If this solution does not resolve your issues or 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to translate the 'lang' attribute of the VikRentCar shortcode ([vikrentcar view="vikrentcar" lang="en-US"]) using WPML, but the translation does not reflect on the page. The issue arises because the 'lang' attribute is stored in a custom database table and is not dynamically updated during the localization process. Solution: To resolve this, you need to make the value stored in the custom database tables translatable with WPML. You can follow the guide on making strings translatable in WPML here: String Package Translation. Until this configuration is set, you will need to manually translate the page containing the VikRentCar shortcode using the WordPress editor instead of the Advanced Translation Editor. Additionally, since the VikRentCar plugin is not listed in WPML’s compatibility directory, it is recommended to contact the VikRentCar development team for further support and encourage them to join WPML's Go Global program for better compatibility.
If this solution does not apply to your case, or if it seems outdated, 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.
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.
