Problem: You are using automatic translation to translate all Elementor pages into Spanish, but only the header and footer appear translated. Solution: First, check your WPML settings by navigating to WPML->Settings and look for the option 'What would you like to do after WPML finishes translating your content automatically?'. Ensure that the settings are configured correctly to publish translations automatically. Next, visit one of the translated pages to confirm that it is 100% translated and published, not just waiting for a review. If these steps do not resolve the issue, it might be due to outdated solutions or a unique problem not covered here. 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to send a translation job to a translation service but encountered an error that prevents the job from being sent. Solution: We recommend trying to send the translation job again. If you're experiencing this issue, it might have been caused by your site being blocked on our servers. We have unblocked it, so please attempt to resend the translation job. If the problem 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 this solution does not resolve your issue or seems irrelevant, please open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to translate the Bricks Builder shop template, but it is not redirecting to the ATE translation page. Instead, you encounter an error with the URL indicating 'ateJobCreationError=101'. You have tried reassigning the translation multiple times without success. Solution: First, verify if this issue occurs only with this specific page or with other pages as well. If it's isolated to this page, it might be due to corruption. To address this, navigate to WPML > Translation Management and send the template for translation to yourself. Then, retrieve it from WPML > Translations. This process will initiate a new translation job, potentially resolving any corruption issues from previous attempts.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, it's advisable to check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and ensure that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client is experiencing an issue where a page translated into German is displaying mixed content in English, German, and sometimes Italian. This problem arose after switching between the Classic Translation Editor and the Advanced Translation Editor (ATE). Solution: We recommend the following steps to resolve the issue: 1. Ensure that the WPML plugin and all related add-ons are updated to the latest version. You can check for the latest versions and update instructions here: http://wpml.org/faq/install-wpml/ 2. If the page was initially translated using the Classic Editor, switch back to it to recover most of the translations. Review and fill out any missing items, then save the changes. 3. If you wish to switch to the ATE, open the existing page and its translation in a new tab, then switch to the ATE and manually fill out the existing translation or use automatic translation, which may require credits. For more details on switching editors, visit: https://wpml.org/documentation/translating-your-contents/using-the-translation-editor/switching-from-classic-to-advanced-translation-editor/
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 was experiencing an issue with WPML 4.7.1 where attempting to access translation jobs resulted in a 'Jobs could not be loaded' error. The ATE Error logs indicated a cURL error 6: Could not resolve host. The client suspected database corruption and noted that the issue persisted even after flushing the site cache and using WPML Troubleshooting options. Solution: We recommended removing the 'Translator' from WPML > Translation Management > Translators, which resolved the issue with loading translation jobs. Additionally, we suggested removing the translation job for the 'custom page' template, which was causing the translation queue to crash due to its lack of static content. After these adjustments, the translation jobs and queue were accessible again.
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, please open a new support ticket at WPML support forum.
**Problem:**
You are experiencing difficulties with category translation in WPML, particularly with category thumbnails disappearing when translating WooCommerce products. After translation, categories display a default thumbnail instead of the original image.
**Solution:**
To resolve this issue, we recommend re-saving the translated categories. Here are the steps to follow:
1. Access the translated category in the WPML admin interface.
2. Click the 'Update' button at the bottom of the page.
3. Verify if the category image appears correctly.
If the issue persists, you may need to repeat these steps for each translated category.
If this solution doesn't resolve your issue or appears outdated, we recommend checking the [known issues](https://wpml.org/known-issues/) and ensuring that you have the latest versions of themes and plugins installed. If needed, feel free to open a new support ticket on our [support forum](https://wpml.org/forums/forum/support-en-francais/).
Problem: Sie haben festgestellt, dass die automatische Übersetzung von Deutsch zu Niederländisch nicht funktioniert, obwohl Sie nur WPML Beta KI für Übersetzungen aktiviert haben. Beim Versuch, automatisch zu übersetzen, erhalten Sie eine Fehlermeldung. Solution: Der Grund für das Problem ist, dass die KI-Übersetzung für das Sprachenpaar Deutsch ↔ Niederländisch derzeit deaktiviert ist. Unsere KI liefert für dieses Paar keine ausreichend hochwertigen Übersetzungen, und es wird derzeit nicht unterstützt, wie auf der Seite https://ate.wpml.org/mt_langs angezeigt. Wir arbeiten an einer klareren Darstellung unterstützter Sprachpaare. In der Zwischenzeit könnten Sie als temporäre Lösung Deepl für Übersetzungen verwenden. Außerdem wurde das Sprachenpaar Deutsch-Niederländisch kürzlich von unseren Entwicklern erstellt und getestet, aber noch nicht freigegeben. Bitte versuchen Sie es jetzt erneut, da es mit WPML AI aktiviert sein könnte.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen unter https://wpml.org/known-issues/ zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum unter https://wpml.org/de/forums/forum/deutsches-forum/.
