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.
Problem: The client is experiencing an issue where the PHP
date()
function is not displaying dates in the correct language on their Spanish translation page. The dates are being output with the data-date attribute set to "1970-01-01" instead of the correct effective date. The client has custom fields for dates that are set to COPY, and while the effective date is displayed next to the post title, the data attribute in the HTML is incorrect.
Solution: We understand that the issue arises because the PHP
date()
function is using the server's locale to generate month names, which may not be translated by WPML's String Translation. This feature is intended for static strings and might not apply to dynamic content such as PHP-formatted dates. To translate month names and dates in WordPress using WPML, additional steps or configurations might be necessary, such as using WordPress-specific functions or hooks to localize the date strings. We found a solution on StackOverflow that could be helpful:
Please note that support for issues arising from custom coding is beyond our support scope. If you require assistance with custom coding, consider hiring a professional developer who specializes in customizing WPML and its extensions from https://wpml.org/contractors/.
If this solution is not relevant to your case, because it's outdated or not applicable, we recommend opening a new support ticket. We also 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 need further assistance, please do not hesitate to contact us in the WPML support forum.
Problem: The client has a Custom Taxonomy called 'Product Categories' and posts in a Custom Post Type called 'Manufacturing Price Updates' that are grouped by these categories. The client wants to display the posts in the Spanish version of the page with Spanish category names without converting the posts themselves to Spanish. Solution: We recommend translating the categories at WPML > Taxonomy Translation. Here's a guide to help you: Translating Post Categories and Custom Taxonomies. Additionally, the posts need to exist in the second language. You can either translate the posts or duplicate them. To duplicate posts in bulk, use the Dashboard at WPML > Translation Management. Here's a guide for that: How to Duplicate Pages and Posts in Bulk. Duplicates will display the same content in all languages and update automatically when the original content is edited.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If so, 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.
There was an error: { "keywords": "WPML, string translation, gettext, custom theme, hardcoded strings", "summary": "Problem:
The client needed to translate hardcoded English strings in a custom theme to Spanish, such as a search box placeholder and button text, and was unsure how to replace these values efficiently.
Solution:
1. We suggested enabling the \"Look for strings while pages are rendered\" option in WPML > String Translation, visiting the page with the string, and then searching for the string in WPML > String Translation.
3. We explained that for WPML to recognize strings, they need to be wrapped in a gettext call. We provided an example of how to wrap strings and a link to find the theme's text domain:
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 with us." }
Problem: The client reported that their Spanish homepage was redirecting to the default language homepage instead of staying on the Spanish version. Solution: We suggested that the client should try accessing the website from a different browser or device to rule out the possibility of a caching issue on their current browser. If you're experiencing this, we recommend you try the same steps to see if it resolves the issue.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please don't hesitate to open a new support ticket with us.
