Problem: Sie versuchen, WPML Translation (automatic) mit ACF Custom Fields zu verwenden, welche per PHP im Theme registriert wurden, aber die ACF-Felder werden im Backend nicht angezeigt/erkannt und können somit nicht automatisch übersetzt werden. Das Problem tritt auf, sobald Repater Fields in PHP registriert werden. Solution: Das Problem, das Sie beschreiben, ist bekannt und noch nicht gelöst. Ein Fix ist für die Version 2.2.0 von "Advanced Custom Fields Multilingual" geplant. Leider gibt es noch keinen festen Termin für das Update, da noch einige interne Tickets offen sind. In der Zwischenzeit empfehlen wir, die Felder direkt im Backend anzulegen.
Da diese Lösung möglicherweise veraltet oder nicht auf Ihren Fall zutreffend ist, empfehlen wir Ihnen, die bekannten Probleme zu überprüfen, die Version des dauerhaften Fixes zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollte das Problem weiterhin bestehen, zögern Sie nicht, ein neues Support-Ticket zu eröffnen. Besuchen Sie dazu unser Support-Forum.
Problem: Si estás intentando traducir los campos del plugin The Events Calendar, como página, categoría y organizador, y notas que muchos slugs no funcionan correctamente, esto puede indicar una incompatibilidad. Los botones como 'esdeveniments anteriors' y 'esdeveniments posteriors' pueden no funcionar correctamente, y la traducción parece perderse. Por ejemplo, al pulsar siguiente, la URL incorrecta muestra patrones como (/?:organizer|organitzador) en lugar del slug traducido esperado. Solution: Este problema está relacionado con un conflicto conocido con The Events Calendar. Para resolver este inconveniente, te recomendamos aplicar la solución temporal que se sugiere en el siguiente enlace: https://wpml.org/es/errata/the-events-calendar-incorrect-link-format-with-custom-slug-translations/.
Si esta solución no resuelve tu problema o si la información parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos relacionados en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: You are encountering translation loading errors on your website with WPML, specifically with the js_composer and instagram-feed domains. The errors indicate that translation loading was triggered too early, and should instead be loaded at the init action or later. Solution: First, refer to the WPML errata page that addresses this specific issue: https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/. Additionally, we have turned off the debug mode on your website, which should prevent the PHP notice from displaying. Please check if the notice has stopped appearing.
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 at WPML support forum for further assistance.
Problem: If you're experiencing an issue where the 'translation management' entry is missing from the WPML menu after the latest update, you are not alone. Solution: We recommend taking a backup of your site first. Then, please follow the workaround provided in our errata. You can find the detailed steps here: https://wpml.org/errata/admins-cannot-access-wpml-translation-management/.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: You are trying to access the WPML main page on your site and encountering a 'page not found' (404) error when trying to reach
https://wimoov.shop/wp-admin/tm/menu/main.php/
. You are wondering if there is a configuration issue with WPML that could cause this error. Solution: We have identified this as a known issue. We recommend taking a backup of your site and then applying the workaround provided in our errata. You can find the detailed steps and information at https://wpml.org/errata/admins-cannot-access-wpml-translation-management/. Please try this solution and let us know the results.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client was unable to see the translation engines and the 'Translate automatically' option in WPML -> Post Type Translations, and their WooCommerce products were not being translated. Solution: We recommended the following steps: 1. Navigate to WPML -> Translation Management -> Translation Tools tab. 2. Scroll down to find translation engines and enable/disable a few. 3. Go to WPML -> Settings to check if the translation engines are now visible. 4. If visible, proceed to WPML -> Translation Management and look for a switch to enable automatic translation. 5. If the issue persists, unregister and re-register WPML on the site by following these steps: - Go to the WPML registration page and click on 'Unregister WPML from this site'. - Remove the site from your WPML account. - Generate a new key and register the site again. 6. Double-check if the issue is resolved by ensuring the site can connect to WPML servers. 7. If problems continue, it might be related to a known issue which can be checked here: https://wpml.org/errata/admins-cannot-access-wpml-translation-management/
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.
The client is experiencing issues with translating Bricks Builder pages using WPML. The main symptoms include improper translations and CSS/JS rendering issues on the translated pages.
Solution:
1) Ensure a full site backup is performed. 2) Navigate to WPML>>Settings>>Post Types Translation and select *Translatable only show translated items* for My Templates (bricks_template) post type. 3) Save the changes. 4) Go to Bricks>>Templates>>My Templates and translate the Header & Footer templates. 5) Update the Homepage in the original language after a minor edit to refresh the translation settings.
Additionally, add the following code to the functions.php file of your theme:
add_filter('get_post_metadata', 'wpml_compsupp7667_bricks_translate_template_conditions', 10, 4);
function wpml_compsupp7667_bricks_translate_template_conditions($value, $post_id, $key, $single) {
if ($key !== '_bricks_template_settings') {
return $value;
}
// Remove filter temporarily to avoid infinite loop
remove_filter('get_post_metadata', 'wpml_compsupp7667_bricks_translate_template_conditions', 10);
// Get all meta values
$raw_values = get_post_meta($post_id, $key, false);
// Add filter back
add_filter('get_post_metadata', 'wpml_compsupp7667_bricks_translate_template_conditions', 10, 4);
// If we have no values, return the original
if (empty($raw_values)) {
return $value;
}
// Process the array structure
foreach ($raw_values as &$settings) {
if (is_array($settings) && isset($settings['templateConditions'])) {
foreach ($settings['templateConditions'] as &$condition) {
if (!empty($condition['archiveTerms']) && is_array($condition['archiveTerms'])) {
foreach ($condition['archiveTerms'] as &$termString) {
if (strpos($termString, '::') !== false) {
list($taxonomy, $termId) = explode('::', $termString);
$translatedId = apply_filters('wpml_object_id', intval($termId), $taxonomy, true);
if ($translatedId) {
$termString = $taxonomy . '::' . $translatedId;
}
}
}
}
}
}
}
return $raw_values;
}
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. Please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: If you're experiencing a PHP notice stating 'Function _load_textdomain_just_in_time was called incorrectly' after updating to WordPress 6.7 and using WPML with plugins like Instagram Feed and WP Security Audit Log, the issue might be related to those plugins. Solution: We recommend ensuring that you are using the latest versions of them and WPML plugins. Update your WPML to version 4.7.3 to benefit from recent bug fixes and improvements. You can check the latest versions under 'My Account -> Downloads' on our website. For updating instructions, visit http://wpml.org/faq/install-wpml/. If updates are not visible, click the 'Check for updates' button in the Plugins → Add New Plugin → Commercial tab. For more details on this specific PHP notice, please visit https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/.
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 further assistance is needed, please open a new support ticket at our support forum.
Проблема: Клиент является суперадминистратором сайта и не может назначить себя переводчиком, система не позволяет это сделать. Решение: Если вы столкнулись с аналогичной проблемой, мы рекомендуем вам добавить следующий код в функции вашего сайта, чтобы восстановить недостающие возможности для пользователей с ролью администратора:
function add_wpml_manage_translations_cap() {
$role = get_role('administrator');
if ($role) {
$role->add_cap('manage_translations');
}
}
add_action('init', 'add_wpml_manage_translations_cap');
Этот код добавит необходимые права вашей администраторской роли, позволяя назначать себя переводчиком.
Обратите внимание, что данное решение может быть неактуальным или не подходить для вашего случая. Мы настоятельно рекомендуем проверить список известных проблем, убедиться в версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов. Если проблема сохраняется, пожалуйста, откройте новый тикет поддержки.
