Problem: After moving to a new server and activating the WPML plugin, you are experiencing PHP warnings related to open_basedir restrictions on every page load. This issue started after the server migration, despite using WPML String Translation 3.2.18. Solution: We recommend clearing your logs and cache to ensure that no old server paths are being cached erroneously. It's also important to double-check the logs after performing these steps. If the problem persists, it might be related to specific server settings or configurations that were changed during the server migration. For detailed guidance, please refer to our documentation on this issue: open_basedir restriction issue.
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, you can open a new support ticket for further assistance at WPML support forum.
Problem: You are experiencing a Divi Timeout Error when trying to edit translated Divi Builder Template pages in the backend, resulting in a 404 page instead of the template. This issue occurs when the WPML plugin is active. Solution: To resolve this issue, follow these steps: 1. Ensure you edit the Divi Template in the site's default language using the Divi Theme Builder. 2. To translate the template, go to WPML > Translation Management. Use the post type filter to select your template's post type (Header, Body, or Footer Template). 3. Create a translation job for the template and access it at WPML > Translation to translate the template using the WPML Translation Editor. 4. Avoid editing translations directly in Divi when using the WPML Translation Editor as your translation method. If you prefer to create translations directly in Divi, change the translation method to "WordPress Editor" in the right sidebar of the WordPress Editor.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket at WPML support forum.
Problem: You are unable to publish translations for old pages that were previously translated using WPML. These pages remain 'in progress' even though they show 100% completion. Solution: 1. First, try saving the translation inside the WordPress Editor to see if this changes the status from 'in progress' to 'Completed'. This should allow you to open the WPML Translation Editor. 2. If the issue persists, take a backup of your site and then navigate to WPML > Support > Troubleshooting. Use the following options: - Clear the Cache in WPML For more details, visit WPML Troubleshooting Options.
If these steps do not resolve the issue, it 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 problem persists, please open a new support ticket at WPML Support Forum.
Problem: You are managing product prices with VAT using WPML WooCommerce Multilingual on a site under development. You've noticed that product prices, including VAT, change unexpectedly after changing the order status from in progress to completed.
Solution:
First of all please make sure that the decimal separator isn't wrongly translated in String Translation.
If you're still experiencing this issue, we recommend you try the following steps: 1) Ensure you take a full backup of your site and database before proceeding. It is highly advised to try these on a dev or staging site first, so your live site isn't compromised. 2) Deactivate all plugins except for WPML, String Translation, WCML, and WooCommerce. 3) Switch to a standard theme like 2024 or 2021. 4) Check if the issue still occurs.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 the problem persists, please do not hesitate to open a new support ticket at our support forum.
Problem: You are experiencing a Yoast license issue on your WordPress site. Specifically, the license works on the primary language site but not on the secondary language (French) site. This discrepancy arises because the WordPress and Site addresses for the original language settings are the same, but they differ in the secondary language. Solution: If you're experiencing this issue, we suggest verifying the domains and updating your Yoast account accordingly. In doubt please consult the Yoast support team.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
