Problem: The client experienced issues with WPML where translations were incorrectly cached, showing different languages across listings. Additionally, there was confusion about the default language of strings being overwritten by translations. Solution: 1. Verify if the problematic strings, such as 'Beschreibung', are correctly assigned and translated in the appropriate languages using the WPML String Translation. If the languages don't match, follow the steps in this guide to change the source language of strings: https://wpml.org/documentation/getting-started-guide/string-translation/how-to-change-the-source-language-of-strings/ 2. To address cache-related translation issues, we recommend setting up a staging site and deactivating all plugins except for WPML. Then, reactivate them one by one to identify the plugin causing the issue.
If this solution does not apply to your case, or if it 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. We highly recommend opening a new support ticket if further assistance is needed. You can do so here: WPML Support Forum
Problem: You are trying to translate Custom Post Type Categories and maintain the hierarchy across languages, ensuring that child and parent relationships are respected. However, the child and parent hierarchy is not respected across languages after translation. Solution: We recommend following the steps described in the guide on how to translate features and amenities in WPML. Make sure your configuration is set as described in the documentation because cache memory might affect the final output. You can find the guide here: https://help.wprentals.org/article/how-to-translate-features-and-amenities-in-wpml/
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 at WPML support forum.
The client needed assistance setting up WPML for a new section of their website (***la.hr/stay/) to have language-specific homepages and consistent URL structures across different languages, similar to their main site configuration.
Solution:
We advised the client that the desired setup would require custom coding as it involves linking two separate WordPress installations, which is beyond the standard WPML support scope. We suggested setting the default language homepage to the 'Stay' page from WordPress settings and translating this homepage into other languages.
Additionally, we recommended using the 'A different domain per language' option for URL formats, but noted that this would require specifying exact domains for each language. For further details on setting up language URL options, please refer to this documentation.
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 open a new support ticket at WPML support forum.
The client is using Advanced Custom Fields (ACF) with WPML and has set up the Advanced Custom Fields Multilingual. However, the field choices are not being translated in the frontend despite translating the labels in WPML>>String Translation. The features section with bullet points is not translated across all languages.
Solution:
We recommended using the
get_field_object
function instead of
get_field
to fetch the field data correctly. This change should allow the field choices to display the translated values.
Here is the modified code snippet to implement in the functions.php file of the child theme:
// Create shortcodes for individual fields without titles
function generate_individual_field_shortcodes_no_title() {
// List of fields to create shortcodes for
$fields = [
'living_area',
'views',
'laundry',
'bathroom',
'kitchen_and_dining',
'bedroom',
'media_and_entertainment',
'miscellaneous',
'home_safety',
'outdoor_spaces',
'family-friendly',
'parking_and_facilities',
'languages_spoken',
'nearby',
'house_rules',
'cancellation_prepayment',
'refundable_damage_deposit',
'payment_methods'
];
foreach ($fields as $field) {
// Dynamically generate shortcode callback for each field
add_shortcode($field . '_list', function() use ($field) {
ob_start(); // Start output buffering
$fields = get_field_object($field); //Get field data
$options = $fields['value'];
// Display labels.
if( $options ): ?>
<ul>
<?php foreach( $options as $option ): ?>
<li><?php echo $fields['choices'][$option]; ?></li>
<?php endforeach; ?>
</ul>
<?php endif;
return ob_get_clean(); // Return the output and end buffering
});
}
}
add_action('init', 'generate_individual_field_shortcodes_no_title');
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 WPML support forum.
You are trying to translate your site using WPML and encountering issues with some articles and elements, specifically involving the base64 encoded fields in the fusion_sharing: description field.
Solution:
If you're experiencing this issue, we recommend adding the WPML language configuration for the Avada Element that is causing the problem. First, identify the exact name of the Avada Element/Widget that is problematic. You can refer to our documentation on how to handle such cases:
Additionally, ensure you have updated the original language page after canceling any translation job and place the following custom XML configuration in WPML>>Settings>>Custom XML Configuration:
If this solution does not apply because it is outdated or not relevant 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.
