Problem: If you're experiencing issues where non-existent translations still appear in the WPML String Translations list under Yoast SEO, this might be due to these strings not being deleted from the database. Solution: We recommend checking the WPML-> String Translations-> Admin Texts screen to see if the strings are still present there. If they are, it indicates that Yoast SEO has not removed these strings from the database, and they will continue to appear in the list. This behavior is expected if the strings are still listed in your _options table, as WPML displays all strings that are present in this table.
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 at WPML support forum for further assistance.
Problème : Le client ne peut pas changer entre le français et l'anglais sur la page /fr/jr1w2a et sa version anglaise. La page en anglais affiche seulement le drapeau anglais et ne permet pas de changer pour le français. Solution : 1. Vérifiez que la traduction correcte de /jr1w2a/ est /fr/jr1w2a-2/, et non /fr/jr1w2a/ qui est actuellement dans la corbeille. 2. Supprimez définitivement la page /fr/jr1w2a/ de la corbeille pour libérer le slug 'jr1w2a'. 3. Éditez la page /fr/jr1w2a-2/ dans l'éditeur WordPress et changez le slug en 'jr1w2a' pour correspondre à la version anglaise.
Si cette solution ne résout pas votre problème ou semble obsolète, nous vous recommandons de vérifier les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support.
Проблема: Клиент столкнулся с проблемой, что при настройке атрибутов в WooCommerce на русском языке, к названиям атрибутов добавляется слово 'Product'. Это происходит из-за особенностей работы WooCommerce, который добавляет 'Product' к множественному числу атрибутов. Решение: Мы рекомендуем делать переводы атрибутов с английского языка, чтобы они корректно отображались на сайте. Также возможно изменить вывод хлебных крошек так, чтобы значение бралось в единственном числе, что поможет избежать добавления 'Product' к атрибутам.
Если данное решение окажется неактуальным или не поможет в вашем случае, мы настоятельно рекомендуем проверить известные проблемы, убедиться в актуальности версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов. Если проблема сохранится, пожалуйста, откройте новый тикет поддержки.
Problem: Клиент пытается связать WPML с Smartcat и сталкивается с ошибкой авторизации, несмотря на правильный ввод API key и Account ID. Возник вопрос о правильном заполнении поля Server URL. Solution: Если вы пытаетесь активировать сервис перевода через раздел WPML -> Translation Management → Translators, вам потребуется больше информации о проблеме, которую можно найти здесь: https://wpml.org/documentation/translating-your-contents/professional-translation-via-wpml/#1-connect-your-website-to-a-translation-service Если вы используете плагин Smartcat Integration for WPML для активации, вам следует обратиться к автору данного плагина, так как мы не тестировали его с WPML. Попробуйте использовать следующий Server URL:
https://smartcat.ai/api/integration
Это должно решить проблему.
Если предложенное решение не актуально или не помогло, рекомендуем открыть новый тикет в службе поддержки. Также настоятельно рекомендуем проверить известные проблемы, версию постоянного исправления и убедиться, что у вас установлены последние версии тем и плагинов.
Problem: You are trying to translate a page on your website and encounter an error message: 'Someone is already rating this translation. Please try again later.' even though you are the only one working on the website. Solution: If you're experiencing this issue, we recommend you try clearing your cache as this resolved the problem for the client. Please note that the solution might be irrelevant if it's 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 the problem still exists, please open a new support ticket.
Problem: You are using WPML with Elementor to translate a page and have encountered an issue where updating text in the English version via WPML overwrites the image you changed in Elementor.
Solution: This happens because changes made in the Advanced Translation Editor (ATE) are saved in the translation memory and overwrite any changes made using another editor like Elementor. To prevent this, you should use the same editor to add/update translations. If you need to change the image in the translation, use the English URL of the image when translating the content in ATE. If URLs are not visible in ATE, search for "http" to find and translate the desired URL. For more details, please see how to translate URLs, shortcodes, and HTML attributes using the Advanced Translation Editor.
If this solution does not apply to your case, or if it seems 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 visit our support forum.
Problem: The client was unable to edit or add images to translated products using Advanced Custom Fields (ACF) with WPML. The images appeared on the translated product, but the edit/remove functions were not available, and the 'add image' button did not appear. Solution: The issue was not related to WPML but was caused by outdated PHP code in the template that defined the ACF field group and its settings. This outdated code interfered with newer versions of ACF, preventing several UI elements from loading properly. The client resolved the problem by removing this outdated PHP code, restoring functionality to the UI elements.
If you're experiencing similar issues, we recommend checking for any outdated code or settings in your templates that might affect ACF's functionality. Additionally, ensure that your theme and other plugins are not causing conflicts. You can do this by switching to a default WordPress theme like TwentyTwenty-Four and deactivating all plugins except for WPML and ACF. If the problem persists, activate the plugins one by one to identify the culprit.
Please remember to back up your site before making any changes. If your site is live, consider performing these checks in a staging environment.
If this solution does not apply to your case, or if it seems outdated, please visit our known issues page and confirm that you have installed the latest versions of themes and plugins. If the issue persists, we highly recommend opening a new support ticket with us here.
Problem: The client experienced an issue where the site's text became unreadable with scrambled letters and charset changes after deleting previous administrators and transferring their settings. The issue was accompanied by PHP errors related to charset support in the console. Solution: We suggested checking if the problem persists when WPML is deactivated to determine if it's related to WPML or a broader database configuration issue. Additionally, we recommended changing the character encoding and collation of the database tables. Here are the steps we advised: 1. Temporarily deactivate WPML to see if the issue still occurs. 2. Follow the documentation to change the character encoding and collation of your database tables: https://wpml.org/faq/texts-showing-as/ If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your current setup, 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 for further assistance.
After migrating from a staging site to a test site, most of the text displays incorrectly, showing special characters and question marks. Additionally, the media section shows blank images, though the images exist.
Solution:
If you're experiencing issues with special characters and question marks after migration, it's likely due to the database collation setting. We recommend changing your database collation to either utf8mb4_unicode_ci or utf8mb4_unicode_520_ci to support non-Latin characters properly. Before making changes, ensure you back up your site fully. You can run the following SQL query for each table:
ALTER TABLE your_table_name CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;
For example:
ALTER TABLE wp_posts CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;
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 at WPML support forum.
Problem: If you're experiencing issues where the language switcher does not work for a specific language, such as German, and navigating from the Dutch homepage to the German homepage results in a 404 'nothing found' error, while the direct URL (e.g., https://hpstaal.nl/de/home) loads fine, the problem might be related to your WordPress reading settings. Solution: We recommend checking your WordPress reading settings. Specifically, ensure that 'Your homepage displays' is set to show a static page instead of 'Your latest posts'. You can find this setting under WordPress Reading Settings. Set it to display the 'Home' page as the static page.
If this solution does not resolve your issue, or if it 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.
Problema: Il cliente ha un multisite con WPML attivo solo in due siti. Vuole cambiare la chiave di licenza solo per uno di questi siti, ma non trova l'opzione per farlo dalla pagina 'Add new plugin'. Soluzione: Se stai riscontrando lo stesso problema, ti informiamo che la chiave di licenza in un ambiente multisite è gestita a livello di network e non è possibile associare un singolo sottosito a un account WPML diverso. Pertanto, non è possibile cambiare la chiave di licenza solo per uno dei siti in un network multisite.
Se questa soluzione non risolve il tuo problema o se ritieni che le informazioni siano obsolete, ti invitiamo a verificare i problemi noti e a confermare che hai installato le versioni più recenti dei temi e dei plugin. Se necessario, apri un nuovo ticket di supporto sul forum di supporto WPML.
Problema: El cliente no puede usar WPML Translation Management para traducir del español a otros idiomas porque el idioma por defecto es el inglés. Solución: Primero, recomendamos verificar en WPML -> Translation Management si es posible filtrar por el contenido en inglés y enviarlo a traducir al español. Si esto no resuelve el problema, hay dos alternativas: 1. Cambiar el idioma por defecto del sitio a inglés. 2. Traducir el contenido directamente desde el bloque de Idiomas que aparece en la columna derecha al editar posts (entradas, páginas, etc).
Si esta solución no es relevante porque podría estar desactualizada o no aplicar a su caso, le sugerimos abrir un nuevo ticket de soporte. También recomendamos revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que tiene instaladas las últimas versiones de temas y plugins. Para asistencia adicional, puede visitar nuestro foro de soporte.