Problem: After upgrading WPML and WooCommerce, the client cannot find the button for WooCommerce Multilingual & Multicurrency with WPML to translate new products. Solution: First, ensure that the WooCommerce Multilingual plugin is still active. If it is active, follow these steps: 1. Make a full backup of your site. 2. Add the following code to the functions.php file in your theme folder:
function wpmlsupp_1706_reset_wpml_capabilities() {<br /> if (function_exists('icl_enable_capabilities')) {<br /> icl_enable_capabilities();<br /> }<br />}<br />add_action('shutdown', 'wpmlsupp_1706_reset_wpml_capabilities');
3. Load any frontend page once. 4. Remove the code from the functions.php file and check if the WooCommerce Multilingual & Multicurrency button reappears in the backend.
If this solution does not resolve the issue or seems irrelevant due to updates or different circumstances, we recommend checking the related 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.
Problem: The client is using an old version of WPML and has lost the translation of the main menu in English. The '+ button' appears instead of the 'edit/pencil icon', and the client is unable to reconnect the existing English menu translation.
Solution: 1. We recommend updating to the latest version of WPML to see if the issue has been resolved in a more recent update. 2. Create a staging site to safely perform the update without risking the live site. 3. Make sure to back up the site before proceeding with the update. 4. After the backup, disable all other plugins and switch to the default WordPress theme. 5. Update WPML via the Plugin Manager on Plugins -> All Plugins in the 'commercial' tab. 6. Reactivate each plugin one by one and update them as needed.
Please note that translations are stored in the database and will not be lost during the plugin update. However, always ensure you have a complete backup before making any changes.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we highly recommend checking the related 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 with us.
