Background of the issue:
I am trying to complete translations for all pages, posts, and portfolio items on my site hidden link using WPML. I manually did all the translations using the + symbol, but only two pages and one portfolio item are fully completed.
Symptoms:
Almost all pages and posts remain stuck in translation progress and never finish.
Questions:
Why are almost all pages and posts stuck in translation progress and never finish?
How can I upload screenshots to provide more information?
Languages: English (English )German (Deutsch )French (Français )
Timezone: Europe/Zagreb (GMT+02:00)
Hi,
When you click on any of the circle buttons (which indicate that the original content was modified and the translation is pending an update), does it show the translation as 100% complete?
And after marking it as completed, does the pencil icon still not appear?
If that's the case, please do the following:
1. After returning from the translation editor, open your browser’s developer console and check for any error messages. Let us know what you see there.
2. Enable debugging in WordPress by editing your `wp-config.php` file. Add the following lines just before the line that says:
`/* That's all, stop editing! Happy publishing. */`
3. **Reproduce the issue**
Go through the exact steps you normally would—click the circle button, open the translation editor, make any changes, and mark it as completed. This helps trigger the conditions that may be causing the problem and ensures the relevant errors are logged.
4. Locate the debug log file at: `/wp-content/debug.log`
5. Copy and paste the last 10 lines of that file here (no need to include the entire log). Please redact any sensitive information.
Most importantly, after reproducing the issue (step 3), also try to get the latest **server error logs**. If you're not sure how to access them, your hosting provider should be able to help.
Regarding your help notes: No 1
Warning messages in my browser’s developer console:
--- In the home page (hidden link)
The only warning are 2 =
- Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies.
- [GroupMarkerNotSet(crbug.com/242999)!:A0309A01FC520000]Automatic fallback to software WebGL has been deprecated. Please use the --enable-unsafe-swiftshader flag to opt in to lower security guarantees for trusted content. uwoman.eu/:1
--- In the About Page (hidden link Which is the only page that has no problem with the second language, and the the pencil icon is good.
The only warning is = Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies.
=====================================
Regarding your help notes: No 2
Before making any corrections to the wp-config.php file:
When I open it, I found this line above the ... `/* That's all ...
Please try the following:
1. Resynchronise and resend jobs
- ❌ Please make a full website backup before proceeding ❌
- Go to WPML → Support → Troubleshooting.
- Click Synchronise local job IDs with ATE jobs and Synchronise translators and translation managers with ATE.  
- Next, open WPML → Translation Management → Jobs, cancel every job still “In progress”. 
- Edit the original (English) page/post, add a space, update, then resend it to translation. 
2. Clear caches / switch browser
❌ Please make a full website backup before proceeding ❌
- Empty all server‑side caches and disable optimisation plugins temporarily.
- Clear the browser cache or open ATE in Chrome Incognito
- Complete the translation
- If the WebGL warning keeps flooding, try with another browser (Firefox, Safari, Edge) and check if it works 
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue.
It would be better to a testing site where the issue is replicated.
The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I'll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site.
This will allow me to create a copy of your site and your content.
Once the problem is resolved I will delete the local site.
**IMPORTANT**
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields.

Hello,
I was trying to resolve the problem and I found this:
"WPML cannot send some fo the content to translation
Some of the content that you selected for translation includes fields that are encoded. Translators will not be able to work on this kind of content, so we removed it from the job.
To fix this problem, please contact our support team and describe this issue.
The “encoded‑fields” notice you now see pinpoints the root cause of the earlier “translations stuck in progress” problem: both Betheme’s BeBuilder and some Elementor widgets save design data inside custom‑fields or shortcode attributes that are base64‑encoded. WPML blocks any job containing such data unless you explicitly tell it how to handle those fields; the job then stays incomplete, and ATE never reaches 100 %. Once the encoded fields are registered (decoding or copying), translation jobs create and finish normally.
Does the issue happen when you only send one page to translate? If so, can you identify which of the elements of the page may contain the encoded content?
Hi,
When I send multiple pages for translation, the queue never end. When I send the homepage, a message alert about encoding fields appears.
Does it happen for all pages? How can I find these fields? Could you help me?
Thank you.
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue.
It would be better to a testing site where the issue is replicated.
The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I'll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site.
This will allow me to create a copy of your site and your content.
Once the problem is resolved I will delete the local site.
**IMPORTANT**
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields.
I just created a full backup today, about two hours ago.
If you find too many issues with the current situation, I also have a cleaner backup—created on May 1st, 2025—before the WPML installation and the action “Translate the entire website automatically.”
These steps allowed me to send the home page to translate in my local copy of your site:
- Go to WPML > Settings > Custom Fields Translation
- Search for: mfn-page-items-backup
- Set it to "Don't translate"
- Then go to WPML -> Translation Management and send the home to translation
Let me know if this fixes the issue for this and the other pages.
I followed the steps you gave me one by one.On the Translation Management page, under the Pages section, I found two "Home" pages:
1) Home – Date: 2025-04-30, Status: Published
2) Home – Date: 2020-10-15, Status: dp-rewrite-republish
I believe the second one is your local copy. It had a red circular symbol. After I sent this page for translation, it now shows a checkmark with the note: Ukrainian: Complete.
All the other pages still show the spinning symbol (running non-stop) with the note: Ukrainian: In progress (unassigned).
What can we do next? Please advise.
Best regards,
PS
I'm not sure if this helps, but during all these days with the Ukrainian translation issues, one page has consistently worked fine in both languages:
About – EN: (hidden link) – UK: hidden link
However, when I copy the UK URL, it appears encoded.
In WPML -> Support -> ATE Error Logs there are several errors like this one: WPML_PB_Handle_Custom_Fields::is_page_builder_page_filter(): Argument #2 ($post) must be of type WP_Post, null given, called in /home/customer/www/uwoman.eu/public_html/wp-includes/class-wp-hook.php on line 324 /home/customer/www/uwoman.eu/public_html/wp-content/plugins/sitepress-multilingual-cms/addons/wpml-page-builders/classes/Shared/tm/class-wpml-pb-handle-custom-fields.php:25
Betheme’s Muffin Builder stores its layout in several base64‑encoded custom fields (e.g., mfn‑page‑items, mfn‑page‑items‑backup, mfn‑page‑objects). When any of those fields are still set to “Translate,” WPML refuses to package the page for ATE and logs the PHP warning you now see: WPML_PB_Handle_Custom_Fields::is_page_builder_page_filter(): Argument #2 ($post) must be of type WP_Post, null given. That broken callback prevents WPML from finishing the job, so the status remains “Ukrainian: In progress (unassigned)” while the spinner never stops. One page (“About”) works because it contains no encoded fields.
I think I may have missed to check some fields:
- Go to WPML → Settings → Custom Fields Translation.
- Set the following fields to Don’t translate (or Copy if you need the same layout in every language):
-- mfn-page-items
-- mfn-page-items-backup (already done)
-- mfn-page-objects
- Save. Edit one problematic page, add a space, update, then send to translation; the spinner should disappear.  
Also, backup the site, then open WPML → Support → Troubleshooting and run:
- Clear the cache in WPML
- Remove ghost entries from the translation tables
- Fix element_type collation
- Set language information
- Fix WPML tables collation
- Assign translation status to duplicated content
- Fix terms count
- Fix post type assignment
- Cleanup and optimize string tables
On the same page:
- Click Cancel in‑progress automatic jobs and Synchronise local job IDs with ATE. 
- In WPML → Translation Management → Jobs, delete any job still flagged as In progress (unassigned).
- Resend the pages
I suggest you disable "Translate Everything Automatically" for a moment. Then you try sending only one page first. If it works, send the rest in small batches.
