사용 가능한 솔루션

Problem:
The client was experiencing issues with the automatic translation feature in WPML where the modal window displaying the cost calculation process would appear, but then nothing would happen. The Dev-Tools network tab showed that the first request returned an error indicating 'No translations found for element type post_acf-field-group and ID 166', although there was an entry in the database with element_id = 166 but with element_type as 'post_post'.

Solution:
We identified that the issue was due to incorrect 'element_type' values in the 'wp_icl_translations' table for entries where 'wp_posts.post_type' was 'acf-field-group'. We executed the following SQL commands to correct the 'element_type' to 'post_acf-field-group' for these entries:

UPDATE wp_icl_translations INNER JOIN wp_posts on wp_posts.id = wp_icl_translations.element_id SET wp_icl_translations.element_type = 'post_acf-field-group' WHERE wp_posts.post_type = 'acf-field-group';

After applying this fix, the automatic translation dialog was able to calculate the cost without any issues, and the requests no longer resulted in errors.

If you're experiencing similar issues, we recommend checking the 'element_type' in your database and ensuring it matches the 'post_type'. If the solution provided here does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If problems persist, do not hesitate to open a new support ticket.

Problem:
If you switch to Chinese Simplified on your homepage, you encounter a fatal error.
Solution:
We found that some strings contained placeholders like

%1$s

,

%3$s

which were either missing or incorrect in the Chinese translation. This discrepancy caused the fatal error. We corrected these placeholders in the affected strings, ensuring they are formatted correctly, such as changing

%1$

to

%1$s

.

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 https://wpml.org/forums/forum/english-support/.

Problem:
The client noticed a discrepancy in the mobile view between the English and Spanish versions of their website, specifically when viewed on actual smartphones. The Spanish version appeared to be forcing a desktop view.
Solution:
1. We initially suggested clearing all site caches, which did not resolve the issue.
2. We then recommended switching to a default WordPress theme temporarily to isolate the issue, which the client could not implement due to the site being live.
3. After creating a staging site, we discovered that the page had a duplicated meta viewport declaration, which WPML translated incorrectly, causing display issues in the Spanish version.
4. We disabled the raw HTML setting in WPML > Settings and asked the client to resend the content for translation, which resolved the problem.

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 issues persist, please open a new support ticket at WPML support forum.

Problem:
The client reported a critical issue with WPML Advanced Translation Editor (ATE) on a live WooCommerce + WPML multilingual store. When sending a product for automatic translation using ATE, the translation process crashed and created fatal errors, specifically an 'InvalidArgumentException'. Despite several actions such as clearing WPML cache, switching to Classic Translation Editor, and deactivating conflicting plugins, the issue persisted.
Solution:
We performed several troubleshooting actions under WPML → Support → Troubleshooting. After these adjustments, we tested translations on the client's site with successful results in both Arabic and Persian using ATE. We asked the client to verify if the issue was resolved on their end and to check if the translations were performed correctly.

If you're experiencing similar issues, we recommend trying the following steps:
1. Navigate to WPML → Support → Troubleshooting and run the necessary troubleshooting actions.
2. Ensure that your Automatic Translation account ID is correctly updated and matches the records.
3. Test the translation with a few products to confirm functionality.

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