The client encountered a bug in class-wcml-product-bundles.php line 796 after upgrading to the newest version of WPML, which required re-applying a personal patch.
Solution:
We have addressed this issue, and the fix will be included in the WooCommerce Multilingual 5.4.0 version. In the meantime, we recommend following the workaround suggested in the errata after taking a full site backup.
Please ensure you take a full site backup before updating to the latest versions of the plugins WPML ones and WooCommerce. After updating, verify if the issue is resolved.
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 the issue persists, please open a new support ticket.
If you're experiencing deprecated warnings like 'Creation of dynamic property Whip_RequirementsChecker::$configuration is deprecated' when using PHP 8.2 with WPML, this is a known issue.
Solution:
1. We recommend disabling WordPress debug mode to prevent these warnings from displaying to site visitors. You can do this by adding the following line to your wp-config.php file:
define('WP_DEBUG_DISPLAY', false);
2. This issue has been addressed in the WPML 4.8 series. Please ensure you take a full site backup before updating to the latest version of WPML. After updating, verify if the issue is resolved.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where Polish translations are appearing on the English page of their WordPress site, despite using WPML and ACF addons. They were advised to add a new filter after accidentally enabling translation for an ACF field group. Solution: We reviewed the client's page and did not initially see the Polish content on the English filter. After further investigation, we directed the client to an existing errata that addresses issues with ACF fields not being translated on the frontend. We recommended using the workaround provided in the errata. For more details, please refer to the following link: https://wpml.org/errata/filter-everything-acf-fields-not-translated-on-frontend/.
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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: You are encountering an API error stating 'No sitekey found for this website' after deregistering and activating a new key on your WPML installation. Additionally, despite translating links in ATE and updating them, they remain in the original language. Solution: First, ensure that the sitekey issue is resolved by checking if the new key is correctly activated in your WPML account. If the problem persists, it might be due to a known issue which our developers are currently addressing. You can track the progress and find more details on this issue at WPML Errata page. For the link translation issue, it is identified as a new problem, and our developers are working to resolve it in the upcoming version of WPML.
If these solutions do not apply to your case, or if the problem persists, 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 still need assistance, please open a new support ticket at WPML support forum.
Problem: The client was experiencing issues with custom fields not displaying correctly after translating pages using WPML's Advanced Translation Editor (ATE). The content from some custom fields was serialized in the database, which prevented it from displaying correctly in the WordPress editor. Solution: We identified that the serialization of complex custom field keys in the database was causing the issue. To resolve this, we applied a specific solution from the WPML errata. Here are the steps we followed: 1. Opened the page for editing in the default language (English). 2. Made a minor change in one of the text fields in the "Page problem tab". 3. Saved the changes. 4. Updated the Hebrew and Arabic translations in ATE. 5. Checked the "Page problem tab" fields by switching to Hebrew and Arabic in the WordPress editor to ensure the fields displayed correctly. For existing pages with issues, repeating these steps should resolve the problem. Additionally, we recommend bookmarking the errata page for future reference and subscribing to comments for updates on permanent fixes.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing an internal server error when trying to translate pages using WPML, particularly with pages containing images without metadata, this might be due to a known issue. Solution: We recommend waiting for the upcoming WPML 4.8.1 update, which addresses this issue. You can check the progress and details of this known issue on our errata page: WPML 4.8 Fatal Error When Translating Pages Containing Images Without Metadata.
If this solution does not apply to your case, or if it seems outdated, please open 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.
