Problem: The client is experiencing a fatal error when loading a variable product in the REST API, but not with a simple product. The error message indicates an issue with calling a member function on an array within the WooCommerce Multilingual plugin. Solution: We recommend deactivating all third-party plugins except for WooCommerce and WPML-related ones, and switching to a default theme like Twenty Twenty-Two to isolate the issue. This approach helped confirm that the problem might be caused by either a conflicting plugin or the theme currently active on your site. If this resolves the issue, you can reactivate each plugin one by one to identify the specific cause of the conflict.
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 for further assistance at WPML support forum.
Problem: The client is experiencing a PHP fatal error when trying to save an options page in Polish and German languages using WPML and ACF Pro. The error message indicates an issue with illegal offset type in isset or empty, which is not directly caused by ACF but by how WPML interacts with ACF's low-level filters. Solution: We have identified that removing the options
options_nl_groep_voor_sociallinks
and
options_pl_groep_voor_sociallinks
from the
wp_options
table resolves the issue. It is crucial to back up the database before proceeding with this solution to prevent any data loss. This action should stop the fatal error from occurring when updating the options pages in the affected 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. If problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are experiencing issues where translated posts are showing as 'uncategorized' and errors occur when switching languages, stating 'couldn't find any post in this category'. Additionally, you are unable to run a synchronization as the sync button is not showing up. Solution: This issue might be related to permalinks being manipulated by SEO plugins like Yoast SEO. We recommend you to: 1. Install and activate the WPML SEO plugin by going to WordPress Dashboard > Plugins > Add New > Commercial (tab) and selecting WPML SEO. 2. After installation, navigate to WordPress Dashboard > Settings > Permalinks and click the save button to purge the cache. If these steps do not resolve the issue, it's important to ensure that your site is backed up before proceeding further. We suggest opening a new support ticket with us, providing access details in a private reply, after confirming that you have a backup.
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 issue persists, please contact our support team for further assistance.
Problem: If you're experiencing issues with the 'Profile Types' field not being translated on the user's profile page and encountering duplicate records when editing your profile in different languages, follow these steps. Solution: 1. Remove any previous workarounds you might have applied. 2. Add the following code to your theme's functions.php file:
// WPML Workaround for compsupp-6144
add_filter( 'bp_get_the_profile_field_value', 'wpml_compsupp6144_translate_buddypress_profile_fields', 10, 3 );
function wpml_compsupp6144_translate_buddypress_profile_fields( $value, $type, $id ) {
if ($type == 'textbox' || $type == 'wp-textbox' || $type == 'wp-biography' || $type == "membertypes") {
//remove html tags from value and limit it's size, so we can use it as string name
$filtered_value = substr(strip_tags($value), 0, 60);
// register string
if ( apply_filters('wpml_default_language', NULL ) == apply_filters( 'wpml_current_language', NULL )) {
do_action( 'wpml_register_single_string', 'BuddyPress Profile Fields', $type.' - '.$filtered_value , $value );
}
//translate string
$value = apply_filters('wpml_translate_single_string', $value, 'BuddyPress Profile Fields', $type.' - '.$filtered_value );
}
return $value;
}
3. Open the profile page on the front-end to view and register the fields. 4. Navigate to WPML > String Translator and translate the field values under the 'BuddyPress Profile Fields' text-domain. 5. Revisit the profile page on the front end to see the changes.
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 the problem persists, please open a new support ticket.
Problem: You are experiencing an issue with the String Translation table on your site, which could potentially become a critical issue in the future. Solution: We recommend following the steps outlined in the WPML errata page to fix issues related to missing String Translation tables. You can find the detailed instructions here: Missing _icl_strings and _icl_string_translations Data Tables. After applying these steps, please check your site to confirm that the issue is resolved.
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 for further assistance at WPML Support Forum.
Problem: The client moved their site from ledstore.fi to wp.ledstore.fi and is experiencing an issue where 190000 credits are not showing up in the backend after the site migration. Solution: We recommend the following steps to resolve the issue: 1. Log in to your WPML.org account and go to the Sites page: https://wpml.org/account/sites/ 2. Delete the existing site key by pressing the little trash icon, which will return the assigned credits to your WPML.org account. More details can be found here: https://wpml.org/documentation/automatic-translation/why-credits-may-be-missing-and-how-to-fix-it/#removing-a-sites-registration-from-wpml-org 3. Log in to your site and navigate to the Dashboard >> Plugins >> Add new > Commercial tab and click the Unregister WPML from this site link if it exists. 4. Click the Register WPML link. 5. Click the Get a key for this site link, which will generate a new key for your site. You can also assign the credits using that popup. 6. Copy the key, paste it back into the input box, and press the Register button.
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 purchased WPML credits but is unable to see instructions for updating their website. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Log in to your site and navigate to Dashboard >> Plugins >> Add new plugin > Commercial tab. If you see the Unregister WPML from this site link, click it. 2. Click the Register WPML link. 3. Enter the site key "yJBx2niB6g" and press the Register button. If this does not resolve the issue, please follow these steps to create a new site key: 1. Log in to your WPML.org account and go to the Sites page: https://wpml.org/account/sites/ 2. Delete the existing site key. 3. Log in to your site and navigate to Dashboard >> Plugins >> Add new > Commercial tab. If you see the Unregister WPML from this site link, click it. 4. Click the Register WPML link. 5. Click the Get a key for this site link. 6. Copy the newly generated key, paste it into the input box, and press the Register button.
If you still need help after trying these steps, 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: You are experiencing issues translating specific content on your WordPress site using WPML, including Footer Text, Contact - Location Map, and Career Section. These texts do not appear in the String Translation or other WPML settings for translation. Solution:
- For translating footer/admin text, please follow the below steps:
1. Go to WPML >> String Translation page.
2. Scroll down and click on the Translate texts in admin screens » link at the bottom of the page.
3. Search for the required string.
4. Select the string.
5. Click on the Add to String Translation button.
6. Then click on the "« Return to String Translation" link.
7. Add the translation from WPML >> String Translation page.
- To translate hardcoded strings such as 'Location Map', follow these steps: 1. Wrap the strings in the gettext
__()
function. For example, replace
'Location Map'
with
__('Location Map', 'themedomain')
in the wp-content/plugins/lifest-elementor/widgets/contact-page/contact-page-form-widget.php file. 2. Scan the Lifest Elementor plugin from WPML >> Theme and plugins localization page. 3. Go to the WPML >> String Translation page, search for the string, and add the translation. For more details on wrapping texts in gettext calls, visit Translating the Theme You Created. If this solution does not resolve your issue or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum.
Problem: If you're trying to edit a product on your WooCommerce site and only see the WooCommerce Multilingual & Multicurrency section, it might be due to an outdated version of the WooCommerce plugin. Solution: We recommend updating both your WooCommerce plugin and WordPress to the latest versions. Before updating, ensure to back up your database to prevent any potential data loss.
If this solution does not resolve your issue or seems irrelevant due to it 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 experiencing a decrease in page speed after installing WPML on their website. Solution: We recommend the following steps to improve your site's performance: 1. Disable "Adjust IDs for multilingual functionality" under WPML -> Languages -> Make themes work multilingual, especially if you are using well-known themes like Astra. 2. Reduce the overall page size by compressing media files using plugins like EWWW. 3. Install and configure a page caching plugin such as Super Cache, W3 Total Cache, or WP-Rocket. 4. Implement object caching with Redis to enhance backend performance. This requires support from your hosting or VPS and can be set up using the Redis Cache plugin. Note that some caching plugins like W3 Total Cache also provide object caching. 5. Ensure that the Query Monitor plugin is only active during testing phases to identify slow queries and not enabled in production as it can degrade performance.
If these steps do not resolve the issue or if the solution 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 the problem persist, please open a new support ticket.
Problem: The client is experiencing issues with WPML and ACF where translated fields are deselected and translations are shifted incorrectly. This results in only 14% of the page being translated correctly, and the addition or deletion of rows in repeater fields causes further misalignment of translations. Solution: We recommend following these steps after ensuring you have a full site backup: 1) Increase the
MaxInputVars
setting in your PHP configuration to 10000. You can find more details on how to do this here: Setting the MaxInputVars directive in an .htaccess file. 2) Clear all types of caches on your site. 3) Navigate to WPML>>Support page, and click on the Troubleshooting link. 4) On the Troubleshooting page, execute the following actions under 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
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: The client is facing an issue where the cart page does not automatically translate when using the language picker, although the checkout page translates correctly. Solution: If you're experiencing this issue, we recommend the following steps: 1. Ensure that the Cart page is translated and published in all required languages by visiting Pages>>All Pages. 2. If the problem persists, perform a full site backup and follow these troubleshooting steps: - Navigate to WPML>>Support page, and click on the Troubleshooting link. - On the Troubleshooting page, under the Clean up section, sequentially click and process: - 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
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your case, 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 for further assistance at WPML support forum.
Problem: The client is using ACF to store employee information and has pages in both primary and secondary languages. However, in the secondary language, the URL components are not translated and are shown in the primary language. Solution: We recommend the following steps to translate URL components using the WPML plugin: 1. Ensure that the ACF Multilingual plugin is active. 2. Set the translation preference for the Link field to "Translate" by changing the translation mode of the field group to "Expert" and then setting the Link field within the group to "Translate". 3. Open the page/post containing the link field, make a small change in the title, and save the changes. 4. Update the translation. Refer to this guide for details on translating links. 5. For translating specific slugs like 'ons-team' and 'advocaten', ensure that each component (page, custom post type, individual post) is translated correctly. For custom post types, go to "WPML > Settings", locate the post type, set it to "Translatable - Only show translated items", and use the "Set different slugs in different languages" option to specify the slug in the secondary language. More details can be found in this guide.
If these steps do not resolve your issue or if the solution 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.
Problem: The client is considering de-registering WPML from their website and is concerned about losing the accumulated translation credits. Solution: If you're considering de-registering WPML from your website, rest assured that you will not lose your translation credits. These credits will remain in your WPML.org account and can be reused if you decide to register WPML on the same or a different website in the future. For more details on how credits can be assigned or removed, please visit how to assign automatic translation credits to your sites. Additionally, when you remove a key from here, the credits assigned should automatically move back to your WPML.org account.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client reported that after translating their site from English to Russian, all Russian translations were displayed as question marks across the site. Solution: We identified that the issue was due to the database encoding not being set to UTF-8. We recommended the following steps: 1. Adjust the database tables to use UTF-8 encoding by executing the following SQL commands:
ALTER TABLE $table DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci
ALTER TABLE $table CHANGE $field_name $field_name $field_type CHARACTER SET utf8 COLLATE utf8_bin
2. Add the following line to the wp-config.php file to ensure the database uses UTF-8 charset:
define('DB_CHARSET', 'utf8');
3. Clear the WPML cache and fix WPML tables collation via WPML->Support->Troubleshooting. 4. If the issue persists, deactivate WPML temporarily and test creating a new page with Cyrillic letters. 5. For existing pages, re-save the translations or edit and update the pages without making changes to force a refresh of the content.
If these steps do not resolve the issue or if the solution 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
