Problem: The client is experiencing an issue where the language code in the URL does not change from 'en' to 'en-gb' as specified, resulting in incorrect URLs. Additionally, there is no option to edit the language as the locale already exists. Solution: We recommend creating a new custom language with the desired language code '/en-gb/'. If you encounter a message stating that the locale (e.g., en_US) already exists, this indicates it is assigned to another language, typically the default English language in WPML. To assign the locale to your custom language, follow these steps: 1. Navigate to WPML → Languages and ensure the default English language is active. 2. Edit the English language and temporarily change its locale to a different, unused value (e.g., en_EN). 3. Save the changes. 4. Add your custom language and assign the desired locale to it. For more detailed instructions, please visit: Editing WPML's Languages Table
If the solution provided 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 issues persist, please do not hesitate to open a new support ticket for further assistance.
Problem: You are encountering an issue where the default locale hreflang already exists, which is preventing the correct hreflang setup. Solution: If you're experiencing this issue, we recommend checking if the English language is already added in your WPML settings. Please navigate to WPML --> Languages --> Add language and ensure that English is properly configured. Additionally, we have prepared a video tutorial to assist you further: Video Tutorial.
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 issue persists, please open a new support ticket at WPML Support Forum for further assistance.
Problem: You deactivated the German (Switzerland) language on your site, but translations associated with this language still exist in your database. Solution: 1. Re-add the 'German (Switzerland)' language using the same language code. 2. Navigate to Templates -> Filter by 'German (Switzerland)' -> Delete the templates. 3. Go to WPML -> Languages -> Edit languages link -> Remove 'German (Switzerland)'. 4. Double-check if the issue has disappeared.
If this solution does not resolve your issue or seems outdated, 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 problem persists, please open a new support ticket.
You are trying to resolve an issue where hreflang tags have disappeared from the source code on your website.
Solution:
If you're experiencing this issue, we recommend you try the following steps:
1. Navigate to WPML >> Languages >> SEO Options. 2. Ensure that the option 'Display alternative languages in the HEAD section' is enabled. 3. If it was disabled, enable it and then clear all types of caches including plugin, server, browser, and CDN caches. 4. After performing these steps, check if the hreflang tags are restored on your website.
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 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.
