Problem: The client is working on a site under development and needs to know which addon WPML will support between Advanced Custom Fields (ACF) and Secure Custom Fields (SCF). Solution: We support both ACF and SCF, and both are compatible with WPML. SCF has maintained the same class name and structure as ACF, which ensures continued compatibility. For more details, you can refer to the discussion on WordPress support about ACF and SCF compatibility: https://wordpress.org/support/topic/acf-ml-compatibility/ Additionally, please review a related support ticket where compatibility with both ACF and SCF was confirmed: https://wpml.org/forums/topic/compatibility-with-acf-scf/
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.
Problem: You are working on a site under development and encountering issues with the WPML advanced editor. The specific problems include: the editor being not user-friendly, the sticky header occupying too much screen space, and the strings not collapsing automatically when clicking on another string. Solution: We appreciate your feedback on these issues. We have informed our development team about your experience and the specific problems you've encountered with the advanced editor. They will look into these concerns to improve the editor's usability in future updates.
If this solution becomes irrelevant due to updates or if it does not address 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where WPML String Translation is running too many slow queries, as reported by their hosting provider. Solution: If you're encountering similar issues, we recommend the following steps: 1. Create a backup of your website, or ideally, test these changes on a staging version to avoid disrupting your live site. 2. Navigate to WordPress Dashboard > WPML > Settings and ensure you select the first option for custom post types, especially for 'products' which currently might be using a less optimal setting. 3. Go to WordPress Dashboard > WPML > Support > Troubleshooting and perform the following actions: - Clear the cache in WPML - Remove ghost entries from the translation tables - Cleanup and optimize string tables - Click on "Clear invalid strings" to delete unused or invalid strings.
These steps should help reduce the number of slow queries generated by WPML String Translation. If this solution does not apply to your situation, 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 issues persist, please open a new support ticket.
Problem: The client is experiencing an issue where the Shop Manager loses access to wp-admin when removed from the list of Translators in a WordPress site using the WPML plugin. Solution: We attempted to replicate the issue by following these steps: 1. Created a new Shop Manager and added the user as a Translator. 2. Logged into the site from another browser using the Shop Manager credentials. The wp-admin still did not load; only the "My Account" page was accessible. 3. Removed the Shop Manager from the list of Translators. 4. Checked again as the Shop Manager, and wp-admin was still inaccessible. Since the issue could not be replicated on our end, it suggests that there might be another factor specific to the client's site causing this problem. We recommend creating a video demonstrating the steps and sharing it for further assistance.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. 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, you can also visit our support forum at WPML support forum.
Problem: You are working on a site under development and have added a plugin in the widgets. While you can translate some strings using WPML, others remain untranslated. Solution: First, ensure you back up your site. Then, add the following code to your
// WPMl Workaround for compsupp-7428
function wpml_compsupp7428_register_and_translate_labels_for_wooVPF($label) {
if (class_exists('Sitepress')) {
$string = $label;
$textdomain = ' woo_vpf_ymm'; // Replace with your actual text domain
$string_name = 'Woo VFP: ' . substr($string, 0, 20);
if (apply_filters('wpml_default_language', NULL) == apply_filters('wpml_current_language', NULL)) {
do_action('wpml_register_single_string', $textdomain, $string_name, $string);
}
// Apply the translation to the string
$label = apply_filters('wpml_translate_single_string', $string, $textdomain, $string_name);
}
return $label;
}
// List of filters to apply the custom function
$label_filters = [
'woo_vpf_ymm_year_label',
'woo_vpf_ymm_make_label',
'woo_vpf_ymm_model_label',
'woo_vpf_ymm_engine_label',
'woo_vpf_ymm_category_label',
'woo_vpf_ymm_keyword_label',
'widget_woo_vpf_ymm_label_year',
'widget_woo_vpf_ymm_label_make',
'widget_woo_vpf_ymm_label_model',
'widget_woo_vpf_ymm_label_engine',
'widget_woo_vpf_ymm_label_category',
'widget_woo_vpf_ymm_label_keyword',
'widget_woo_vpf_ymm_label_search',
'widget_woo_vpf_ymm_label_reset_search'
];
// Apply the custom function to each filter
foreach ($label_filters as $filter) {
add_filter($filter, 'wpml_compsupp7428_register_and_translate_labels_for_wooVPF');
}
After adding the code, follow these steps:
Go to the page with the strings in the original language to register it.
Navigate to WPML > String Translator and locate the strings.
Change the language of the strings from English to French.
Translate the strings to English.
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: If you're experiencing issues where products appear correctly when logged in as an admin but do not appear in incognito mode, it might be due to the products being in draft status or not being automatically published after translation. Solution: First, ensure that the product translation review is complete by following this guide. 1. From the WordPress dashboard, switch to a secondary language using the language switcher on the top bar. 2. Navigate to "Products > All Products." 3. Check if the products are set to 'Published'. If they are in 'Draft', open the product in the Editor, go to the Publish meta section, change the status to "Published," and click on 'Update'. Additionally, check the WPML > Settings and ensure the option to 'Publish the post translations' is selected. This setting will ensure that translations are published immediately upon completion. For any products currently saved as drafts, you will need to publish them manually.
If this solution does not resolve your issue or seems irrelevant due to outdated information or a different case scenario, we recommend opening a new support ticket. We also advise 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: The client needed to delete a website from their WPML account but was unable to find the delete button. They were able to remove the site from the 'Your Registered Sites' section but not from the 'Sites Using Prepaid Credits' section. Solution: 1. We asked the client to check if they had tried removing the site from the WPML account sites page at https://wpml.org/account/sites. 2. We inquired if the client could see a trash icon next to the domains on the same page, as shown in our provided screenshot. 3. We requested confirmation from the client to ensure the site no longer appeared in their account.
If you're experiencing a similar issue and the provided steps do not help, or if this solution doesn't seem relevant to your problem, please open a new support ticket at WPML support forum.
Problem: If you're using WoodMart with WPML Sticky Links and notice that links within WoodMart WPBakery widgets are not being transformed into PageIDs like they do with the default WordPress editor, you're encountering a known limitation.
Solution: We have investigated this issue and found that WPML Sticky Links is designed to search for href attributes within the content. However, with page builders like WoodMart's WPBakery widgets, links are part of the shortcode content and not standard href attributes. To handle translation for these links, you need to register them with the wpml-config.xml file. Fortunately, WoodMart's links are already registered in the XML configuration.
Here are the steps to ensure your links translate correctly: 1. Translate the target page (e.g., the 'Cart' page). 2. Update the original page that contains the WoodMart widget link to point to the target page. 3. Translate the page containing the widget. 4. Check the translated page on the front-end to confirm that it links to the translated target page.
Problem:
If you're experiencing issues with Sticky Links converting URLs to PageIDs and you want to retain the original URL for specific links, you may find that the suggested code to blacklist certain slugs is not working as expected.
Solution:
We recommend adding the following code to your
functions.php
file to blacklist specific requests and prevent Sticky Links from converting them into PageIDs. Here's the code you should use:
If this solution doesn't look relevant to your issue, please don't hesitate to open a new support ticket. You can do so by visiting the WPML support forum.
