Problem: You are trying to use GraphQL with WPML on your site, but GraphQL is not functioning properly. The issue is identified with the WooGraphQL plugin, which is not officially compatible with WPML. The problem arises because the product model is unexpectedly transformed into a post model when WPML is active. Solution: We recommend contacting the WooGraphQL plugin author to discuss joining our compatibility program. Meanwhile, we have escalated this issue as a feature request for a new version of WPML GraphQL; however, it will take some time before this is considered and released. As a workaround, you can use the standard post schema to fetch products and their translations, which bypasses the schema conflict.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are using WPML to translate content on your site, but while translations are available, they are not visible on the frontend. Solution: First, ensure that the WPML String Translation can write in the necessary folder. This issue might be due to insufficient writing permissions. Contact your hosting provider to adjust these permissions as outlined here: WordPress File Permissions. After resolving the permissions issue, apply the workaround provided on the WPML errata page here: WordPress 6.7 .mo files not loaded and verify if the translations now appear on the frontend.
If this solution does not resolve your issue or seems outdated, we highly recommend checking related known issues at WPML 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 developing a site and wants to translate country names in product listings using WPML, while also looking to save credits. Solution: Currently, WPML does not support direct import of content for translation that is stored outside of the database. However, we recommend using WPML's translation memory feature, which can automatically translate strings that have been previously translated, thus helping to save credits. We are also actively working on adding functionality to better support your needs.
If this solution does not fully address your issue, 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 further assistance is needed, please open a new support ticket.
Problem: You are working on a site under development and need to understand the correct settings for translating product custom fields using WPML. Solution: When you install the WPML and WooCommerce Multilingual plugins, the default settings for WooCommerce product custom fields are configured correctly. If you are using custom fields not added by the WooCommerce plugin but have added them yourself, we recommend referring to our guide on how to translate specific custom fields. You can find the guide here: Translating Custom Fields.
If this solution does not apply to your case, or if it seems outdated, please check the 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 you need further assistance. You can do so here: WPML Support Forum.
