Problem: The client needed to know how to find the word count for their site using WPML and also inquired about editing translations globally after using AI translation, specifically for handling incorrectly translated terms. Solution: We advised the client that when they are on the Translation Dashboard and select a page, they can see at the bottom the number of words that need to be translated, how many credits are used, and the exact price. Unfortunately, an estimate for the entire website is not currently available, but the client can check the estimated cost for each selected page or post.
For editing translations globally, we recommended that from WPML > Settings, the client can choose to review the translation or set specific terms and their translations in the Glossary, which will then be used in automatic translations. More details on managing glossary entries can be found here: How to Create and Manage Glossary Entries.
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 further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: You are experiencing inefficiencies in uploading images with localized filenames for SEO purposes using WPML Media Translation. You've noticed there is no automatic process for translating filenames, which makes the process time-consuming. Solution: We have considered the possibility of implementing automatic filename translation. However, after internal discussions, we decided not to pursue this feature at the moment. The main reasons are the lack of sufficient demand from our users and the potential increase in database usage due to file duplication. WPML is designed to focus on translating user-generated content like alt texts and captions while using the same media file across different translations.
If this solution does not resolve your issue or seems outdated, we recommend checking the related known issues and verifying that you have the latest versions of themes and plugins installed. If the problem persists, please open a new support ticket.
Problem: The client needed to customize the default translation batch name in WPML Translation Management, which is hardcoded as 'WPML|{lang}|{number}'. They requested a filter to change the prefix 'WPML' to a custom string like 'Help Center'. Solution: We reviewed the request and decided not to add a new filter for customizing the default translation batch name. This decision was based on the specificity of the request and the fact that it's the first of its kind in over 10 years of WPML development. Additionally, since the batch name can be manually edited before sending for translation and it does not impact the translation workflow, we concluded that the demand for this feature does not justify a new implementation at this time. However, you are welcome to implement a custom solution if necessary.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please open a new support ticket.
Problem: The client is using the 'Update internal links' feature in WPML to correct links in translated posts that incorrectly point to the original English page. Despite translating content into three languages and having a large number of posts (33,600), the process often stops or breaks around 19,600 posts, displaying an error message. The client seeks a solution to make this process run in the background without needing the admin page to remain open. Solution: We discussed three potential solutions: 1. Address the immediate issue by ensuring the 'Update internal links' process does not stop or break. 2. Tackle the underlying problem by ensuring that posts do not point to the original English page when translated alternatives exist. 3. Consider the feature request to run the process as a background task, although this might not be implemented soon. We recommend focusing on the second solution, which addresses the root cause of the issue. It is expected that internal links in other languages should automatically translate along with the content, making the 'Update internal links' button unnecessary in this scenario. If the client still prefers to pursue the feature request, we can proceed with that, but we suggest reconsidering for a more immediate resolution.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: You have a custom 'options' page created with Advanced Custom Fields (ACF) and the options are not rendering in other languages when the language is changed. You've set the mode to 'Expert' and chose 'Don't translate' because the contents of the option page don't need to be translated (e.g., phone number). However, when you switch languages, the content is missing. Solution: Currently, the functionality to disable translation for ACF option pages and ensure they render correctly in all languages regardless of the translation settings is not available. This issue has been escalated internally as a feature request. As of now, there are no plans to implement this due to limited demand, but it remains open in our internal tracker for future consideration.
If this solution does not apply to your case, or if it becomes outdated, 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. For further assistance, please contact us through the WPML support forum.
Problem: The client would like to lower the amount of HTTP requests, due to each language flag being loaded as an individual SVG file. This results in multiple HTTP requests, which increase Time To First Byte (TTFB) and initial rendering time, particularly affecting visitors on slower networks.
Solution: We have forwarded a feature request to load SVGs programatically instead of using SVG files, which is currently under revision. You can find a custom solution approach for the issue inside the comments of this ticket.
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 further assistance is needed, please open a new support ticket at WPML support forum.
