Problem: If you're experiencing issues where the header and footer do not appear on translated pages using FSE pattern templates, it might be due to incorrect template assignment. Solution: First, ensure that the templates are correctly translated and check if they are assigned properly to the translated pages. This issue often arises when templates share the same slug or have very similar names. For more details, you can refer to our documentation on this known issue at https://wpml.org/errata/template-is-not-applied-to-translated-page/. In the specific case addressed, we manually edited the second language homepage and assigned the correct template, which resolved the issue. If you add a new language, you might need to manually assign the correct template to the translated pages as well. A permanent fix is planned for WPML 4.10. .
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. If issues persist, please open a new support ticket at WPML support forum.
Problem: The client was experiencing issues with the WooCommerce Product Bundles plugin where bundled products were not being synchronized in translations. Solution: We recommended checking if the issue aligns with a known problem detailed on our errata page: https://wpml.org/errata/woocommerce-product-bundles-bundled-products-not-synced-in-translations/. Following this, we advised the client to: 1. Navigate to Dashboard > Products. 2. Open the edit screen of the original product and make a minor change (e.g., adding an extra space). 3. Save the changes, which should prompt an update icon beside the translation links indicating that an update is required. 4. Re-edit the translation to ensure it is 100% translated and save again. If this solution does not resolve the issue or 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. If the problem persists, please open a new support ticket at WPML support forum.
Problem: You attempted to translate a page, but encountered an error stating that WPML cannot send some of the content for translation because it includes fields that are encoded. As a result, these fields were removed from the translation job. Solution: We have escalated this issue to our development team for further investigation. Meanwhile, we recommend you follow the workaround provided to handle pages with base64 encoded content. You can find detailed instructions on how to proceed by visiting the following link: WPML cannot send base64 encoded content to translation.
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 issue persists, please open a new support ticket.
Problem: If you're experiencing issues with your translated page templates still displaying in the original language, or inconsistencies with the language selector, the issue might be related to the slug of the translated template. Solution: First, check if adding a "-2" to the slug of your translated template occurs by referring to our documentation on this specific issue: Template is not applied to translated page. If this is the case, removing the "-2" from the slug should resolve the problem. We are aware of this behavior and plan to make improvements in future releases to prevent similar issues.
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. If issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are working on a preproduction website and encountering issues with automatically translating pages because the plugin indicates that the pages are encoded. Solution: We recommend using the workaround provided in the this documentation. If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/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 encourage you to open a new support ticket for further assistance at WPML support forum.
Problem: After migrating a site, TRANSLATE-mode custom fields fail to sync to wp_postmeta due to the FilterJobUrlMigration component in WPML. This component incorrectly handles non-base64 encoded field_data, leading to data corruption and loss of custom field values in the translated post. Solution: Until this issue is resolved, you can avoid the problem by:
- Sending content for translation directly from the post edit screen, or
- Sending content from the post list screen using the + icon.
It also works if your content is being translated with Translate Everything Automatically.
If these solutions do not resolve your issue or seem 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. If the problem persists, please open a new support ticket for further assistance.
