Problem: The client is experiencing issues with locked fields in WPML and has concerns about the translation of the footer, which does not display correctly across different language versions of the site. Solution: We clarified that the locked fields can be unlocked simply by clicking on the 'lock' icon. Regarding the footer, it appears that the client had previously attempted to fix the issue by deleting the translated footer template directly from the database. However, this did not resolve the problem as the footer still does not appear correctly. We suggested that the footer's translation issue might be due to the limitations described in the WPML errata for the Pro theme, where layout texts are not translatable via the WPML Translation Editor (https://wpml.org/errata/pro-theme-layout-texts-not-translatable-via-wpml-translation-editor/). The client can either manually translate the template or apply custom code to make it compatible with String Translation. We asked the client to confirm if they intend to use String Translation for the footer in the same way as the “Object (CPT) – Single View” template.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues (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 reported issues with untranslated parts of their website, including the sidebar, bullet points, button 'bekijk vergroot', subheadline 'het verhaal', and the footer. Additionally, some ACF fields were locked, preventing translation. Solution: We advised the client to activate the pro version of the ACF plugin to unlock and edit the fields. For the untranslated text not coming from ACF fields, you can follow this errata https://wpml.org/errata/pro-theme-layout-texts-not-translatable-via-wpml-translation-editor/ If this solution does not resolve your issue or seems irrelevant due to updates or different circumstances, 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. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: If you're trying to translate a Gravity Forms form and have installed the Gravity Forms Multilingual but cannot see the 'Gravity Forms' tab under WPML → Translation Dashboard. Solution: We recommend you follow these steps: 1. Navigate to WPML >> Translation Dashboard. 2. Click on the “Clear Filters” link. This action should make the Gravity Forms tab visible on your WPML Translation Dashboard. Please check and confirm if this resolves your issue.
If this solution does not apply because it might be outdated or not suitable for 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: The client is experiencing issues with the single post layout when using WPML with ThemeCo Pro, specifically with a custom post type. The site crashes, likely due to insufficient server resources. Solution: 1. We installed the ACFML addon to support Advanced Custom Fields (ACF) integration with WPML. For detailed steps on this setup, visit https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/. 2. We configured the 'acf-field-group' to 'Not Translatable' in WPML > Settings to avoid unnecessary translation loads. 3. We attempted to delete the English single layout for the custom post type so that Cornerstone would automatically use the Dutch layout instead, but the site continued to crash. 4. We checked and confirmed that the header is locked for translation, and the footer was not translated.
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 issues persist, please open a new support ticket at WPML support forum.
Problem: You are using WPML AI translations across multiple websites and need a detailed breakdown of the monthly credits used and their costs per website. You are unable to find which website used how many credits and are looking for a centralized place to view credit usage for the current and previous months. Solution: To view the detailed breakdown of monthly credits used per website, you need to access each website individually. Follow these steps: 1. Log in to each website you manage. 2. Navigate to WPML > Translation Management > Translation Tools. 3. Here, you can download reports divided by month, detailing which content was translated, to which languages, and how many credits were used. Currently, you can only access this information by logging into each site individually. On your WPML.org account, you can view purchases for credit packages and payments for the Pay-As-You-Go subscription at: https://wpml.org/account/view_order/
If this solution does not apply to your situation, or if it seems outdated, 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 visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is trying to translate a page into Dutch, but the translation does not appear on the front end, even though the Translation Editor indicates that the translation is complete. Solution: 1. We noticed that the Pro theme by Themeco was not updated to its latest version. We recommended updating the theme to see if this resolves the issue. 2. We also discovered that the issue could be resolved by updating WPML to the latest version, 4.7.0. You can download the latest version of WPML from here. 3. Before updating, ensure to make a full site backup (files and DB) to prevent any potential data loss.
If these steps do not resolve your issue, or if the solution 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. Additionally, please feel free to open a new support ticket on our forum for further assistance at WPML support forum.
