Problem: The client experienced an issue with media translation where the translated text skipped to the next picture, affecting multiple images sourced from a dummy page. Solution: We explained the difference between 'connected media' and 'copied media'. 'Connected media' allows changes in Media Translation to affect all languages, whereas 'copied media' does not. To address the issue: 1. Disable the 'Automatically detect best options for translating image texts' in WPML > Settings > Media Translation if you prefer not to use this behavior. 2. For images already marked as 'Copied Media', translate the Alt Text through the Advanced Translation Editor while translating the page. 3. Test by adding new images to a new page to see if they are no longer marked as 'copied media'.
If this solution does not resolve your issue or seems outdated, we 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 reported that their media library shows different numbers of items per language in WPML, specifically concerning PDF files uploaded to a custom meta field on a WooCommerce product that has been translated. Solution: We recommended checking the settings under WPML > Settings > Media Translation to ensure that the media synchronization feature is enabled, which helps in auto-detecting media that needs to be synced across translations. If the feature is disabled, there is an option for manual setup where the client can select all checkboxes for existing content and start the media synchronization process manually.
Additionally, we advised verifying the translation settings for the custom field named 'product_sheet' under WPML > Settings > Custom Fields Translation. If it is set to 'Ignore', it will not be translated. We suggested setting it to 'Copy' to use the same file across translations or 'Translate' if alternative files are uploaded for other languages.
If these steps do not resolve the issue, we offered further assistance by requesting admin access to take a closer look, ensuring that the client creates a backup before providing access.
For more detailed guidance, please refer to our documentation on Media Translation.
If the solution provided here does not apply or is outdated, we recommend opening a new support ticket. We also advise checking related known issues at 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 are noticing a large quantity of duplicated images in your media library and are concerned about performance issues. These duplicates appear in the English tab and are not assigned to anything. Solution: The duplication of entries in the media library is a normal behavior when using WPML, as it creates one entry per language for each media file to ensure that media appears correctly in all languages. However, WPML does not duplicate the physical media files but creates database connections for the necessary language information. To manage this efficiently, we recommend enabling the automatic detection of media for translation under WPML > Settings > Media Translation. This setting helps WPML to duplicate media texts only when necessary and during translation, thus avoiding unnecessary database space usage and ensuring that the correct texts are sent for translation. If you disable this option, you will need to manage media settings manually, which might lead to unnecessary duplication and potential issues in the Translation Editor and on the front-end. For more detailed guidance, please visit: WPML Media Translation documentation. Additionally, if you are looking to clean up your media library from previously duplicated entries, you might consider using a plugin like Media Cleaner. Ensure you back up your site before running any cleanup processes.
If this solution does not apply to your situation, 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: You are concerned about how browser language redirection might affect Google indexing and whether using separate domains for each language would resolve this issue. Solution: We recommend understanding that interactions with Google indexing can occur regardless of the URL format you choose in WPML. Specifically, automatic redirection based on browser language can influence how search engines crawl and index your site. For a detailed explanation, please review our documentation on how browser language redirection affects Google indexing: https://wpml.org/documentation/getting-started-guide/language-setup/automatic-redirect-based-on-browser-language/how-browser-language-redirect-affects-google-indexing/
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 experiencing issues where content translated in WPML does not appear on the frontend, despite being visible in edit/preview mode. This includes Elementor sections/templates not showing translated content on the frontend and the WooCommerce Checkout page not displaying translations correctly. Solution: First, ensure that all content within Elementor is saved in the
_elementor_data
custom field. This is crucial for the translations to apply correctly on the frontend. If you've confirmed this and the issue persists, follow these steps: 1. Use Elementor's Tools to Regenerate Files & Data. 2. Utilize WPML's Troubleshooting options to clear cache and sync content. 3. Verify that all Elementor Templates are set as Translatable. 4. Confirm the correct language URLs are in use (e.g., /nl/ for Dutch). 5. Check that all buttons, links, and widgets are translated and saved. 6. Clear both site and browser cache. If these steps do not resolve the issues, the problem might be outdated or specific to your setup. We recommend visiting related known issues, verifying the version of the permanent fix, and ensuring you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
Problem: If you're experiencing a critical error on your translated site pages, it might be due to a PHP Fatal error indicating a type mismatch. Specifically, the error occurs because the code expects an array but receives a string instead. This issue often arises with ACF custom fields that are not correctly handled in translations. Solution: We recommend checking the ACF custom fields used in your template. Ensure that fields such as 'section_details', 'section_info', and 'section_map' are properly registered for translation with WPML and are returning arrays as expected. Here's what you might see in your code:
$salon_details = get_field('section_details');
$salon_info = get_field('section_info');
$salon_map = get_field('section_map');
$map_link = $salon_details['map_link'];
$address = $salon_info['address'];
$coords = $salon_map['lat_lang'];
Please confirm where these fields are defined: Are they attached to a specific page, a custom post type, or an ACF Options Page? 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. If problems persist, please open a new support ticket.
Проблема: Клиент столкнулся с проблемой дублирования атрибутов и поломкой таксономий при использовании стандартного CSV-импортера WooCommerce в связке с плагином WPML Export and Import. Атрибуты, которые уже были переведены и связаны через WPML Taxonomy Translation, дублировались и теряли связь с переводами после импорта. Решение: Мы провели тесты и обнаружили, что проблема возникает из-за неправильной структуры файла импорта. В поле
Attribute 1 name
должны быть указаны оригинальные названия атрибутов, а не их переводы. Поле
Attribute 1 value
должно содержать переведённые значения атрибута для соответствующих языков. Это предотвратит создание новых атрибутов при импорте и сохранит корректную связь с уже существующими переводами.
Если данное решение окажется неактуальным или не поможет в вашем случае, мы настоятельно рекомендуем проверить известные проблемы, убедиться в актуальности версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов. Если проблема сохранится, пожалуйста, откройте новый тикет поддержки.
