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.
