Problem: If you're experiencing an issue where your event dates are displaying as '1 January 1970' instead of the actual start and end dates on your website using the Avada theme, this might be due to a conflict with WPML. Solution: We recommend the following steps to address this issue: 1. Ensure you have a backup of your website. 2. Add the following code to your theme's functions.php file:
3. Test this solution in a staging environment before applying it to your live site to ensure it does not cause other issues.
Please note that this solution might become irrelevant due to updates or may not apply to your specific case. If this solution does not resolve your issue or if you encounter other problems, 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, feel free to open a new support ticket at WPML support forum.
Problem: The client reported that activating WPML resulted in high levels of outgoing connections, CPU consumption, and database overflow. The specific issue was traced to the file
. After deleting and re-uploading a fresh copy of WPML, the problems persisted, including high CPU levels and database overflow. Solution: We requested the client to create a video detailing the steps that reproduce the issue and share it with us for a better understanding of the problem. Additionally, we asked for access credentials with administrator privileges to the site to allow us to replicate the described issues and investigate further. We also emphasized the importance of confirming that a full site backup is available, which can be restored if necessary.
Please note that the solution provided 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 issue persists, please open a new support ticket.
Problem: You are experiencing issues importing products using WP All Import with the WPML Import Export plugin installed. Despite following all instructions, you end up with more products in English than in another language, even though your Excel file has equal products listed as translations. Solution: We found that the import setting 'Skip WooCommerce products if their data in your file has not changed' was enabled, which we disabled and ran another successfull import.
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 at WPML support forum for further assistance.
Problem: The client reported that after re-importing their site from production back to staging, all previously translated Arabic content disappeared, and the WPML plugin was requesting new credits for re-translation. The client was concerned because the previously used translation credits were not being reflected, and they did not have unlimited credits to redo the translations. Solution: We explained that this behavior is expected if the sites are not connected or sharing the same translation memory. We confirmed that the client's staging site and the original site are connected and share the same translation memory with 2,571 segments. We clarified that the Translation Memory stores translations in segments (usually sentences or paragraphs), not by the number of credits used, and the amount of segments the client sees is within the expected range based on the credits used. We advised that there is no need to recover or reconnect anything as the existing translations should appear when translating similar content again. We also recommended checking the full usage and URLs translated by going to WPML > Translation Management > Tools and downloading the usage report for more detailed insight.
Please note that this solution might be irrelevant if it's 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 issue persists, please open a new support ticket.
Problem: If you're experiencing an issue where after translating a template in Bricks Builder using WPML, only the English version of the template appears in the template picker, and other language versions are missing, this might be due to the admin language settings. Additionally, all previously assigned templates might display a raw post ID instead of the template name. Solution: We recommend checking the language settings in your user profile on your WordPress site. Specifically, you should ensure that the option 'Set admin language as editing language' is not selected if you are working in a multilingual environment. This setting can cause Bricks Builder to load templates only in the currently set admin language, hence not showing other language versions in the template picker. After adjusting this setting, reopen Bricks Builder and check if the template picker now correctly displays templates in all languages.
If this solution does not resolve your issue, or if it seems 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 product categories not displaying correctly in English compared to German, and products not being assigned to the appropriate categories in English. This issue is linked to the Rentman plugin, which is not fully compatible with WPML. Additionally, other posts and pages are not translating properly, and menus are not synchronized between languages. Solution: 1. For the issue with product categories and products, we recommend checking the compatibility of the Rentman plugin with WPML. If it's not compatible, manual adjustments might be necessary. 2. To address the translation inconsistencies, go to WPML > Settings > Taxonomies Translation, locate
product_type
, and set it to 'Not translatable'. Then, navigate to WooCommerce > WooCommerce Multilingual > Status > Troubleshooting and run the tool to fix product_type assignment. 3. For issues with translating posts and pages, ensure that the Translation Memory is not incorrectly reusing German translations for English. Manually adjust translations or use the 'Translate automatically' option in WPML to ensure correct translations. 4. If these steps do not resolve the issues, we have opened a new ticket to investigate this further. Please continue the discussion there: https://wpml.org/forums/topic/split-translation-not-working-correclty/
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 the issue persists, please open a new support ticket for further assistance.
Problem: If you're experiencing issues with the Dual Color Heading widget from UAE for Elementor not translating correctly, where only two of the three strings appear in the Advanced Translation Editor, and the translations do not display in French, you might be facing a configuration issue. Solution: The issue has been reported to the plugin author. In the meantime, we recommend updating your WPML configuration. Here is the suggested configuration to ensure that the Dual Color Heading widget translates properly. Add this config to WPML > Settings > Custom XML Configuration:
<wpml-config>
<elementor-widgets>
<widget name="eael-dual-color-header">
<conditions>
<condition key="widgetType">eael-dual-color-header</condition>
</conditions>
<fields>
<field type="Dual Color Heading: Title ( First Part )" editor_type="LINE">eael_dch_first_title</field>
<field type="Dual Color Heading: Title ( Last Part )" editor_type="LINE">eael_dch_last_title</field>
<field type="Dual Color Heading: Sub Text" editor_type="VISUAL">eael_dch_subtext</field>
<field type="Wrapper Link" key_of="eael_wrapper_link" editor_type="LINK">url</field>
</fields>
<fields-in-item items_of="eael_dch_multiple_titles">
<field>eael_dch_title</field>
</fields-in-item>
</widget>
</elementor-widgets>
</wpml-config>
This configuration should help in correctly recognizing and translating the widget. You will now need to edit the widget on the original content, save the page or post you are working on, and then update the translation. 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client wishes to cancel their WPML subscription and request a partial refund after selling their practice and no longer needing the services, having renewed the subscription in February. Solution: If you're in a similar situation, we recommend waiting until your subscription expires, as it will be automatically canceled. Please remember that we offer a 30-day money-back guarantee if you are not satisfied with WPML. The refunds or partial refunds are not available once this period has passed.
This solution might be irrelevant if it's 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: You are considering not renewing your annual WPML subscription as the client you use it for is being offboarded soon, and you want to avoid paying for a full year that you won't use. Solution: We recommend switching to the Pay-As-You-Go plan, which does not require a monthly subscription fee. With this plan, the first 2,000 translation credits each month are free. If you exceed this limit, you will only be charged for the additional credits used. You can cancel this service at any time without financial penalty. For more details on pricing, please visit Automatic Translation Pricing. For more information on Pay-As-You-Go, including terms and conditions, visit Pay-As-You-Go Terms and Conditions. To learn how to stop Pay-As-You-Go, please follow the instructions here: How to Stop Pay-As-You-Go. Remember, WPML will continue to function on your site, and your existing translations will remain available and display correctly even if you stop Pay-As-You-Go or do not renew your subscription.
If this solution does not apply to your situation, 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 you need further assistance, please open a new support ticket.
Problem: The client purchased a 1yr subscription to "WPML Multilingual CMS" and is considering upgrading to "WPML Multilingual Agency" due to hosting 26 client sites on a WordPress multisite network, each with multiple environments, totaling 78 sites. Solution: We informed the client that when using Multisite, it is only necessary to register the main site using the site key. There is no need to register the subsites, as this is not supported.
If this solution does not fully address your concerns, or if it seems 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: If you're experiencing the issue where clicking the icon to translate pages results in the error message "WPML didn't manage to translate this page," we have a solution that might help. Solution: We recommend trying the following steps to resolve this issue: 1. Choose a page as an example. 2. Make a minor change to the page title (such as adding a letter), update the page, then revert the change and update it again. 3. Open the translation editor. This process forces WPML to refresh the translation job, which often resolves this type of issue. 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 open a new support ticket.
Problem: The client reported a significant visual discrepancy between the original English blog page and its Hungarian translation in Bricks Builder. Specifically, the header is not appearing as expected. Solution: If the menu items are too long, causing layout discrepancies, we suggested manually translating the menu to adjust the length of the items. For more detailed guidance, we provided a link to our documentation on translating menus: https://wpml.org/documentation/getting-started-guide/translating-menus/
If the solution provided does not resolve the issue or seems outdated, or if it does not apply 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 https://wpml.org/forums/.
Problem: If you're experiencing extended loading times with the Advanced Translation Editor (ATE) and encountering a 504 error, it might be due to certain WPML settings affecting performance. Solution: We recommend trying the following steps to potentially resolve the issue: 1. Disable the "Adjust IDs for multilingual functionality" setting. Test this on a staging site first to ensure that it does not affect your content adversely. 2. Turn off the "Track where strings appear on the site" feature to reduce database writes and improve performance, unless you actively use this feature for tracking. 3. Consider disabling Media Duplication, which includes duplicating media, featured images, and their metadata. This will not affect existing translated pages but will stop future duplications. 4. Note that disabling media duplication generally does not negatively impact SEO, as WordPress uses the same image file across translations. 5. After disabling media duplication, you can still translate image attributes like Alt text, Title, and Caption, but be aware that images might not display in secondary languages. 6. For existing duplicated media entries, manually review and remove unnecessary media as there is no built-in feature in WPML for automatic cleanup.
If these steps do not resolve your issue or if the solution becomes irrelevant due to updates or different circumstances, 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: A product with French as the default language was being incorrectly translated into Spanish instead of English, despite Spanish not being an active language on the site. Solution: 1. We recommended checking the active languages in WPML settings to ensure Spanish was not enabled. 2. We suggested checking for stray Spanish translations in the trash and deleting them if found. 3. We advised updating WPML plugins and verifying the correct language mapping for English. 4. We instructed the client to edit the product in the original language, make a minor change, save it, and update the translation. 5. The issue was resolved after resending the product for automatic translation.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If needed, please open a new support ticket.
Problem: The client asked if the WPML SEO plugin is necessary for compatibility with SEOPress, as it was with Rank Math. Solution: We confirmed that the WPML SEO plugin is not required for SEOPress. However, the client should ensure they have WPML Multilingual CMS and WPML String Translation plugins installed. For more details on optimizing WPML for search engines with SEOPress, visit https://wpml.org/documentation/plugins-compatibility/optimize-wpml-multilingual-sites-for-search-engines-using-seopress/.
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 visit our support forum at https://wpml.org/forums/forum/english-support/.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
