Problem: The client is experiencing an issue where WPML add-ons such as WPML String Translation, WPML CMS Navigation, WPML Media Translation, and WooCommerce Multilingual & Multicurrency are installed and active, but still appear as 'Not installed' in the WPML → Support section. Despite trying steps like reactivating plugins in the recommended order and re-registering WPML, the issue persists. Solution: We acknowledge this problem and recommend ignoring it for now as it does not impact the functionality of the site or the plugins. The plugins should continue to operate normally. We will include a fix in an upcoming release.
If this solution does not seem relevant, or if it becomes outdated, we encourage you to open 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 at WPML Support Forum.
Problem: The client reported that while translating a site automatically, the post translation worked, but the home/footer did not translate properly, although the header did translate. Solution: We recommended resending the footer for translation. After doing so, the issue was resolved. If you're experiencing similar issues with parts of your site not translating, we recommend trying to resend the content for translation.
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 problem persists, please open a new support ticket.
Problem: Если вы столкнулись с ошибкой в консоли на товарных страницах в админпанели, где указано, что файл локализации (например, uk.json) не найден, это может быть вызвано отсутствием файла локализации для установленного языка. Solution: Мы подтвердили, что данная ошибка не влияет на функциональность сайта и является безвредной. Наша команда уже информирована о проблеме и рассмотрит возможность добавления необходимых файлов локализации в будущих обновлениях. Если ошибка вызывает беспокойство, мы рекомендуем проверить, установлены ли последние версии тем и плагинов, а также ознакомиться с известными проблемами на странице известных проблем.
Problem: The client was unable to translate certain texts and strings on their website using WPML.
Solution: We recommended several steps to make the strings translatable: 1. Enable auto-detection in WPML → String Translation and visit the front-end in a non-default language to help WPML detect and register the strings. 2. If strings are still missing, use WPML → String Translation → Utilities → Admin Texts Translation to find and select strings from theme or plugin options for translation. 3. If strings are not found in Admin Texts, scan the theme or plugin directly from WPML → Theme and plugin localization. 4. Check WPML → Translation Dashboard under Templates or Template Part sections for embedded strings in theme parts.
If these steps do not resolve the issue, it might be due to strings being hardcoded in theme/template files or using non-WPML-compatible functions. In such cases, a manual inspection of the texts and their page sources is necessary. We recommend not repeating previously confirmed ineffective steps and considering alternate methods like registering text via WPML hooks or direct gettext review.
If the solution provided here is 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues where hard-coded strings in your template are not available for translation after using WPML, it might be due to the strings not being properly wrapped in translatable PHP functions. Solution: We recommend wrapping any hard-coded strings in your PHP template files with translation functions. For example, if you have a line like
<span>Regulation and Safety</span>
, you should change it to:
<span><?php _e('Regulation and Safety', 'bricks'); ?></span>
This change ensures that the string 'Regulation and Safety' is registered for translation in WPML under the 'bricks' theme domain. After making this modification, the text should be available for translation in WPML > String Translation.
Please note that this solution might be irrelevant if it's 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.
