Problem: The client is experiencing an issue where WPML's Advanced Translation Editor (ATE) has refused the request due to a detected change in the site's URL after cloning the site. The error status shown is 426, indicating that confirmation is needed before syncing translations again. Solution: If you're experiencing this issue, we recommend re-registering both your live and staging websites independently. Here are the steps to follow: 1. Visit https://wpml.org/account/sites and remove the website from the list. 2. Add it again and copy the newly generated key. 3. In your website's admin panel, navigate to Plugins > Add New > Commercial Tab and click on "Unregister WPML from this site". 4. Register the website again using the key you copied in step #2. Perform these steps for both your live and staging websites.
This solution might be irrelevant if it's 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 issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing UI issues on their website pages when the WPML string translation plugin is enabled, specifically in the Indonesian language. Solution: We recommended enabling WP Debug to gather more detailed error logs. The steps include modifying the 'wp-config.php' file to enable WP_DEBUG, WP_DEBUG_LOG, and SCRIPT_DEBUG while disabling WP_DEBUG_DISPLAY. This setup helps in logging errors without displaying them on the site. For detailed instructions, visit WPML Debugging Documentation and WordPress Codex on Debugging. Additionally, to address potential issues with page updates not reflecting in translated versions, we suggested: 1. Open the default language page in Edit mode. 2. Make a minor change (e.g., add a space or + sign in the page title). 3. Save the page. 4. Remove the change made in step 2. 5. Update the page again. 6. Attempt to open the translated page in the WPML Translation Editor to check if it loads correctly. If these steps do not resolve the issue, we advised opening a new ticket for further investigation.
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 for personalized assistance.
Problem: The client is experiencing issues with the UI of some Indonesian pages on their website not displaying correctly after translating the website into Spanish using the WPML String Translation plugin. Deactivating the plugin resolves the issue, suggesting a problem with string translation. Solution: 1. We recommended the client to provide debug information to better understand the site configuration. This can be done by following the steps at https://wpml.org/faq/provide-debug-information-faster-support/. 2. If the issue is related to menu translation: - Navigate to Appearance > Menus. - Select the problematic menu and switch to the translated language. - Delete the translated menu and synchronize it again by following the steps at https://wpml.org/documentation/getting-started-guide/translating-menus/. 3. Check if reducing the text size in the menu buttons resolves the issue, as oversized text might be causing layout problems.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing a PHP warning stating 'foreach() argument must be of type array|object, null given' in the AutomaticTranslationJobCreationFailureNotice.php file when activating the WPML Multilingual CMS plugin, we can help you resolve this. Solution: First, ensure you have a full backup of your website. Then, follow these steps: 1. Navigate to Plugins > Plugin File Editor. 2. Open the /wp-content/plugins/sitepress-multilingual-cms/classes/automatic-translation/AutomaticTranslationJobCreationFailureNotice.php file. 3. Find the following line of code:
This modification should resolve the PHP warning. If this solution does not apply to your situation, or if it becomes 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 issues persist, please open a new support ticket.
Problem: The client is unable to use their translation credits on WPML to translate content despite having credits available. They also encountered issues with Vietnamese translations not completing and some page links showing with page IDs instead of slugs. Solution: 1. To resolve the issue with using translation credits, we advised the client to ensure that the migration banner is set up correctly. 2. For chatting with support, the client needs to close the current ticket and open a new one for chat support. More information can be found here: https://wpml.org/announcements/2018/11/chat-support-for-wpml/ 3. To check the status of the Vietnamese translation, navigate to WPML -> Translation Management, filter by the default language, and check the translation status in the desired section (posts, pages, etc). 4. To translate the homepage, go to WPML -> Translation Management -> Pages, select the homepage, and send it for translation. 5. For pages showing with page IDs instead of slugs, ensure these pages are published. Go to Pages -> Filter by Vietnamese language -> Click on Quick Edit link below the page title -> Change the status to 'Published' and save the changes.
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 further assistance is needed, please open a new support ticket at WPML support forum.
