Problem: The client needed to change the WPML plugin key from a development key to a production key before transferring their website to a production domain. Solution: 1. We instructed the client to create a new production key by visiting https://wpml.org/account/sites/. 2. After the migration to the production domain, the client should go to their site's backend, navigate to Plugins > Add New > Commercial, unregister WPML using the old key, and then re-register WPML with the new production key.
If this solution does not apply to your situation because it might be outdated or not relevant to your case, 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. If further assistance is needed, please contact us in the WPML support forum.
Problem: The client's website does not translate Elementor widgets, including a newsletter and some banners, despite using custom translation code. Solution: We recommend registering the custom widgets for translation. This is necessary if the widgets are custom or added by a theme or a plugin. Here are two guides to assist with this process:
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your specific case. If the issue persists, 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 you still need assistance, please do not hesitate to open a new support ticket. You can do so here: WPML support forum.
