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 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.
Problem: The client is unable to translate a PDF file assigned to a custom 'project' post using an ACF field of type 'file'. The field is set to 'Translate' in WPML settings, but it does not appear in the translation screen, and the same PDF file as the PL version is automatically used for the EN version. Solution: We recommended inserting the following code into the theme's functions.php file to allow translating numeric values, which include the PDF file ID:
After adding this code, make a minor change to the page title and attempt to translate the PDF file ID, which should now be visible in the media library. Additionally, we suggested using the Media Translation interface for a more user-friendly approach to translating the PDF file.
If this solution does not resolve your issue or 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. If the problem persists, please open a new support ticket.
Problem: The client reported that after translating a property into Greek, the content was missing on the Greek page. Additionally, some fields were still untranslatable. Solution: We advised the client to ensure that the ACF Field Groups were set to 'Not Translatable' in WPML → Settings → Post Types Translation. Then, in ACF → Field Groups → Property Fields, we recommended using the option to apply all fields across languages. For finer control, we suggested switching to 'EXPERT' mode to access field-level options. To address the missing content on the Greek page, the following steps were taken: 1. Edited the property in the default language. 2. Switched to Greek using the language switcher. 3. Scrolled to Theme/Page Options and copied the same settings from English to Greek, ensuring the Content Layout → Post Template was set. 4. Set the custom field 'thegem_page_data' to copy. For the untranslatable fields, we set the specific field 'ammenities' to 'Translate' in ACF Field Groups under 'Expert' mode and updated both the property and its translation.
If this solution does not resolve your issue, 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. If problems persist, please open a new support ticket.
