Problem: The client was disconnected during a support chat and needed to reconnect with the supporter, Christian. The issue was related to accessing a specific URL during the chat. Solution: We advised the client to modify the URL by including /wp-admin at the end. Instead of using the URL
. This change should lead to a message confirming that all product categories have been re-saved, as expected.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is unable to create a fully-functioning staging site replica of their production site using 'subdomain-like' URLs to distinguish languages without changing their hosting subscription. Solution: We recommend using the free version of the Duplicator plugin to clone the production site to a staging environment. After importing the site into the staging environment, the client should change the Language URL format to ensure it functions correctly. This approach avoids the need to upgrade the hosting plan.
If this solution does not apply to your situation, 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: The client was experiencing issues with saving and creating multi-language products with several hundred variations, which was taking a long time to complete. Solution: 1. We confirmed that the issue had been tested on a site clone and the changes were working. 2. We instructed the client to edit a specific file by navigating to "Plugins -> Plugin Editor" and overwriting the mentioned code lines, emphasizing the importance of making a backup before making any changes. 3. We informed the client that we could not provide an ETA for the release that includes these changes, as the priority might be lower due to the lack of similar reports from other clients. 4. We updated the files on the client's site and asked the client to try saving the product again, noting that it should now take around 30 seconds without getting "stuck".
If you're experiencing a similar issue, we recommend you try the steps mentioned above. However, please be aware that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking 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 with us.
