Background of the issue:
I am trying to manage translations using the 'Translate myself' method in WPML > Settings. After changing the translation method, all translation jobs are automatically assigned to my user account as a local translator, and they are getting stuck in the translation queue. I attempted to resolve this by removing the translator, clearing pending jobs, and trying to reset the translation method, but the system does not allow it. My user is no longer listed under translators. The issue can be seen here: hidden link.
Symptoms:
Translations are automatically assigned to a removed translator and get stuck in the translation queue. When I open and confirm translations from the queue, nothing happens. I expected to choose between automatic and manual translation without assigning jobs to a local translator, but instead, I got a blank page.
Questions:
How can I stop translations from being automatically assigned to a removed translator?
How can I reset the translation method to allow choosing between automatic and manual translation?
How to use ATE without assigning translation job to a local translator?
I recently changed some settings in WPML, and now every time I use the Advanced Translation Editor (ATE), the system automatically creates a translation job and assigns it to a “local translator” (which is my admin account).
This was not happening before. I used to open the ATE, translate, and publish directly, without any job assignment or waiting process.
I have already:
Removed all local translators in Translation Management
Deactivated "Translate Everything Automatically"
Reset the professional translation state.
Enabled ATE under “How to translate posts and pages”
Still, ATE creates a job and assigns it to a translator.
How can I use the ATE as an admin and translate + publish directly without assigning the job to a local translator or going through the translation queue?
I want to keep using the ATE features (memory, glossary, etc.) but avoid the job assignment step.
Welcome to WPML support. I will answer this ticket before the ticket is assigned to one of my colleagues.
First thing first please do as follows:
- Go to "WordPress Dashboard > WPML > Languages > Language filtering for AJAX operations".
- Make sure that the "Store a language cookie to support language filtering for AJAX" option is checked.
- Click the "Save button".
- IMPORTANT STEP! Create a backup of your website. Or better approach will be to test this on a copy/staging version of the website to avoid any disruption of a live website.
- Go to "WordPress Dashboard > WPML > Support > Troubleshooting (link)".
- Click the buttons annotated in the screenshot below one by one and wait for each button process to finish: https://wpml.org/wp-content/uploads/2020/10/7206941-buttons.png
I need to request temporary access (wp-admin and FTP) to your site—preferably to a test site where the problem has been replicated if possible—in order to be of better help. When you log in to leave your next reply, you will find the needed fields below the comment area. The information you will enter is private, meaning only you and I can see and access it.
Before I take a closer look, could you please try the following steps?
1. Go to WPML → Translation Management → Jobs
2. Cancel the translation job for the About page.
3. Temporarily disable the amazon-s3-and-cloudfront-pro plugin.
4. Make a small change to the original product and save it.
5. Then, navigate to the WPML Translation Editor to complete the translation.
1. WPML → Translation Management → Jobs → cancelled the job.
2. Disabled **amazon-s3-and-cloudfront-pro** (WP Offload Media).
3. Made a small change on an Elementor page and saved.
4. Re-translated the page via the WPML Translation Editor.
**Result**
* For Elementor pages, everything now syncs correctly: once the translation is completed, the content updates immediately in all languages.
**Remaining issue**
* **Blog posts’ featured images** still do not sync.
• A new translation does not pick up the image.
• When the source image is changed, existing translations keep the old image.
• This happens even with WP Offload Media disabled.
We do, however, need a final solution that works **with WP Offload Media enabled**, since S3 storage is required in production.
Could you advise on how to get featured-image sync working, and confirm that it will remain compatible once WP Offload Media is re-enabled?
I need to switch on WP Offload Media, because all the image are there.. so you'll find enable.
Do I understand correctly that the original issue (reported in this support ticket) does not occur when WP Offload Media is disabled using the steps I provided?
Itamar has already consulted with our team about this matter. Please continue the conversation in that ticket to avoid any confusion and duplicate troubleshooting. This will help us provide you with clear and consistent support.
