Available Solutions

Problem:
The client is experiencing an issue where, after translating a page from Polish to English using WPML, the frontend still displays the original Polish text, even though the Translation Management shows the translation as 100% complete.
Solution:
The WPML support team identified that the issue was related to a 'Lordicon' element, likely from a custom plugin to customize Bricks installed on the site. The problem was escalated to the 2nd-tier support, who isolated the cause and applied a workaround. They modified the code in the file

themes/bricks/includes/integrations/wpml/wpml.php

to ensure proper translation handling. The client was advised to contact Bricks support for a permanent fix and was provided with the workaround to apply on the production site if necessary.

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 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 needed, please open a new support ticket at WPML support forum for further assistance.

Problem:
If you're experiencing issues where automatic translation does not initiate or gets stuck when trying to translate new content, and there are no error logs displayed, this might be similar to the issue we addressed.

Solution:
First, we recommend checking the ATE error logs by navigating to WPML->Support->ATE Error Logs in your dashboard to identify any errors that might be preventing the translation process. If no errors are listed there, it's possible that an error 500 occurred.

Next, enable debugging in your WordPress environment to capture more detailed error information. You can do this by editing your

wp-config.php

file:
1. Change

define('WP_DEBUG', false);

to

define('WP_DEBUG', true);

2. Add the following lines just before 'stop editing here':

ini_set('log_errors', TRUE);<br />ini_set('error_reporting', E_ALL);<br />ini_set('error_log', dirname(__FILE__) . '/error_log.txt');

This setup will create an

error_log.txt

file in your site's root directory, which can help us diagnose the issue further.

If these steps do not resolve the issue or if you prefer not to perform them yourself, we can provide a staging environment to investigate the problem without affecting your live site. Please let us know if you wish to proceed in this manner.

Keep in mind 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.

Problem:
If you're experiencing issues with the translations of ACF fields not displaying correctly on your car detail pages, it might be due to the configuration of your field groups.
Solution:
We recommend setting your ACF Field Groups to 'Not translatable'. You can do this by navigating to WPML → Settings → Post Types Translation. If you have previously created duplicates of these field groups for each language, please delete the duplicates and retain only the default language version. Additionally, ensure that each field within the group has the translation preference set to 'Same fields across language' if you are using the WPML editor to translate. This setup should help WPML correctly synchronize and display the ACF values across different languages. After making these changes, update your default language page, then re-translate, and it should resolve the issue.
For more detailed guidance, you can visit these links:

• Advanced Custom Fields Field Group Should Be Set as Not Translatable
• Translate sites built with ACF

If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please open a new support ticket.

Problem:
The client noticed that their WPML license was renewed twice on different dates (March 4th and March 8th), resulting in being charged twice.
Solution:
If you're experiencing a similar issue with double charges on your WPML license, we recommend contacting us at https://wpml.org/home/contact-us/contact-form/. We will provide the necessary guidance.

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 at WPML support forum for further assistance.

Problem:
You are experiencing an issue with translating older pages using WPML. When attempting to open a page in the translation editor, you receive an error indicating that WPML tried to translate the page three times and failed. The temporary workaround involves making a small change to the original page, saving/updating it, and then opening the WPML translation editor, which is not feasible for many pages.
Solution:
We recommend trying to update pages in bulk to resolve this issue:
1. Select multiple pages using bulk actions.
2. Make a small change.
3. Update them in bulk.
4. Then revert the change and update again.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.