Problem: The client was trying to delete English translations for posts following the instructions from the WPML documentation but encountered warnings not mentioned in the documentation. Solution: We recommended the client to edit the default language post in Edit mode, switch to the English language using the admin language switcher, and then choose the 'None' option from the 'This is a translation of' dropdown. This action should unlink the English post from any other post, allowing it to be safely deleted.
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 problems persist, please open a new support ticket.
Problem: The client wants the language switcher in the nav bar to display the name of the other language instead of the active language. The site uses Gutenberg blocks, and the switcher currently shows only two letters representing the active language (German), but the client wants it to display the name of the other language (French). Solution: We recommend two methods to achieve this: Method 1: Hide the current language using CSS 1. Edit the Language Switcher block. 2. Set the "Layout" to list. 3. Add the following CSS in the custom CSS section of the theme:
Method 2: Add language switcher using shortcode 1. Go to the WPML >> Languages page. 2. Enable the Custom Language Switcher. 3. Replace the language switcher block with a shortcode block and use the following shortcode:
If these solutions do not resolve your issue or if they seem 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: The client is experiencing an issue where the translation counter in WPML does not reach 100%, preventing the saving or completion of translations. This is accompanied by a spinning wheel at the bottom of the text on two posts. Solution: We recommend trying to switch to the older version of the Advanced Translation Editor by clicking on the cog wheel icon in the top right corner to see if this resolves the issue. If the problem persists, we may need to examine the website more closely. For this, temporary access (WP-Admin and FTP) to a test site where the problem has been replicated would be required. It is crucial to ensure that you have a backup of your site to prevent any potential data loss. We suggest using the UpdraftPlus plugin for your backup needs.
If this solution does not apply to your case, or if it seems outdated, please check the 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. If issues persist, we highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing an issue where their site warns that there are not enough credits for automatic translation, despite having a sufficient amount of credits assigned in their WPML account. Solution: If you're encountering a similar issue, it might be due to the automatic translation account ID being reset or changed, which can happen if WPML is uninstalled or WordPress is reinstalled. Here are the steps we recommend: 1. Visit your WPML account page at https://wpml.org/account and use the "add/remove credits" button to manage your credits. 2. If necessary, remove the existing site key and create a new one by following these steps: - Go to https://wpml.org/account/sites/ - Remove the current site key and generate a new one. - Navigate to your website's backend > Plugins > Add new > Commercial. - UNregister WPML from the old key and REregister it with the new key. 3. Reassign the credits to your site by following the guide at https://wpml.org/documentation/automatic-translation/how-to-assign-automatic-translation-credits-to-your-sites/.
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 needed, please do not hesitate to open a new support ticket for further assistance.
Problem: You are using WPML to translate content from German to French, and some images are not displaying on the translated pages. The issue is due to broken image links where the 'uploads' folder is missing from the URL. Solution: We recommend checking the format of your image links to ensure they include the 'uploads' folder. This problem might be related to a known issue with SVG support when WPML Media is activated, which strips the 'uploads' folder from the SVG image URL. For a workaround, please visit the following documentation: WPML Errata on SVG Support.
If this solution does not apply because it is outdated or not relevant 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 issues persist, please open a new support ticket at WPML Support Forum.
Problem: The client has an issue where a translated blog post is not displaying the translation on the frontend, even though the backend shows everything as 100% translated. Solution: If you're experiencing a similar issue where your translated content is not appearing on the frontend, we recommend you try the following steps: 1. Edit the page in the default language. 2. Add "V2" to the page's title and update the page. 3. Remove the "V2" from the title and update the page again. 4. Update the translation of the page.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, we suggest opening a new support ticket. We also highly 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 you need further assistance, please don't hesitate to contact us on the WPML support forum.
Problem: The client needed to add additional text to the translated page that indicates a download link leads to an untranslated PDF file. This text should only appear in the French translation. Additionally, the client wanted to use non-breaking spaces in the French translation to adhere to the typographical norms of the language.
Solution: 1. To add additional text to the translated page, we recommend using the manual translation approach. You can find detailed instructions on how to apply manual translations for specific pages here: Using different translation editors for different pages.
2. Regarding the use of non-breaking spaces in the French translation, if the standard translation editor does not meet your needs, you might consider using the HTML widget in Elementor. This issue has been discussed in a forum post, which could provide a solution: Elementor HTML widget content does not appear in advanced translation.
If these solutions do not seem relevant to your situation, please open a new support ticket with us, and we will be happy to assist you further.
Problem: The client migrated a development site to a live server using Duplicator Pro and encountered an error stating 'WPML Media is enabled but not effective. It requires WPML in order to work.' Despite the site being registered in the WPML account, the plugin seemed to require re-registration. Additionally, the client was concerned about a list of errors after migration.
Solution:
1. We accessed the site's admin area and deactivated/activated the WPML Media plugin, which resolved the error message. The client had LiteSpeed Cache plugin installed, which might have been the cause of this issue.
2. We advised the client that the list of errors showing on the page "wp-admin/admin.php?page=wpml-tm-ate-log" could be ignored as in this case they were related to the site transfer process.
3. We noticed that the WP memory limit was below WPML's minimum requirements and recommended increasing it.
If this solution doesn't look relevant, please open a new support ticket at WPML support forum.
