Problem: The client is unable to manually translate slugs in WordPress using WPML. Specifically, changes to slugs in the Classic Editor revert to the translated title after saving, and the WPML Translation Editor does not show the slug as a translation option for posts that have already been translated. Solution: First, ensure that all plugins, especially WPML, are updated to the latest versions. The issue might be occurring due to outdated plugins. If the problem persists after updating: 1. For new content, ensure the WPML setting is on 'Translate' to include the slug in the translation. This setting should allow manual slug translation when creating new translations. 2. For existing content, change the title in the original language, save it, then open the WPML Translation Editor and manually translate the slug. 3. If the slug still does not save correctly, it might be necessary to check the specific characters used in the slug, as some might not be supported or could be causing issues.
If these steps do not resolve the issue, or if the solution seems outdated or irrelevant to your specific case, please visit the WPML support forum to open 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.
Problem: The client was unable to translate the "Read more" text in a WP Post Query Block using the Advanced Translation Editor (ATE). The text was not appearing as translatable in the ATE, and any changes made in the classic editor were reverted when the ATE was used.
Solution: We recommended adding a custom XML configuration to make the "Read more" text translatable. Here are the steps we suggested: 1. Navigate to WPML -> Settings -> Custom XML Configuration. 2. Add the following code and save:
3. Make a minor edit to the original page to trigger a "needs update" status for the translation. 4. Open the translation editor to check if the string now appears for translation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problem persists, please open a new support ticket at WPML support forum.
Problem: You are experiencing issues where fully translated text is not appearing on the front end of your website after migration from a staging to a production site. Additionally, links in the Advanced Translation Editor still point to the staging site, despite having completed translations. Solution: If you find that the Translation Management is blocked or not functioning correctly on your production site, we recommend the following steps: 1. Navigate to WPML → Support. 2. Click on the Troubleshooting link. 3. On the Troubleshooting page, click the button labeled Force-enable WPML’s Advanced Translation Editor. This action should help resolve the issue with the translation editor and ensure that your translations display correctly on the front end.
Please note that this solution might be outdated or not applicable to your specific 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're trying to translate content inside a Custom HTML Block in WordPress using the Advanced Translation Editor and find that the Custom HTML Block is not available for translation, this is because the Advanced Translation Editor is not designed for translating non-visual elements like HTML. It automatically copies the markup over to the translation, allowing only the included text to be translated. Solution: We recommend using the Classic Translation Editor, which supports HTML translation. You can learn more about using the Classic Translation Editor here. Alternatively, you can switch to the WordPress Editor for translating this content. This allows you full control over the HTML. For guidance on how to use different translation editors for different pages, please visit this link.
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. Should you need further assistance, please do not hesitate to open a new support ticket here.
Problem: You are trying to register a WPML site key but receive an error message stating 'Unable to register: Site key not matching', even though the site key matches. Solution: This issue often occurs when the site URL registered in your WPML account does not match the actual site URL (e.g., differences in using 'www'). To resolve this, follow these steps: 1. Log in to your WPML.org account and go to the Sites page. 2. Delete the existing site key. 3. Log in to your site's dashboard, navigate to Plugins > Add New Plugin > Commercial tab, and click the Unregister WPML from this site link if available. 4. Click the Register WPML link. 5. Click the Get a key for this site link to generate a new key. 6. Copy and paste the new key into the input box and press the Register button. 7. Take a backup of your site and update WPML plugins to the latest version.
If this solution does not apply to your case, or if it seems outdated, we recommend checking the related 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 open a new support ticket.
Problem: The client was experiencing issues with not all ACF fields appearing in the WPML Translation Editor despite being set up identically. They were unsure how to ensure all fields are included in the translation process and faced difficulties with saving the 'Same fields across languages' setting in WPML. Solution: 1) Ensure that the 'Same fields across languages' setting is selected for the ACF field groups when using the WPML Translation Editor. This setting should be saved by clicking 'Save Changes' in the ACF UI. 2) Set the ACF Field Groups to 'Not translatable' in WPML > Settings > Post Type Translation to avoid translation issues. If there were previous translations for these field groups, they should be removed. 3) Do not use the same field name more than once within your ACF groups to prevent conflicts. 4) Always use the WPML Translation Editor or the WordPress Editor consistently for translations. Mixing these methods can lead to loss of data. For detailed guidance on setting up ACF fields for translation with WPML, refer to the documentation here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to translate a custom post type archive page using a template file in a child theme, but the translated page appears differently than the original language template. Solution: The issue is related to the specific archive template in your child theme, located at
themes/monochrome-pro/archive-trustee.php
on line 83. If this functionality was custom-built and not provided by the theme authors, it is recommended to consult with a certified WPML developer who can help adjust the code. You can find a developer here: https://wpml.org/contractors/.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is trying to translate the 'Roles:' string from the Genesis theme, which is added via the functions.php file. The string is not appearing in WPML's String Translation search even after scanning the theme and child theme. Solution: 1. Enable the 'Look for strings while pages are rendered' option in WPML >> String Translation page. 2. Visit the page where the string appears on the front end. 3. Return to the WPML >> String Translation page and search for the 'Roles:' string. 4. Translate the string and then disable the auto-registration option. If this does not resolve the issue, install the String Locator plugin (https://wordpress.org/plugins/string-locator/) and search for the text in theme or theme bundled plugins files. Ensure the 'Roles:' string is wrapped in the gettext function, as detailed in the documentation (https://wpml.org/documentation/support/translating-the-theme-you-created/#wrap-all-texts-in-gettext-calls). Alternatively, replace the existing code in functions.php with:
Then, scan the theme again and translate the 'Roles:' string via WPML >> String Translation page.
If the solution provided here 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client needed to correct the display of the Punjabi language in the WPML language switcher. Solution: We recommended the following steps: 1. Navigate to WPML-> Languages-> Edit Languages. 2. Change the Punjabi's language Translation (Punjabi) to ਪੰਜਾਬੀ. 3. Click Save. After these changes, we advised checking the language switcher on the front end to ensure the display is correct.
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.
Problem: You are trying to translate words embedded in HTML tags within a .php template for a custom post type, which are not editable from the WordPress dashboard. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Wrap the strings in the gettext
Apply this procedure for all hardcoded strings you wish to make translatable. 2. Scan the theme or plugin from the WPML > Theme and plugins localization page where you updated the code. 3. Go to the WPML > String Translation page, search for the string, and add the translation. For more detailed instructions, please visit our documentation on translating texts wrapped in gettext calls.
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 you still need assistance, please open a new support ticket at WPML support forum.
