Problem: The client was experiencing an issue where part of the layout was missing from the translated page of their website, even though it was visible in the source code.
Solution: We investigated the issue and initially thought it might be related to the Spectra plugin. However, further investigation showed that the problem was not with Spectra, as other translated pages displayed correctly. The client then experimented by removing different blocks from the page and discovered that a specific block was causing the issue. Once this block was removed, the layout appeared correctly on the translated page.
If you're experiencing a similar issue, we recommend trying to isolate the problem by selectively removing components or blocks to see if one might be causing the layout to break. Additionally, ensure that all plugins and themes are up to date.
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 further assistance.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that the banner image on their blog category page was not translated, despite being processed through the Media Translation plugin. This issue was specific to the blog category page, as translations worked correctly on other pages. Solution: We discovered that the issue occurred only on the category page and suggested a workaround. We recommended rearranging the blocks on the page: moving the column containing the image block above the column that has the WordPress Archive Output block. This change should allow the translated image to display correctly on the frontend.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking for 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 problems persist, please open a new support ticket.
Problem: The client created a post category template that appears correctly in the default Spanish language but has layout issues in other languages. The translated version is missing several divs, causing the layout to be inconsistent with the default template. Solution: We resolved the layout issue by adjusting the block arrangement in the WPML Advanced Editor. Specifically, on the staging site, we moved the "WordPress Archive Output" block under the "Column" block and above the "WordPress Archive Loop" block. The client should replicate these changes in the English and French translations of the layout. On the live site, we ungrouped the block items under the "WordPress Archive Loop" block, updated the translation layout, and cleared the SG cache. This adjustment made the layout in the English version consistent with the Spanish version.
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 the problem persists, please open a new support ticket.
Problem: The client was facing an issue where the 'read more' text in the posts was not translating correctly using WPML, despite other text translations working fine. This issue persisted even after deactivating the Post Type Order plugin and rebuilding the template. Solution: We identified that the untranslated 'read more' text was part of a Toolset template. To resolve this, we translated the specific text using the WPML Advanced Translation Editor (ATE) via the Translation Management section. After applying the translation directly in the Toolset template, the 'read more' button text displayed correctly in the desired language.
Please note that this solution might be outdated or not applicable to your specific case. If you're still experiencing issues, we 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 the problem persists, please open a new support ticket.
Problem: The client is trying to translate the blog page and the category page using Toolset templates, that fully compatible with WPML. Despite using the advanced translator, media translation, and string translations for elements like the slider texts, some texts, sidebar images, and the slider in the hero section remain untranslated in the default language, Spanish. Additionally, the blog category page automatically switches from Spanish to French, and outdated translated versions of the page persist. Solution: We identified that a plugin conflict was causing the translation issues. There was a plugin, called "Post Types Order" by Nsp code, that was causing the issue. If the problem persists or if you encounter new issues, we advise opening a new support ticket. For further assistance, please visit our support forum at https://wpml.org/forums/. Additionally, it's crucial to check for any related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and ensure that you have installed the latest versions of themes and plugins. If this solution does not apply to your case because it might be outdated or not relevant, please do not hesitate to open a new support ticket.
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.
