Problem: The client is experiencing issues with duplicate WPML keys showing in the Account section, with concerns about affecting translations and the correct domain representation. Solution: We recommend creating a full website backup first. After securing your backup, you can safely remove the WPML key that is no longer in use. This action will not affect your translations as they are stored in the database, not loaded from our servers. To resolve the issue of incorrect domain representation, remove both keys for the domain, generate a new PRODUCTION key, and then navigate to your site's backend > Plugins > Add new > Commercial. Here, unregister WPML from the old key and re-register it with the new key.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket.
Problem: The client was unable to remove the development site banner from their website even after marking it as a production site in their WPML account. Additionally, they were concerned about duplicate entries in the WPML account section. Solution: We advised the client to remove the old development site key from their WPML account and generate a new production site key for their domain. This can be done by visiting WPML.org > Account > Sites and following the steps to remove and generate keys. After updating the key, it's important to unregister and re-register WPML on the site's backend under Plugins > Add new > Commercial. It's also crucial to clear any caching on the site or server to ensure changes take effect. This might involve contacting hosting support or clearing caches through any installed caching plugins. For the issue regarding duplicates in the account section, a separate support ticket was created to address it specifically. You can follow the updates for this issue at this link.
If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket.
Problem: You are experiencing issues with translated posts not being found due to complex permalink structures and custom rewrite rules in a multilingual WordPress setup using WPML. Solution: We recommend modifying the timing of your redirect rules. Instead of loading your redirects on 'init', try using the 'wpml-loaded' action. This ensures that WPML's language handling is fully loaded before your custom rewrite rules are applied, which helps in maintaining the correct language directories in URLs. For more details on this hook, please visit https://wpml.org/wpml-hook/wpml_loaded/.
If this solution does not resolve your issue or 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are trying to display tags for news posts on translated pages using WPML, where the news posts use an ACF field post object for selecting 'area of expertise'. However, the tags are not showing on the translated pages. Solution: We recommend following these steps to ensure that the ACF field post object for 'area of expertise' is correctly translated and displayed: 1. Navigate to WPML >> Settings > Custom Fields Translation section. 2. Click on the Show system fields link. 3. Set the
area_of_expertise
and
_area_of_expertise
fields to Copy. 4. Re-save the default language news post. You may need to re-save all existing news posts in the default language which have tags to apply the field settings correctly.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client has a custom Gutenberg block with a heading attribute and content. The heading translates correctly when there are no nested blocks, but fails to do so when nested blocks are present, with only the nested blocks being translated. Solution: We resolved the issue by registering the custom blocks for translation. Here are the steps we recommend you follow: 1- Navigate to WPML-> Settings-> Custom XML tab. 2- Add the following code:
3- Save the changes. 4- Edit the page in the default language. 5- Click the Update button. 6- Update the translation using the translation editor. For more information on registering blocks for translation, please check this guide.
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 the issue persists, please open a new support ticket.
