Problem: The client reported that the language switcher was not appearing on newly translated posts on their website, despite being visible on other parts of the site.
Solution: We recommended several steps to troubleshoot and resolve the issue: 1. Verify that the WPML Language Switcher is enabled in WPML settings and configured to appear in expected locations such as menus, widgets, or footers. 2. If the switcher is intended to appear in navigation menus, ensure it is added and positioned correctly within the menu settings. 3. For placement in sidebars or other widget areas, check that the 'Language switcher as a widget' option is enabled and the widget is added to the desired area. 4. Check Elementor templates used for headers, footers, or specific post types to ensure the WPML Language Switcher widget is included and properly configured. 5. Clear site and browser cache after making changes to check if the issue is resolved. 6. If the problem persists, particularly with specific posts, ensure that the 'Links to translation of posts' option is enabled in WPML settings and check the Elementor template settings for those specific posts.
If these steps do not resolve the issue or if the solution seems outdated or not applicable to your case, we highly recommend opening a new support ticket. Additionally, please check 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. For further assistance, you can also visit our support forum at WPML Support Forum.
Problem: The client is working on a development site with IP restrictions and is unable to allow WPML plugin to connect to wpml.org for updates due to network or security settings. Solution: We recommend the following steps to resolve the connection issues: 1. Log in to your WPML.org account and navigate to the Sites page: https://wpml.org/account/sites/ 2. Delete the existing site key. 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. Click the Register WPML link and then the Get a key for this site link. 5. Copy the newly generated key, paste it back into the input box, and press the Register button. 6. Take a backup of your site and update WPML plugins to the latest version. If the issue persists, try the following: - Go to WP Dashboard Menu >> Updates and press the "Check again" link. - Contact your hosting service provider and ask them to whitelist the following URLs: - wpml.org - cdn.wpml.org - api.wpml.org - api.toolset.com - cloudfront.net For more details, refer to this documentation: https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/
If these steps do not resolve your issue, or if the solution 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 needed, please open a new support ticket for further assistance.
Problem: You are trying to register your site using WPML but cannot find where to enter the product key. Solution: If you are experiencing this issue, we recommend following these steps: 1. After installing WPML on your site, you should be able to add or generate a key in the setup wizard. 2. If WPML is already installed, you can register it by navigating to Plugins > Add new > Commercial and clicking the "Register WPML" button.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and verify the version of the permanent fix. Also, confirm that you have installed the latest versions of themes and plugins. If you still need assistance, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client needed a way to set their Spanish translated pages to 'noindex, nofollow' without unpublishing them. Solution: We recommended two approaches: 1. Using Yoast SEO to set 'noindex, nofollow' on a page-by-page basis: - Edit the page in the main language. - Switch to the secondary language using the admin top bar. - In the Yoast SEO section, disable the options for indexing. Yoast SEO settings screenshot Note: This action will switch from the advanced translation editor to the WordPress editor for that translation. 2. Adding code to the theme's header file to apply 'noindex' globally to all pages in Spanish:
The client should replace 'es' with the appropriate language code if needed.
If the provided solution does not apply or is outdated, or if further assistance is needed, we highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If the issue persists, please open a new support ticket at WPML Support Forum.
Problem: The client's company name 'L&W Supply' is incorrectly translated by the computer as if 'supply' were a verb, resulting in incorrect translations like 'PRODUCTOS DE SUMINISTRO DE L&W' instead of 'PRODUCTOS DE L&W SUPPLY'. Solution: We recommend adding the company name 'L&W Supply' to the translation glossary. This will instruct the translation engine to treat 'L&W Supply' as a non-translatable term, ensuring it remains unchanged in the translation. You can find the steps to create and manage glossary entries in our documentation:
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If after checking the 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, you still encounter issues, we encourage you to open a new support ticket. For further assistance, please visit our support forum: WPML support forum.
Problem: The client was experiencing an issue where posts were not displaying unless one post was translated, even though the WPML settings were set to 'Translatable - use translation if available or fallback to default language'. The posts were sorted by a custom taxonomy and needed to be visible in the Spanish translation without being translated, as they linked to primarily English content.
Solution: We resolved the issue by adding the parameter
'hide_empty' => false
to the
get_terms()
function in the custom WP_Query. This allowed terms with no posts translated into the secondary language to be displayed.
$terms = get_terms(array(
'taxonomy' => $taxonomy_slug,
'child_of' => $parent_term_id, // Specify the parent term ID
'hide_empty' => false
));
If you're experiencing a similar issue, we recommend trying this solution. However, 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, 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 with us.
