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.
