Problem: The client was experiencing an issue where WPML reported 'WPML doesn't manage the translation' when attempting to update translations for previously translated Chinese articles. The problem persisted even after trying features on the WPML troubleshooting page and changing the PHP version. Solution: We advised the client to downgrade the PHP version from 8.5.5 to 8.2 or 8.3 and check if the issue was resolved. After downgrading, the issue seemed to disappear, which might have been aided by the flushing of an outdated cache memory file. If you're experiencing similar issues, we recommend trying the following steps: 1. Downgrade your PHP version to 8.2 or 8.3. 2. Clear your site's cache. 3. Confirm that the issue is resolved.
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 at WPML support forum.
Problem: The client is experiencing intermittent issues when attempting to start translating a Chinese article to English on their website. Sometimes the translation initiates without any problems, but at other times, it fails to start. The WPML dashboard shows an error indicating that WPML tried to translate the page three times and failed, along with repeated 'Job resent to ATE' events in the logs.
Solution: We recommend the following steps to resolve the issue: 1. Navigate to WPML → Translation Dashboard. 2. Click on the Jobs tab. 3. Locate the translation job for the Chinese article (identified by the article title or Job ID 74) and click the Cancel button next to it. 4. Go to Articles in your WordPress admin and edit the original Chinese article by making a minor change (e.g., adding a space). 5. Save the article and resend it for translation from the Translation Dashboard or the Articles list page.
If the problem persists after following these steps, it may require further investigation by our support team. Please use the 'Switch to Human Support' button for direct assistance.
Please note that the solution provided 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 issue continues, do not hesitate to open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client was unable to attach a WPML language switcher to the 'main' menu on their development website, which was built using Elementor. WPML did not recognize the menu, and the client preferred the language switcher to be integrated directly within the menu rather than as a separate element. Solution: 1. We advised the client to ensure that the menu is translated, as WPML requires menus to be translated to assign a language switcher to them. Detailed steps for translating menus can be found here: https://wpml.org/documentation/getting-started-guide/translating-menus/ 2. After translating the menu, the client can add a language switcher to it via WPML -> Languages. 3. We also recommended increasing the WordPress memory limit to at least 128MB, as per WPML's minimum requirements. This can be done by adding the following code to the wp-config.php file:
This code should be placed above the line /* That's all, stop editing! Happy blogging. */. The client can verify the WordPress memory limit in WPML -> Support.
If this solution does not resolve your issue 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: After migrating a production website to a local development environment using the "All-In-One WP Migration" plugin and updating WPML settings, the client is unable to start any translation jobs. The edit button in the translation job redirects to the "Translation Queue" UI instead of allowing editing. Solution: We recommend changing the local development environment URL from the default http://localhost.local/ to a more specific one, as the Advanced Translation Editor (ATE) might not function correctly with common local URLs. Additionally, follow these steps to diagnose and potentially resolve the issue: 1) Activate the debug.log: - Enable WordPress debugging by editing the wp-config.php file. Insert these lines before the comment /* That's all, stop editing! Happy publishing. */:
- Replicate the error. - Check the debug.log file in the /wp-content directory for any WPML-related errors and share the full error message with us. 2) Verify if the same fatal error occurs as in a similar case found here: https://wpml.org/forums/topic/cannot-translate-3/#post-17937026 3) Apply the fix suggested in the support ticket linked above.
If these steps do not resolve the issue, it might be due to outdated solutions or a different problem. 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 our support forum.
