Problem: You have a custom taxonomy called 'fitment' assigned to WooCommerce products, set as Not Translatable in WPML. Terms are created in Polish and work correctly in Polish products, but in the English product edit screen, the taxonomy is visible without any terms to select. You want the same taxonomy terms to be shared across all languages without needing translations.
Solution: The issue might be related to the
meta_box_cb => 'post_categories_meta_box'
in your custom code. This meta box forces WordPress to render the classic Categories-style checklist metabox for this taxonomy, which relies on wp_terms_checklist() → get_terms(), and WPML filters get_terms() in wp-admin to the current admin language. If your Fitment terms are created only in the default language and don’t have term translations, the checklist in the secondary language can appear empty. To resolve this: 1. Remove the
meta_box_cb => 'post_categories_meta_box'
from your custom code to test if the terms show in the translation without it. 2. Register the taxonomy on init with priority 0 to avoid issues with it being registered too late.
If these steps do not resolve the issue, or if the solution becomes 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 the problem persists, please open a new support ticket.
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: The client needs to filter posts in the WPML Translation Dashboard to show only those that are not translated and not duplicated, excluding posts where the translation process has started. Additionally, the client wants to duplicate all published posts of a particular type that do not have any duplicated pages for other languages or where the translation is not started. Solution: To filter posts as required: 1. Go to WPML → Translation Dashboard. 2. In the filter options at the top, locate the Translation status dropdown. 3. Select Not translated from the options. This will display only the posts that are completely untranslated and not duplicated.
To duplicate posts: 1. In the Translation Dashboard, select the Type of post you want to duplicate (e.g., 'Post', 'Page', or a specific Custom Post Type). 2. For the Status filter, choose Published. 3. For the Translation status filter, select Not translated. 4. Select all the posts you wish to duplicate by checking the box next to the Title column header. 5. Scroll down and use the Translate selected content section to duplicate the selected posts.
For automation via a custom script, WPML's Coding API provides hooks such as
apply_filters('wpml_post_duplicates', $post_id)
and
do_action('wpml_make_post_duplicates', $post_id)
to detect and create duplicates programmatically. However, this requires custom development outside the standard support services. More details and examples are available at WPML Coding API documentation.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we recommend opening a new support ticket or contacting one of our recommended contractors at WPML contractors.
Problem: If you're experiencing issues with text alignment in Hebrew and Arabic translations appearing left-aligned instead of right-aligned on your pages created with Beaver Builder, despite the text being RTL. Solution: We recommend adjusting the CSS directly in your theme to ensure proper RTL text alignment. Here's how you can do it: 1. Access your Astra child theme's RTL CSS file, which you can find here: https://dorhaba.com/wp-content/themes/astra-child/rtl.css. 2. Open the file in a code editor or through WordPress by navigating to Appearance -> Theme File Editor. 3. Locate the section for Hebrew and add
text-align: right;
under the body:lang(he) directive. It should look like this:
4. Similarly, update the Arabic section by ensuring the text-align is set to right. 5. Save your changes. This adjustment will align your Hebrew and Arabic text to the right without affecting centrally aligned sections.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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. If the problem persists, please open a new support ticket.
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.
Problème : Le client ne peut pas sauvegarder la page d'administration de la page d'accueil en polonais sur leur site WordPress. L'erreur retournée est "La mise à jour a échoué. La réponse n’est pas une réponse JSON valide." Solution : Nous avons identifié que le problème survient lorsque le plugin WPRocket est actif en même temps que le plugin permalink-manager. Un conflit est également détecté dans le fichier
/wp-content/themes/sur-mesure/functions.php
à cause d'un champ Advanced Custom Fields qui interagit incorrectement avec le gestionnaire de permaliens. Pour résoudre ce problème, nous recommandons de commenter ou de réviser le code dans le fichier functions.php, spécifiquement la fonction
pm_fix_language_mismatch
.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous conseillons de vérifier les problèmes connus et de vous assurer que vous utilisez les versions les plus récentes des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support.
Problem: If you're experiencing issues with your theme strings not appearing in the Theme and Plugin Localization section of WPML, and the scan seems never to end, follow these steps for a possible solution. Solution: 1. Navigate to WPML > Theme and Plugin Localization. 2. Look for a list of available themes and plugins, which you can select by clicking on their respective checkboxes. 3. Select your active theme by clicking on its checkbox. 4. Click the button under the list to start the scan of the selected theme.
If this solution does not resolve your issue, or if it seems outdated or not applicable to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: If you're experiencing issues where the CSS breaks on translated pages of your website, it might be related to how global sections are rendered within your theme. Specifically, the Code Snippets plugin may not be loading your theme's CSS correctly for the second language. Solution: We recommend using a Child Theme instead of the Code Snippets plugin. You can add the following snippet to the functions.php file of your Child Theme to address some of the CSS issues:
add_action('init', function() {
// Hook location to output the global section
$location_hook = 'nectar_hook_global_section_footer';
add_action($location_hook, function() use ($location_hook) {
// Detect current language
$current_lang = apply_filters( 'wpml_current_language', null );
// Default section ID (Spanish)
$global_section_id = '24759-2';
// Use translated section ID for English
if ( $current_lang === 'en' ) {
$global_section_id = '26378';
}
// Default category ID (Spanish)
$category_id = 47;
// Use translated category ID for English
if ( $current_lang === 'en' ) {
$category_id = 156;
}
// Output the section only if we're on the correct category archive
if ( is_product_category( $category_id ) ) {
Nectar_Global_Sections_Render::get_instance()->output_global_section($global_section_id, $location_hook);
}
});
});
However, if disabling the Code Snippets plugin resolves all issues, we suggest not using it and instead managing code through the Child Theme as shown above.
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.
