Problem: The client is experiencing issues with widgets being disorganized after changing the default language. They are unable to translate widgets independently, including headers and footers. Additionally, there are problems translating WooCommerce settings for emails, and the shop page layout is broken after changes made with WPML. Solution: For translating WooCommerce emails that have been customized or newly created, follow the steps provided in the WPML documentation on translating WooCommerce emails.
If you're experiencing similar issues with widget translation or layout problems after using WPML, we 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 solution provided here is outdated or not applicable to your case, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where the site key does not match when trying to register their WPML product on a multisite network. Solution: If you're encountering a similar issue, we recommend registering your main site first as the same site key applies to all subsites in a multisite network. There is no need to register each subsite separately. Follow these steps: 1. Delete all existing site keys. 2. Create a new site key (just one for the entire multisite). 3. Register the multisite with this new key. 4. Assign credits to the newly created site key. For detailed guidance on registering WPML in a multisite setup, please visit WPML Multisite Registration Documentation. Additionally, if you need to connect a subsite to the main site using a migration code to share its credits, please refer to How to Connect Your Sites.
Please note that this solution might be irrelevant if it's 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 issue persists, please open a new support ticket.
Problem: Sie finden die Option nicht mehr, um eine Website an einen Kunden zu übertragen. Solution: Wenn Sie diese Option suchen, beachten Sie bitte, dass wir diese Möglichkeit am 13. Januar eingestellt haben. Daher steht diese Option nicht mehr zur Verfügung. Wir empfehlen, dass Ihr Kunde eine eigene Lizenz erwirbt. Weitere Informationen finden Sie in unserer Dokumentation:
Falls diese Lösung für Sie nicht relevant ist, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Problem: The client changed their website URL from https://dev.lcm.org.my to https://lcm.org.my and forgot to copy the migration code, resulting in a 404 error when trying to access the old URL. Solution: We resolved the issue on the client's site and restored 208 credits to their WPML.org account. Here are the steps we recommend if you're experiencing a similar issue: 1. Log in to your site and navigate to Dashboard >> Plugins >> Add new >> Commercial tab. 2. Click on the Get a key for this site link: https://wpml.org/account/sites/?add=https://lcm.org.my 3. This will generate a Key for your site. You can also assign the credits using that popup. Confirm the assigned credits from WPML >> Translation Dashboard > Translation Tools. 4. Copy the key, paste it into the input box, and press the Register button.
If this solution does not apply to your case, 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: You have translated a new article using WPML, but it is not published yet. Solution: If you're experiencing this issue, we recommend checking if you are using the "Translate Everything" mode on the WPML > Translation Dashboard. Ensure that the WPML's automatic translation setting is not set to "Review translations before publishing" at WPML > Settings > Automatic Translation setting "Wait for review". Also, verify if you have any pending reviews at WPML > Translations. It's possible that, based on your settings, the translations are still saved as drafts.
Additionally, if your original content was a draft when you started the translation job, the completed translation would also be saved as a draft by default. You can control this behavior in WPML > Settings > Translated documents options.
If these steps do not resolve your issue, it 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 at WPML support forum.
Problem: The client deleted a file from the media library, but it still appears in Media Translation. Despite deleting all translations, one remains visible. Solution: We recommend checking in WPML > Languages > Site Languages to see if there is an active dialogue about old translations from inactive languages. If such a dialogue exists, use it to remove those contents. Additionally, ensure that the media is indeed removed from the media library by setting the admin bar language selector to "All languages". If the issue persists, we suggest visiting our support forum for further assistance.
Please note that this 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 continues, please open a new support ticket.
