Problem: If you're experiencing issues where the bundle ID is not correctly pointing to its translated version in WPML, despite being set to copy, this might be similar to the issue we encountered. In this specific case, the bundle ID 20 was not automatically pointing to its translated counterpart, ID 21. Solution: We recommend checking the settings to ensure that the IDs are correctly linked for translation. If the problem persists, it may require further investigation by our compatibility team. We will keep the client updated on any progress.
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 continues, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are facing an issue where product bundles are not being copied over to translations in WooCommerce. Even manual additions disappear upon publishing. Solution: This problem stems from a function in the WooCommerce core, not the WooCommerce Product Bundles plugin. Currently, there's an internal ticket reviewing potential changes to this behavior. Meanwhile, you can prevent the duplication of translations when duplicating a product by adding the following code to your theme's functions.php file:
/** * Prevent WCML from also duplicating the translations * when duplicating a product. */ add_action( 'admin_init', function() { /** @var \woocommerce_wpml $woocommerce_wpml */ global $woocommerce_wpml; if ( isset( $woocommerce_wpml->duplicate_product ) ) { remove_filter( 'woocommerce_product_duplicate', [ $woocommerce_wpml->duplicate_product, 'woocommerce_duplicate_product' ] ); } } );
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have the latest versions of themes and plugins installed. If necessary, do not hesitate to open a new support ticket.
Problem: You are experiencing an issue where a single block template created in the Site Editor, when translated, receives a different slug, causing the front end page not to recognize the template. Solution: We recommend following the workaround described in our errata to address the slug mismatch issue. Please visit the following link for detailed steps: https://wpml.org/errata/template-is-not-applied-to-translated-page/ If the problem persists after implementing these steps, we encourage you to open a new support ticket for further assistance. 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.
If you need further assistance, please contact us through our support forum: WPML Support Forum
Problem: If you're experiencing issues with permalinks for translated posts using WPML along with Yoast SEO and WPML SEO Multilingual, where the Yoast sitemap outputs URLs that mix the English path with the translated slug, leading to 404 errors, this might be due to the language context not being switched when generating permalinks. Solution: We recommend trying the workaround described in the WPML errata page. You can find the detailed steps here: WPML SEO Incorrect URLs in Sitemap Alternate Links. If this workaround does not resolve the issue, it's possible that the 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 problems persist, please open a new support ticket with us for further assistance at WPML support forum.
Problem: You are experiencing issues with updating translations manually in Elementor for multiple pages and languages, and you are concerned about being charged additional fees for translation credits. You also mentioned problems with activating the OTGS plugin and a related issue with base64 encoded content. Solution: We are aware of the difficulties you are facing and plan to enhance the functionality in a future release of the Advanced Translation Editor. The specific issue with sending base64 encoded content to translation is also recognized and will be addressed in the upcoming WPML version 4.9.3.
If this solution does not resolve your issue or seems outdated, we 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: 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: You need to solve an issue related to a fatal error with the flux checkout. Solution: We recommend trying the following workaround. First, ensure you take a backup of your site. Then, follow the instructions provided in this documentation: Flux Checkout Fatal Error.
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 at WPML support forum for further assistance.
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.
