Problem: The client de-authenticated Skrivanek and deleted the connection, but all translation jobs are still pending and cannot be canceled, showing the error: 'This action does not apply to any of the selected translation jobs'. Solution: If you're experiencing this issue, we recommend you try the following steps: First, check if the translation job can be canceled: 1. Go to WPML → Translation Management → Jobs. 2. Check whether the translation jobs are listed there and see if you can cancel them. If you are unable to cancel the job from there: 1. Go to WPML → Translation Management. 2. Select the page for which you want to cancel the translation job. 3. Send it again for translation. 4. Choose Translate myself, and you should then be able to translate it manually from WPML → Translations.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. 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, you can also visit our support forum at WPML Support Forum.
Problem: The client reported an issue where the job titles in the 'Team' section of their website were not translating correctly. The titles were visible in the translation editor but did not display on the frontend. The content was built using the Elementor 'Team' widget, and the issue persisted even after scanning all plugins and making minor edits.
Solution: We discovered that the untranslated job titles were being pulled from 'Item Options' which are not included in the translation editor, unlike the Elementor fields. To resolve this, we manually translated the tagline. We recommend checking if similar issues are occurring with other items pulled from 'Item Options' and manually translating them if necessary. For further assistance, please visit our support forum at WPML Support Forum.
Please note 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 issue persists, do not hesitate to open a new support ticket.
Problem: You are trying to set up pay-as-you-go for three websites, but when activating it on the first website, you encountered an error indicating that the payment was declined, despite the card being actively used for other transactions. Solution: We have determined that the payment was declined by your bank. We recommend contacting your card provider directly to find out why the payment was declined and to ensure that future transactions are processed successfully.
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. Should you need further assistance, please do not hesitate to open a new support ticket with us.
Problem: Product variations do not appear on a translated language.
Solution: For the issue with product variations not appearing: - Navigate to WooCommerce > WooCommerce Multilingual > Attributes tab. - Select the attribute assigned to the product and ensure that the terms have been translated into other languages. - Scroll down and click on the Synchronize Attributes button to synchronize the attributes. - If the problem persists, go to WPML > Support > Troubleshooting, select "Product" from the dropdown under "Cleanup", and click on Synchronize post taxonomies.
For the issue with "My Account" translations:
Additionally, editing the product in the original language and making a small change to the content, then saving and updating the translation can help display attribute images on the translation category page.
Please note that the solution provided might be irrelevant due to being 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 necessary, do not hesitate to open a new support ticket for further assistance at the WPML support forum.
Problem: The client is experiencing issues with the translation of the WooCommerce "My Account" page. The main page appears translated, but the translations do not persist on the subpages of the account.
Solution: We recommend updating the WPML and WPML String Translation plugins to their latest versions, as this has resolved the issue on a staging site. Follow the steps below: 1. Update WPML to version 4.6.10. 2. Update WPML String Translation to version 3.2.10. 3. Verify if the issue with the translation of the "My Account" page is resolved. You can refer to our documentation for automated updates: https://wpml.org/faq/install-wpml/#automated-updates
Please note that this solution might be irrelevant if it's 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 you need further assistance, please open a new support ticket: https://wpml.org/forums/forum/english-support/
Problem:
Trying to translate the filters. All of the attributes are translated, and page and HTML blocks are translated, yet in the French language only the translated Filter button appears, but two filter fields with attributes are not appearing.
