This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing issues with translating Custom Post Types (CPT) and their associated meta fields using JetEngine and WPML, where the meta fields do not appear as editable options within the translation screen, follow the steps below. Solution: 1. Confirm that you have set your translation preferences correctly by navigating to WPML → Settings. Ensure you have the following sections configured: - Post Types Translation – Set Listings, Components, Post Types, etc., to Translatable. - Custom Fields Translation – Set Meta Boxes, Meta Fields, etc., to Translate. If the fields handle settings that do not need a translation, set them to "Copy". - Taxonomies Translation – Set Custom Taxonomies, etc., to Translatable. Save these settings. 2. Edit one of the original post types, save it, and then open the translation editor. You should now see the metafields in the Advanced Translation Editor. For detailed guidance, visit How to Translate JetEngine with WPML. 3. If the metafields are still not translatable, go to WPML > Settings > Custom Field Translation and set each related field to "Translate". After setting, edit and save one of the affected original posts, then update the translation. For more information, check Translating Custom Fields. 4. If issues persist, we recommend backing up your website and providing temporary admin access for further investigation.
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 problem continues, please open a new support ticket.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I am trying to translate Custom Post Types (CPT) and their associated meta fields using JetEngine and WPML. I have multiple CPTs with meta fields, but when I attempt to translate them, the meta fields do not appear as editable options within the translation screen.
I have created a video to illustrate the issue: hidden link.
We are using the latest versions of WordPress, JetEngine, and WPML.
Symptoms:
The JetEngine meta fields in the Custom Post Types are not showing up as options to edit when attempting to translate them.
Questions:
Why are the JetEngine meta fields not appearing as editable options when translating CPTs?
Is there a specific setting or configuration needed to make meta fields translatable in JetEngine with WPML?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Madrid (GMT+01:00)
Hi there!
I’m leaving this first reply before one of my teammates continues with your ticket.
I checked your site and noticed that the translations remain “in progress”, which usually means there’s an issue preventing the jobs from being completed.
To help us identify the cause, could you please do the following checks?
1. Check the ATE Error Logs:
Go to WPML → Support → Advanced Translation Editor → Error Logs (or WPML → Support → WPML Troubleshooting → ATE Error Logs, depending on your setup).
Please copy and share any error messages you see there.
2. Plugin conflict test:
Temporarily deactivate all plugins except WPML, WPML Translation Management (or WPML Translation Control), WPML String Translation, JetEngine, and WPManage.
Then try to complete one of the translations again and see if it finishes correctly.
3. Finally, please confirm if this issue — translations stuck “in progress” — happens only with JetEngine post types or if it also affects Pages or Posts.
1. No error logs are available.
2. Done, still will not update meta fields in custom post type (Team is a good one to check as it has several meta fields)
3. I think Pages is showing as one, but it is because we haven't finished translating that one.
Before you can translate JetEngine with WPML, you first need to choose which content on your site is translatable.
To set your translation preferences, go to WPML → Settings and scroll down to the following sections:
Post Types Translation – Listings, Components, Post Types, etc.
Custom Fields Translation – Meta Boxes, Meta Fields, etc.
Taxonomies Translation – Custom Taxonomies, etc.
To enable a type of content for translation, set it to Translatable and Save.
IMPORTANT:
After that, edit one of the original post types, save it, and then open the translation editor.
You should now see the metafields (custom field values) in the Advanced Translation Editor.
If this is not the case, please let me know, and we can take further steps from there.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
To make the metafields translatable, you will need to go to WPML > Settings > Custom Field Translation and set each of those related fields to "Translate".
After that, edit one of the affected original posts, save it, and then update the translation.
If this does not solve the issue, I'd like to offer to take a closer look and request temporary access (wp-admin) to the website to investigate the issue further.
Please provide access as an admin user.
The required fields are located below the comments section when you log in to leave the next reply. The information you provide is private, meaning only you and I can see and access it.
IMPORTANT
Please be sure to back up your website and database before granting us access.
If you can't see the "wp-admin / FTP" fields, your post and website credentials will be set to "PUBLIC." DO NOT publish the data unless you see the required wp-admin / FTP fields.
I may need to install a plugin called "All In One WP Migration" to create a copy of the website so I can investigate the issue further.
The private reply form looks like this: hidden link
Click "I still need assistance" the next time you reply.
Video: hidden link
Please note that we are required to request this information individually on each ticket. We are not permitted to access any credentials that were not specifically submitted on this ticket using the private response form.
These fields were currently set to "Not translate". See screenshot.
I have adjusted these settings now.
You will now need to edit one of the original team members inside the WordPress Editor, save the post, and then open the translation editor. Complete the translation to 100%.
Do this for each team member.
If you still face issues after that, please let me know.
Thank you! I see why I was confused. I did not associate CPT with my actual META fields, so I didn't put two and two together. Now I know for next time.
