Problem: The client reported that listing items were visible on one page but not on another after translation. The issue was suspected to be related to a filter in the Post Query settings. Solution: We identified that the 'highlight' custom field in the Post Query settings was set incorrectly, preventing listings from showing on the English version of the page. We changed the 'highlight' field setting to 'Copy' and updated the translations for the events. This adjustment allowed the listings to appear correctly on the English version of the homepage. We recommend the client to make a small change to all events and update their translations to ensure the field is correctly added.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and check for any related issues. Also, ensure you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket here.
Problem: You are trying to translate a page into French using WPML, but nothing is displayed on the website. This issue is due to an incompatibility between Royal Elementor Addons and WPML. Solution: The problem occurs in the
file. Royal Addons is attempting to find a non-existent template, which leads to a NULL return. To resolve this, access your database, locate the 'wpr_single_conditions' option in the WordPress Options table, and delete its value. After making this change, the issue should be resolved.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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, please visit our support forum at WPML support forum.
Problem: The client reported that forms on their website were displaying in English on both language versions, despite having translations available in Serbian. Solution: We discovered that the issue was due to the client using an older version of the WPML plugins. We recommended updating these plugins to the latest version. After the update, the forms displayed correctly in the respective 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 the problem persists, please open a new support ticket.
Problem: After updating to a version of ACFML greater than 2.0.5, you might find that on a secondary language page, many ACF fields (e.g., from an ACF options page) and unfilled fields in the backend are saved in the postmeta. This results in numerous empty fields and incorrect
get_field()
calls because the field is present with the post but has an empty array as a value. In the default language, these fields are not saved in the database. Solution: We recommend editing the file
This change should resolve the issue. Additionally, ensure that each of your custom fields across different field groups has a unique Field Name to avoid translation and functionality issues. More details can be found in the WPML documentation. If this solution does not apply to your case, or if it seems outdated, please 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. For further assistance, you can always contact our support at WPML support forum.
Problem: You are using manual translation to translate the list view in the footer to French URLs, but the last 2 URLs are not showing up after translation. Solution: We recommend checking if you have used the Advanced Translation Editor, as internal links typically do not appear in the WPML Translation Editor. You can learn more about the features of the Advanced Translation Editor here: Advanced Translation Editor Documentation. Additionally, try searching for "http" in the top left search bar of the Advanced Translation Editor to locate the missing links.
If this solution does not resolve your issue or 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 the problem persists. You can do so here: WPML Support Forum.
Problem: The client is experiencing an issue where the product ID changes when switching languages from Italian to English in a WPML-translated e-commerce platform. This change in ID causes issues with the platform's ability to recognize the correct product. Solution: We explained that each translation in WPML is treated as new content, hence each has a unique ID. To maintain consistency across languages, you can use the
wpml_object_id
hook to fetch the correct translated content's ID. This ensures that each language displays the appropriate content without changing the original product ID in all languages. For more details on how to implement this, please visit the documentation on WPML Object ID Hook.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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 contact our support team at WPML Support Forum.
Please note that the solution provided 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 you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client has an ACF block with a radio field where the radio element's value should not be translated as it breaks the PHP code logic. Despite setting the field to not translate in the field group settings, it still appears in auto translate. Solution: We recommend adding the following code to your functions.php file:
After implementing this code, update the page in the default language and its translation. Remember to add the fields you wish to exclude from translation to the
$fieldsToIgnore
array.
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 the problem persists, please open a new support ticket.
Problem: The client is experiencing issues with 'Invalid post type' and 'Invalid taxonomy' errors after attempting to translate custom post types and taxonomies using the 'Post Types Unlimited' plugin, which is not listed in WPML's compatible plugin directory. Solution: 1. Navigate to WPML > Settings > Post Type Translation. 2. Set the translation preference for the post types 'ptu' and 'ptu_tax' to 'Not Translatable'. 3. Go to the 'Post Types Unlimited' plugin, delete any translations of custom post types and taxonomies. 4. Clear your site's caches and check if the post types are now accessible. If the issue persists, we recommend replicating the problem in our sandbox environment to isolate the issue. You can access the sandbox here: WPML Sandbox Environment.
If these steps do not resolve the issue or if it seems outdated or irrelevant to your case, please 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. For further assistance, you can contact us directly through the WPML support forum.
Problem: The client is experiencing issues with currency conversion when creating orders in USD on a staging site, where the shop currency is THB. Specifically, the unit price is not converting correctly and is using the base currency price as if it was in USD, resulting in an incorrect discount being applied. Solution: We have identified that this issue is already known and is scheduled to be fixed in a future version of WooCommerce Multilingual. As a temporary workaround, we recommend the following steps: 1. Edit the order and click on the pencil icon to change the product quantity. 2. Press the Save button. 3. Edit the order again and revert the quantity to the original amount. 4. Press the Save button again. This workaround should correct the unit price display after saving the order.
Please note that this solution might be irrelevant if it's 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 open a new support ticket.
Problem: The client is unable to translate references on their website using WPML with the Premium Addons for Elementor. The references are displayed in Danish instead of English. Solution: We modified the XML configuration for the Elementor widget used by the client. Here is the updated XML configuration:
<wpml-config><br /> <elementor-widgets><br /> <widget name="premium-addon-testimonials"><br /> <fields><br /> <field>premium_testimonial_person_name</field><br /> <field>premium_testimonial_company_name</field><br /> <field editor_type="VISUAL">premium_testimonial_content</field><br /> <field>heading</field><br /> </fields><br /> <fields-in-item items_of="multiple_testimonials"><br /> <field>person_name</field><br /> <field>company_name</field><br /> <field>heading</field><br /> <field editor_type="VISUAL">content</field><br /> </fields-in-item><br /> </widget><br /> <elementor-widgets><br /></wpml-config><br />We asked the client to check if the translated page now displays correctly.<br /><br />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. Additionally, we highly recommend checking related known issues at <a href="https://wpml.org/known-issues/">https://wpml.org/known-issues/</a>, 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 <a href="https://wpml.org/forums/forum/english-support/">WPML Support Forum</a>.
Problem: The client is experiencing an issue where items added to the WooCommerce cart appear in the checkout process but the main cart page shows empty. Solution: We found that the issue might be related to the use of blocks within an Elementor text widget. We recommend replacing these blocks with the WooCommerce cart shortcode
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: After updating WPML plugins, the client's site stopped functioning correctly. Products and pages were not accessible in Arabic, and the cart appeared empty when switched to Arabic. Solution: We identified that the issue was due to an endpoint translation in String Translation (wc/file/transient). We resolved the problem by deleting this endpoint translation, which restored the functionality of products and pages in Arabic.
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. Additionally, 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, please visit our support forum at WPML support forum.
Problem: The client is experiencing issues with WPML's Automatic Translation not working for Russian and Finnish languages despite having activated the Pay-as-you-go mode. Solution: 1. We recommended switching the default language to English and then attempting the automatic translation again. 2. Upon further investigation, we discovered that the Pay-as-you-go mode was actually deactivated. However, records showed that translations from English to Finnish and Russian were successfully completed after the last communication. If you're experiencing this issue, we recommend checking if the Pay-as-you-go mode is activated and trying to switch the default language to English. If the problem persists, please confirm the status so we can assist further.
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, do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing a critical error warning on the Arabic interface of their website, and the Arabic homepage is automatically redirecting with a 410 status, indicating that the resource is no longer available. Solution: We recommend checking if the Arabic resources are still available on the server. If they are, proceed to clear all caches on the site, including server-level caches if applicable. Follow these steps: 1. Take a full backup of the site, including the database. 2. Navigate to the root directory of your site using the File Manager in your hosting control panel. 3. Locate the '.htaccess' file and open it in an Editor. 4. Copy the contents to your computer for backup. 5. Replace the '.htaccess' rules with the default WordPress rules, which can be found here: https://wordpress.org/documentation/article/htaccess/#basic-wp 6. Save the changes and try accessing the Arabic page again.
If these steps do not resolve the issue, we suggest 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 with us for further assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
