Problem: After migrating from Bluehost to Rocket.net, an older post that was previously translated is no longer linked to its translations. Each translation appears as a separate post, and some categories are incorrect. Solution: Since standard troubleshooting steps did not resolve the issue, we recommend manually linking the translations. It's possible that during the migration, some WPML tables did not transfer correctly. If the original site on the previous host is still accessible, consider redoing the migration using tools like Duplicator or All-in-One WP Migration. To manually link translations in WPML, edit the post and in the Language meta box, select the correct language from the dropdown and save. Then, under "Connect with translations", select the corresponding post for the other language and save.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also 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. For further assistance, visit our support forum at WPML Support Forum.
Problem: The client has transferred their website to a new host and needs assistance ensuring WPML functions correctly on the new site. They previously marked the site as a temporary copy and now wish to set it as the standard production site. Solution: We recommend following the steps outlined in the documentation to move your website to production. Specifically, you can find detailed instructions under the section 'What if the notice still appears after moving to production?' at https://wpml.org/faq/how-to-remove-the-this-site-is-registered-on-wpml-org-as-a-development-site-notice/.
If this solution does not apply to your case, or if it 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client was experiencing an issue where translated post categories were displaying incorrectly on the latest post on their blog. They attempted to use a previous troubleshooting solution that had worked before, but it was unsuccessful this time. Solution: We initially suggested revisiting the troubleshooting steps from a previous ticket. The client tried the suggested solution again, and after a day, it resolved the issue, and the categories displayed correctly. Therefore, no further action was required, and the ticket was closed.
If you're experiencing a similar issue, we recommend revisiting previous troubleshooting steps that may have worked before. It's important to note that this solution might be 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 persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing issues with translated categories on their blog, where categories are labeled incorrectly, missing, or duplicated in different language versions. The Greek and Italian versions have missing categories, while the Chinese version shows duplicated categories. Solution: We recommended checking and maintaining the taxonomy structure across languages by referring to our documentation on Translating Post Categories and Custom Taxonomies. If the structure is incorrect, it is necessary to synchronize the hierarchy. Additionally, we suggested using the following troubleshooting functions in WPML:
Synchronize posts taxonomies (for posts)
Set language information
Fix terms count
Fix post type assignment for translations
These steps helped resolve the issue after they were performed in sequence.
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.
Problem: You are using AHREFS to optimize your site and it has identified numerous hreflang problems, including 215 pages with missing reciprocal hreflang and 14 pages with hreflang leading to redirects or broken pages. Solution: We reviewed the reported issues and found that the pages do indeed have the necessary hreflang tags, including the 'x-default' tag. Additionally, the links that were reported to lead to broken pages or redirects were checked and all returned a 200 status, indicating they are functioning correctly. It appears that the issues reported by AHREFS might be false positives or outdated. You can verify the status of these links yourself using https://www.redirect-checker.org/index.php.
If this solution does not resolve your issue or seems irrelevant due to it being outdated or not applicable to your case, we recommend opening a new support ticket. We also 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. For further assistance, please contact us at our support forum.
Problem: The client reported that the Greek version of a blog post was incorrectly marked as 'Uncategorized' alongside the correct category, and they were unable to unselect 'Uncategorized' despite not having chosen it initially. Solution: We recommended checking the WPML > Taxonomy Translation and running the synchronization to resolve the issue. This action should correct the categorization error.
If this solution does not apply to your situation, or if it seems outdated, we highly recommend opening a new support ticket. Additionally, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can always contact us through the WPML support forum.
Problem: The client was experiencing issues with Yoast Breadcrumbs not displaying the '/blog' path in the breadcrumbs on the Hestia Pro theme, even after disabling all plugins and resaving Yoast and Reading settings. Solution: We checked the blog page and noticed it was missing a title. We added a title to the blog page. We then asked the client to verify if the 'blog' string appeared correctly in the breadcrumbs.
If you're experiencing a similar issue with Yoast Breadcrumbs not showing the correct path, we recommend you: 1. Ensure that your blog page has a title set. 2. Check the breadcrumbs after adding the title to confirm if the issue is resolved.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem persists, we 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 still need assistance, please open a new support ticket.
Problem:
If you're experiencing issues with unwanted translations of your shop page appearing in your sitemap, even though they don't exist in the Page menu, we have a workaround for you.
After applying these changes, please check your product sitemap to see if the issue is resolved.
Please note that this is a temporary workaround and for WooCommerce Multilingual (WCML) to function properly, it's recommended to translate the shop pages.
If this solution does not apply to your case, or if it's outdated, we 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 still need assistance, please open a new support ticket.
Problem: If you're experiencing redirect errors in Google Search Console for translated URLs on your site, where the URLs include a language slug but redirect to an original page, this might be due to the content being recently translated. Solution: We recommend checking if you're using the fallback method where WPML displays the original content in secondary languages when the content is not yet translated. This could result in the slug not being translated. For more information, please refer to our documentation on Displaying Untranslated Content on Pages in Secondary Languages.
If this solution doesn't look relevant, please open a new support ticket in the WPML support forum.
