Problem: The client was experiencing issues with content not displaying correctly after translation using WPML on their website. Specifically, a block in Blocksy content blocks was not showing correctly, and the Fluent Forms form submit button was missing from string translations. Solution: 1. We recommended checking the WPML String Translation section in the WordPress dashboard to search for any untranslated strings related to the problematic content. 2. If the strings were not listed, we suggested using the Debug info to ensure all settings were correct and that the strings were properly registered for translation. 3. For the Fluent Forms submit button, we advised ensuring that the button's string was correctly scanned and available in the String Translation interface. If not, rescanning the plugin files might be necessary.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Please also 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. For further assistance, you can contact us directly through our support forum.
Problem: You are experiencing issues with WP All Import where products are being imported into a different language than the one you set during the import process. Solution: We are aware of this issue and it will be resolved in the next release of the WPML Export & Import plugin. Please keep an eye out for the upcoming release. We will announce it through a blog post and provide detailed documentation on how to implement this. 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 this solution becomes outdated or does not apply to your case, please open a new support ticket. We highly recommend visiting our support forum for further assistance at WPML Support Forum.
Problem: The client is developing a site and needs to auto-translate product titles that are in Lithuanian, a language not available on their website, into English. Solution: We recommended creating a Lithuanian language option for the purpose of importing products and then auto-translating them to other languages. The client can hide the Lithuanian language from the website's front end and set English as the default language after completing the translations. For ongoing product imports, the client can use the WPML Translation Management Dashboard to automatically translate batches of content. Additionally, we advised the client to use the WPML translation memory to leverage previous translations and reduce costs. For more details on using automatic translation with custom languages, visit https://wpml.org/documentation/automatic-translation/using-automatic-translation-with-custom-languages/.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client encountered an issue where products imported in Italian were automatically moved to Lithuanian after running a cron job for updating product information using WPML and WP All Import Multilingual plugin. Solution: We discovered that the problem occurs because the Italian language was set to hidden. When a language is hidden, and a cron job is executed, WPML defaults to creating the product in the primary language instead of the intended hidden language. This is due to hidden languages being visible only to logged-in users, and therefore, not accessible to cron requests. To resolve this, we recommend: 1. Unhide the Italian language. 2. Import the products as drafts. 3. Publish the products once they are ready.
Please note that this solution might not apply to your situation if it's outdated or not relevant to your specific case. If the issue persists, we highly recommend checking the 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.
