Problem: The client is experiencing an issue where the post category has been translated, but the translated blogs still use an untranslated path. Solution: If you're encountering a similar issue, we recommend following these steps: 1. Ensure you have a full backup of your website for safety. 2. Navigate to Settings > Permalinks and re-save your options. 3. Go to WPML > Taxonomy Translation, select Categories, and check if there's an option to synchronize them. 4. Still in WPML > Taxonomy Translation, select Categories and verify if the slug is translated by clicking on the pencil icon for the mentioned category.
If these steps do not resolve your issue, or if the solution seems 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: You are trying to translate the payment gateway description on your site using WPML, but the translation does not appear on the front-end. Solution: This issue might be due to a compatibility problem. First, ensure you have followed the steps outlined in finding strings that don't appear on the string translation page. If the issue persists, you may need to add language configuration for plugin or theme options strings in WPML >> Settings >> Custom XML Configuration tab. Consider implementing the workaround suggested in these tickets after a full site backup:
After applying these changes, clear all types of caches and check if the issue is resolved.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum.
Problem: The client is trying to sync their staging site with the production site and encountered an issue where WPML was unable to update records with the new URL, displaying an error: 'Error with moving translation information to new URL'. Solution: 1. If you're still seeing the migration banner, please check again to see if the issue persists. 2. Verify the URL from which you are migrating the site. 3. Navigate to WPML->Support->Troubleshooting in your WPML dashboard. Look for the option 'Force-enable WPML’s Advanced Translation Editor' near the bottom of the page. If it's available, click and run it, then check if the problem is resolved.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: You've added Hindi as a language through WPML's Add Language option and are trying to enable automatic translation for Hindi. However, you encounter an error stating: 'The following target languages do not support automatic translations: Hindi. To enable automatic translation map them to known languages.' Despite mapping it to Hindi, the settings are not saved. Solution: This issue occurs when the translation engines that support Hindi are disabled. We recommend visiting this link to find which translation engines support Hindi and then activate them in WPML -> Settings.
If this solution does not resolve your issue or seems irrelevant due to being 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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client created three new user roles: shop_manager, content_manager, and general_manager, all requiring full translation capabilities. However, they encounter an issue where half of the products display a message 'You can only edit translations assigned to you' when attempting to edit a translation. Solution: Take note, that the workflow for non-admin users usually is as follows: - Assign the user as 'Translation Manager' and as 'Translator' for selected language pairs at WPML > Translation Management > Translators. - This setup allows the user to create jobs at WPML > Translation Management > Dashboard and access them at WPML > Translations.
To resolve this, we recommend two approaches: 1) Use a third-party plugin to adjust user roles to grant similar capabilities as an admin. A suitable plugin for this purpose is the User Role Editor. 2) Alternatively, use our Toolset Access plugin for a more customized solution.
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: You are trying to complete the translation of your forms using WPML, but you are encountering an issue with Font Awesome glyph icons in HTML. Strings with glyph icons are not saved, and the translation is not 100% completed, leaving some English text on translated pages/forms. Solution: 1. Increase the PHP memory limit to at least 512M. You can do this by adding the following code to your
wp-config.php
file just above the line that says '/* That's all, stop editing! Happy blogging. */':
2. Enable the previous version of the Advanced translation editor. Go to the advanced translation editor, click the gear icon on the top right to access settings, enable the 'Previous version' option, provide feedback, and submit to reload the page. 3. Apply the fix for a known issue with Gravity Forms by following the steps outlined here: https://wpml.org/errata/gravity-forms-merge-tags-are-available-for-translation/
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 at WPML support forum.
