Problem: After updating WPML Multilingual CMS on a staging site, the WPML Settings and Translation Dashboard are stuck in an admin refresh loop, endlessly auto-refreshing. Solution: If you're experiencing a similar issue, we recommend the following steps: 1. **Update WPML String Translation:** * Navigate to Plugins → Add New Plugin in your WordPress admin. * Click on the Commercial tab. * Click the Update button next to WPML String Translation to ensure it's updated to the latest version. 2. **Clear WPML Cache:** * Go to WPML → Support → Troubleshooting. * Clear the WPML cache and transient data.
If these steps do not resolve the issue, it might be due to other factors such as compatibility with other plugins or themes. Since 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 the problem persists, please open a new support ticket for further assistance. You can do so at WPML support forum.
Problem: When saving the original English version of a page, the translated versions (French, Spanish, UK) revert to English. The client follows steps to duplicate the US version of the article and set the duplicated pages to 'Translate Independently'. Solution: Temporarily disable WPML String Translation when creating a new manual translation using the WordPress Editor. This is a known issue detailed here: https://wpml.org/errata/editing-translated-posts-directly-can-result-in-lost-content/.
Note: An update from WPML that addresses this issue is expected soon, though no specific release date is available.
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. We highly recommend opening a new support ticket if the problem persists. Visit our support forum here: https://wpml.org/forums/forum/english-support/.
Problem: The client experienced a fatal error after updating Elementor to version 3.27.6, which was resolved by updating WPML Multilingual CMS. The error was due to a class not being found by Elementor, indicated by server logs pointing to WPML Multilingual. The client wanted to understand the cause and if there's a specific update order to follow. Solution: 1. Ensure both Elementor and WPML are updated to the latest compatible versions to avoid version mismatch issues. 2. If Elementor is still causing errors, try deactivating and reactivating it. If the issue persists, reinstall Elementor by deactivating, deleting, and then reinstalling the plugin. 3. Check for other potential conflicts such as theme conflicts, other plugin conflicts, cache issues, PHP version compatibility, or issues with the WPML Page Builders addon. 4. Always update plugins as soon as new updates are available to prevent such issues. For more details on known issues between Elementor and WPML, visit https://wpml.org/plugin/elementor/
If this solution does not apply to your case, or if it seems outdated, 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 visit our support forum.
Problem: The client is updating their WPML plugins and is concerned about compatibility with the latest WordPress version 6.7.2. They are considering updating from WPML Multilingual CMS Version 4.6.3 to 4.6.15 and have questions about potential issues, update timelines, and recommendations on plugin updates. Solution: We recommend updating to the latest WPML version 4.7.1, which is fully compatible with WordPress 6.7.2. Here are the steps to update your WPML plugins: 1. Create a backup of your database. 2. Navigate to My Account -> Downloads on the WPML website to download the latest version. 3. Deactivate all WPML plugins. 4. Delete the old plugin files. 5. Download fresh copies of the WPML plugins from wpml.org. 6. Upload and activate the new plugins. 7. While deactivating the WPML plugins, update other plugins like Advanced Custom Fields PRO to their latest versions. If you don't see the updates, click the "Check for updates" button in the Plugins → Add New Plugin → Commercial tab.
Please note that this solution might be irrelevant if it's 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 you still encounter issues, please open a new support ticket at WPML support forum.
Problem: The client needs to switch the WPML site key to a new account and is concerned about potential disruptions or data loss. Solution: If you're experiencing the need to switch your WPML site key to a new account, we recommend the following steps to ensure a smooth transition without affecting your site: 1. Navigate to your site's backend, go to Plugins > Add new > Commercial and unregister WPML. 2. Visit https://wpml.org/account/sites (ensure you are logged in with the new account), create a new key for your domain, copy this key. 3. Return to your site's backend (Plugins > Add new > Commercial) and register WPML with the new key.
This process should not disrupt your site settings or cause data loss. However, if this solution does not apply to your situation, or if it 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 further assistance is needed, we highly recommend opening a new support ticket at WPML support forum.
