Problem: You are trying to use the 'pay as you go' feature, but it incorrectly adds a non-existent non-www website version to the list, even though the migration code comes from a www website. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Disconnect the site from where you connected it. 2. Go to Plugins → Add New and click the Commercial tab. Then click 'Unregister WPML from this site'. 3. Once the page loads, click on 'Register WPML'. You will see a message asking you to enter the site key. Click on 'Get a key for this site'. 4. In your WPML account, complete the site key wizard and set it to 'Production site'. 5. Copy your new key and paste it in the Commercial tab. Afterward, you can delete your old site key in the WPML account. 6. Try to connect the sites again.
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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client is unable to add a site key in the backend to register WPML. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Log in to your WPML.org account and navigate to the Sites page. 2. Delete the existing site key if it exists. 3. Log in to your site, go to the Dashboard >> Plugins >> Add new plugin >> Commercial tab and click the Unregister WPML from this site link if it exists. 4. Then click the Register WPML link. 5. Click the Get a key for this site link. 6. It will generate the Key for your site. 7. Copy the key, and paste it back into the input box, and press the Register button.
If these steps do not resolve the issue, please provide more details about the problem, such as whether you are unable to see the input box to enter the site key, or if the input box is visible but disabled.
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 the issue persists, please open a new support ticket.
Problem: You are trying to get strings from the Elementor plugin to show in the Advanced Translation Editor (ATE), but they are not appearing as expected. Solution: If you're experiencing this issue, it might be because you are using a global widget that has not been translated. We recommend translating this global widget to see if that resolves the problem. For more details on how to translate global widgets, you can visit our documentation here: Translating Widgets.
If this solution does not apply to your case, or if it seems outdated, please check the 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 the issue persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client reported an issue where a URL with a language prefix that does not match any of the activated languages in WPML (Austrian German 'de-at') was added and could not be removed. This URL was incorrectly listed in the sitemap.
Solution: We resolved the issue by manually removing the erroneous entry from the database. Specifically, in the posts table, there was a leftover entry for 'test-pagew'. After deleting this entry, the URL no longer appears in the sitemap.
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. If the problem persists, please do not hesitate to open a new support ticket with us for further assistance at WPML Support Forum.
Problem: You are experiencing an issue where the URL is not translatable despite having URL translation activated in WPML settings. Solution: 1. Ensure that the option for URL translation is activated for newly created content. If you are working with existing content, try the following steps: - Edit the title or permalink slug on the original content. - Reopen the WPML Translation Editor to see if the changes take effect. 2. Check if the page in other languages is set as "Duplicate". If so, remove this option and try translating the URL again. 3. If the issue persists, make minor edits to the primary language page. This might trigger the system to recognize the changes and allow for URL translation. For a visual guide on how to do this, you can watch this screen recording: https://go.screenpal.com/watch/cZQ6ImVRJZW
If these steps do not resolve your issue, or if the solution seems 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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: If you're unable to delete deactivated content in WPML, this might be due to a known issue. Solution: We recommend performing a full site backup before proceeding with any changes. After backing up, try deleting the Post Category and Tags terms in Korean and Portuguese (Portugal) languages. This workaround is suggested in our errata, which you can review here: https://wpml.org/errata/taxonomies-are-not-deleted-with-the-delete-content-from-database-option/.
If this solution does not resolve your issue or seems irrelevant due to being 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. Additionally, please feel free to open a new support ticket for further assistance at WPML Support Forum.
