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.
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.
as malicious after updating the string translations plugin, this is identified as a false-positive. Solution: We have confirmed that this is a false-positive warning by Wordfence. A fix for this issue is scheduled for the next WPML release. For more details, you can visit our errata page: https://wpml.org/errata/wordfence-reports-a-false-positive-security-warning-with-wpml-4-9-0/
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue installing WPML in a Bedrock + Composer setup due to the inability to access the official WPML Composer repository at https://packages.wpml.org/packages.json. The error reported is 'curl error 6: Could not resolve host: packages.wpml.org', and DNS resolution for packages.wpml.org fails (NXDOMAIN). Solution: We currently do not support installation or updates of WPML via Composer natively. There is no official or supported method to automatically fetch the latest WPML versions via Composer. However, a suggested workaround is discussed in a forum thread, which can be found here: https://wpml.org/forums/topic/composer-update-to-latest-plugins-versions/. Additionally, you can refer to our errata entry here: https://wpml.org/errata/composer-installation-of-wpml-not-officially-supported-yet/. A third-party project that might help is available at https://github.com/ffraenz/private-composer-installer, where the version can be handled as a placeholder.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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 contact us through the WPML support forum.
Problem: The client reported a critical security alert from Wordfence concerning a file in the wpml-string-translation.3.5.0 update, identified as potentially malicious or unsafe. The file in question is located at wp-content/plugins/wpml-string-translation/lib/StringScanning/vendor/wp-cli/wp-cli/features/context.feature, and it is flagged as a backdoor with suspicious modifications. Solution: We have identified this issue as a false-positive warning by Wordfence. This will be addressed and resolved in the upcoming WPML release. For more details, please visit our errata page at https://wpml.org/errata/wordfence-reports-a-false-positive-security-warning-with-wpml-4-9-0/.
If this solution does not seem relevant to your case, or if it appears 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.