Problem: The client needed to set different slugs for a custom post type (CPT) archive page in different languages. The default slug was in Spanish, and translating it directly using WPML's String Translation caused issues, resulting in pages not relating properly and 404 errors.
Solution: We informed the client that WPML currently has a limitation when it comes to translating the 'has_archive' option for a unique value, meaning that a direct translation of the CPT archive slug is not possible at this time. We provided a guide for a better understanding of this limitation:
We suggested that if the client enables the 'Has archive' and uses the default CPT's slug, they can then translate that slug from "WPML > Settings > Post Type Translation".
We also mentioned that our development team is aware of this issue and is working on a solution for a future version of WPML, but we do not have an estimated time of arrival for this update.
If this solution is not relevant to your case, either because it's outdated or not applicable, we recommend opening a new support ticket. 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 you need further assistance, please contact us in the WPML support forum.
Problem: The client was experiencing an issue where Toolset repeat fields were not consistently showing the correct manual translation across multiple pages. Instead, automatic translations were sometimes loaded. Additionally, there were problems with translations not appearing in WPML>Translations for certain languages, and a message indicating a failure to synchronize with the professional translation system was displayed.
Solution: We recommended the client to make minor edits to the primary language page and then re-translate the affected pages. This process should resynchronize the translations and ensure that the correct manual translations are displayed instead of the automatic ones. Specifically, we advised editing the primary language page at
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should the problem persist, please do not hesitate to open a new support ticket with us for further assistance. You can do so by visiting the WPML support forum.
Problem: Advanced Translation Editor doesn't load properly. Solution: We recommend clearing your browser cache as outlined in our errata on the Advanced Translation Editor (ATE) freezing issue. You can find the instructions here: https://wpml.org/errata/advanced-translation-editor-ate-freezing-issue-on-certain-browsers/. If this does not resolve the issue, we suggest trying a different browser to see if that fixes the problem.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking the 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 in the WPML support forum.
