Problem: After installing WPML to translate their website, the client's site became very slow. The client wants to know why and how to resolve the performance issue. Solution: 1. Increase the WP Memory Limit to at least 128MB, ideally to 256MB for optimal performance. Open the
wp-config.php
file and add the following line just before the comment that says '// That's all, stop editing! Happy blogging.':
define('WP_MEMORY_LIMIT', '256M');
2. After updating the memory limit, clear any caches (plugin, browser, and server-side if available), then check your site speed again. 3. If the site remains slow, deactivate all plugins except WPML and its add-ons to check for plugin conflicts. Reactivate them one by one to identify any specific plugin causing slowdowns. 4. Enable object caching and configure a caching plugin like W3 Total Cache for improved performance.
If these steps do not resolve the 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 the problem persists, please open a new support ticket for further assistance.
Problem: The client is trying to turn off automatic translation in WPML due to running out of credits and encountering errors that the system does not recognize manual translations. Solution: 1. To disable the automatic translation feature, navigate to WPML > Translation Management and turn off the "Translate Everything Automatically" option. 2. If pages are stuck in the process of automatic translation, causing pop-up warnings, you can resolve this by: - Going to WPML > Support > Troubleshooting and clicking on the "Cancel in-progress automatic jobs" button. - Alternatively, navigate to WPML > Translation Management > Jobs, find the problematic jobs, and click the red "X" icon to cancel them.
If these steps do not resolve your issue or if the solution becomes 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. Should the problem persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was unable to translate the string '0€ of 15000€ funded' using WPML on their website, even though the translated string was visible. Solution: We recommended the following steps to resolve the issue: 1. Navigate to WPML >> String Translation page. 2. In the 'Auto register strings for translation' section, enable the 'Look for strings while pages are rendered' option. 3. Revisit the page on the front end where the string appears. 4. Return to the WPML >> String Translation page and search for the strings. 5. Translate the string and then uncheck the auto-registration option. This process should allow the string to be translated correctly. For more details, you can refer to our documentation on finding and translating strings.
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.
Problem: If you're experiencing issues with displaying only one flag in the language switcher on your website, such that when the site is in Croatian, only the English flag is visible, and vice versa. Solution: We recommend following these steps: 1. Navigate to the WPML >> Languages page. 2. Click on the 'Edit language switcher' icon. 3. In the language switcher settings popup, disable the 'Current language' option and press the save button. This adjustment will ensure that only the opposite language's flag is displayed in the language switcher.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: The client was unable to find and translate a specific string in the header of their website using WPML. Solution: 1. To make the custom Marquee Elementor element compatible with the WPML Translation Editor, we added the following XML configuration in WPML >> Settings > Custom XML Configuration section:
After this, we made a small change in the default language header template and translated the header in the secondary language. This made the marquee element content available for translation. 2. For translating the 'Donation' text, we followed these steps: - Navigated to WPML >> String Translation page. - Clicked on the 'Translate texts in the admin screen' link at the bottom of the page. - Searched for the string and enabled its translation. - Assigned the correct source language and added the translation of that string. - Cleared the cache to reflect the updated translation. For further details, you can refer to the following documentation links:
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 reported that the Donate button was only functioning on the English version of their website, not on the Croatian version. Solution: We identified that the issue was due to multiple instances of the same ID being used for the Donate button, which is generated by the Donations Plugin. Here are the steps we took to resolve the issue: 1. Accessed the Elementor Header template in the default language. 2. Replaced the shortcode
[dp_donation_modal]
with
[dp_donation_modal_off]
in the template. 3. Advised the client to remove or replace the shortcode in other places where it appeared but was hidden in the desktop view. To avoid similar issues in the future, we recommended either using the button ID only once per page or updating the plugin code to use a class selector instead of an ID for JavaScript triggers. The popup should now work in both languages. We asked the client to confirm if the issue was resolved.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please do not hesitate 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. For further assistance, you can contact us directly through our support forum.
