Problem: You are experiencing an issue with the String Translation table after performing a WPML reset. This problem is not currently affecting your site's operation but could become critical in the future. Solution: If you have not yet completed any translations, we recommend resetting WPML again and reconfiguring it. Please follow these steps: 1. Navigate to WPML → Support and click on the Troubleshooting link. 2. In the Reset section of the Troubleshooting page, check the "I am about to reset all translation and language data" box. Then, click the "Reset and deactivate WPML" button. For detailed instructions, visit WPML Reset Documentation. Before making any changes, ensure that you back up your database.
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.
Problem: The client's homepage in English was showing only the latest posts instead of the translated content, even though it was translated and working fine in the past. Solution: 1. We asked the client to check if the posts were translated. 2. We requested a screenshot of the permalinks settings for the English language. 3. We advised the client to provide WPML debug information. 4. We suggested navigating to Settings → Reading to check the homepage configuration for English. 5. We recommended increasing the WP_MEMORY_LIMIT value to at least 256M. 6. We instructed the client to switch the homepage settings to 'Latest Posts', save it, then change it back to a static page and save again. 7. Upon further investigation, we found that the issue was not related to WPML. The header on the English homepage was set to display posts. We provided a screenshot for reference and corrected the header to point to the correct template, which resolved the issue.
If this solution does not apply to your case, or if it seems outdated, we encourage you to open a new support ticket. We also 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 you need further assistance, please contact our support forum.
