Problem: If you're trying to translate custom fields with a repeater on your site and they appear in the translation admin panel but not on the site after translation, we have a solution. Solution: 1- Add this snippet to the functions.php file of the theme:
/*
* WPML Workaround for compsupp-7642 - Part 1
*/
add_filter('wpml_filter_field_value', 'wpml_compsupp7642_workaround_for_serialized_post_meta');
function wpml_compsupp7642_workaround_for_serialized_post_meta($field_value) {
if (!is_array($field_value)) {
return $field_value;
}
foreach ($field_value as &$single_value) {
if (!is_array($single_value)) {
continue;
}
foreach ($single_value as &$value) {
if (!is_string($value)) {
continue;
}
if (is_serialized($value)) {
$unserialized = @unserialize($value);
if ($unserialized !== false) {
$value = is_array($unserialized) ? reset($unserialized) : $unserialized;
}
}
}
}
return $field_value;
}
2- Open the app/public/wp-content/themes/cash4smstheme/page-faq.php file
3- Replace the following snippet:
The idea is to apply a filter to all fields with the issue. This filter will apply our workaround function (part 1) that removes the double array of the value.
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 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 working on a site under development and needs to ensure compatibility with WPML. They are concerned about the compatibility of WPML with the 'Secure Custom Fields' plugin and whether to manually install the Advanced Custom Fields version 6.3.9 provided by WPEngine. Solution: We confirm that WPML is compatible with both the 'Secure Custom Fields' and the Advanced Custom Fields version 6.3.9. You are free to choose either of these plugins for your website as both are compatible with WPML. If you have any further questions or need more specific advice, 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 this solution does not apply to your case, or if it seems outdated, please do not hesitate to open a new support ticket at our support forum.
Problem: The client is using WooCommerce Multilingual & Multicurrency to set different prices per currency based on the visitor's location. However, the price does not change according to the visitor's location when accessed from Bulgaria, showing the same price as the Greek version.
Solution: 1. To display currency based on the visitor's language, ensure the content is translated into the respective language. For example, when a visitor from Bulgaria accesses the site in Bulgarian, the prices should display in BGN. 2. For proper location detection use the "MaxMind Geolocation" API. More details can be found here: Setting up currencies per location. 3. Check for plugin conflicts by deactivating other plugins and testing the currency display. Also, verify the correct operation of the VPN or MaxMind service being used for geolocation. 4. If issues persist, consider opening a new support ticket focused on this specific problem.
Please note that this solution might be 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client is considering switching from GTranslate to WPML for their sites, which need to be 100% automatically translated. They are concerned about whether WPML can handle fully automatic translations without manual intervention. Solution: We confirmed that WPML is compatible with many WordPress themes and works closely with theme authors to ensure compatibility. To check if the client's theme is compatible with WPML, we recommended visiting our compatible themes directory at https://wpml.org/theme/. For fully automatic translations, WPML offers the 'Translate Everything' mode, which can translate all types of content automatically as soon as they are published. This includes posts, pages, custom post types, products, taxonomy, and custom fields. More details on Automatic Translation can be found here: https://wpml.org/documentation/automatic-translation/. Additionally, we provided links to demonstrations of how Automatic Translation works:
If this solution does not fully address your concerns, or if it 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 further assistance is needed, please open a new support ticket.
fusion_image_hotspot_point long_text link link_title
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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.
Problem: If you're experiencing issues where a page update seems to have broken the database but another update resolved the issue, it might be related to temporary inconsistencies during the update process. Solution: We recommend you first ensure that your issue is still occurring. If it persists, please provide us with the WPML debug information to help us diagnose the problem more accurately. You can find guidance on how to gather this information here.
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. If the problem persists, please do not hesitate to open a new support ticket with us here.
Problem: You need to change the default language of your site's frontend while keeping the backend/dashboard in English.
Solution: To achieve this, follow these steps: 1. Understand that changing the default language in WPML affects both the frontend and backend. However, you can set a different language for the WordPress admin area. For detailed instructions, visit Setting the WordPress Administration Language. 2. To keep the backend in English while changing the frontend language: - Navigate to Users > Profile in your WordPress dashboard. - Set your preferred language for the backend under 'Language'. - Ensure to disable the option 'Set admin language as editing language'.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, check the related known issues and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problem: The client has translated the CPT archive slugs into six languages using WPML settings, but the PL and RO languages are not appearing in the language selector. Solution: We have configured an option that acts as a fallback for languages without vacancy posts. If there are no vacancy posts in PL and RO languages, the archive page for those languages will not be created. This setup ensures that the archive pages only appear when there are posts available in those languages.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client wants to have two different page layouts for different languages using WPML but encountered issues after initially using the translation editor. Solution: We recommend completing the translation by clicking the save button on each element to copy it from the original. After saving, delete the entire translation. Then, you can duplicate the page and follow the workflow as explained in our video tutorial here: https://www.loom.com/share/aa51354bb1ec448abf610a4d1149aeae.
If this solution does not resolve your issue or seems outdated, please check for 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 needed. For further assistance, you can contact us directly at WPML support forum.
Problem: You are trying to translate an article using WPML, but after translation, the featured image is not visible. Solution: We recommend navigating to the primary language page of the article and clicking the update button. After updating, retranslate the page to the desired language and check if the Featured Image appears.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue with the Vikrentcar plugin on their English website, which requires a modification in the database handling code. Solution: We recommend backing up your website before attempting any fixes. Navigate to the
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.
Problem: The client is using the Blocksy Theme on their WordPress site and has encountered an issue where the post-time format in English ('F j, Y') is not translating correctly to Chinese Traditional ('Y 年 n 月 j 日') for single posts. Despite ensuring all translations related to the time/date format have been applied, the translation only affects the update time, not the post-time.
Solution: We identified that the issue stemmed from the Customizer settings under Blog -> Single Post -> Post Title -> Post Meta. The solution involves ensuring that the theme is updated to the latest version as the Blocksy team has released an update addressing this compatibility issue. Additionally, it is crucial to enable aggressive options for string scan and auto-registration. The client should also check and adjust the date format settings from 'Default' to 'Custom' if necessary, to ensure the translations are registered and appear correctly. If the problem persists on a customized theme, we recommend reinstalling a fresh copy of the theme to eliminate any customization conflicts.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our support forum at https://wpml.org/forums/ 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.
Problem: The client is trying to translate posts made in Gutenberg using WPML and wants them to appear as one single text box in the Advanced Translation Editor. However, the translation is separating the content into different paragraphs. Solution: 1. In the Advanced Translation Editor, click on the settings icon (gear icon) located at the right top corner. Here, you will find an option to show 'Bigger segments'. 2. If the content still appears as separate paragraphs, you can use the merging chain to merge the paragraphs. Here is a helpful screenshot: https://prnt.sc/C5d-_x9J6en8 3. It is important to note that each paragraph in Gutenberg is treated as its own block, which WPML detects and maintains the same structure. Therefore, the largest segments that can be displayed are based on these individual blocks.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is trying to trigger an action when a custom post type translation is saved using the WordPress hook. The problem is with the is_admin function.
. This hook works as expected for the original language but does not trigger when saving or updating a translated version of the post. Solution: We recommend modifying the condition to check if the request originated from the WPML Advanced Translation Editor (ATE) by using the following code:
This code snippet checks the HTTP_REFERER to determine if the request came from the WPML ATE and adjusts the execution environment accordingly.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where changes made to your pages are not immediately visible on the live site, even after saving or translating from scratch, this might be due to a caching conflict with Elementor. Solution: First, ensure you back up your entire site. Then, follow these troubleshooting steps: 1) Navigate to WPML>>Support page and click on the Troubleshooting link. 2) On the Troubleshooting page, execute the following actions in the *Clean up* section, waiting for confirmation after each: - Clear the cache in WPML - Remove ghost entries from the translation tables - Fix element_type collation - Set language information - Fix WPML tables collation - Assign translation status to duplicated content - Fix terms count - Fix post type assignment - Cleanup and optimize string tables - Show custom MO Files Pre-generation dialog box>>Generate .Mo files If the issue persists, disable the Element Caching option in Elementor by going to Elementor>>Settings>>Features tab. We have also released an errata for this issue, which can be found here: https://wpml.org/errata/elementor-translated-pages-show-stale-content-after-being-updated/
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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. Should you need further assistance, please open a new support ticket at WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
