[Resolved] jetengine custom post types meta field translation
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is unable to translate a JetEngine custom post type meta field that is a subfield of another field. Despite setting the field to translate in WPML, the translations do not appear in the frontend, especially after deleting a specific field from the post type custom fields. Solution: 1. To translate the field label, navigate to WPML > String Translation. 2. To ensure the field appears in the frontend in the translated language, edit the post in the Norwegian language, select the field options, and save. This action should make the translation field visible in the frontend. 3. If a field is deleted from the post type settings, re-update the post to fix any issues in the frontend. 4. Set the field preference to "Translate" if the field needs to be translated. Manually select the field in the Norwegian language to translate it. If the field value is the same across languages, ensure the items are checked to display in the second language. 5. Alternatively, set the field preference to "Copy" to copy all checked items into the second languages, but maintain the same field value in all languages and only translate the field label.
If this solution does not resolve your issue or seems outdated, 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.
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:
We want to translate a JetEngine custom post type meta field on each product. I have changed the settings to include the particular meta field (facilities), but it seems that it is not working. Maybe because the fields are a subfield of the field facilities.
Symptoms:
We can't find the translation for the JetEngine custom post type meta field.
Questions:
How can we translate a JetEngine custom post type meta field that is a subfield of another field?
Are there specific settings in WPML that need to be adjusted for translating subfields in custom post types?
Thank you for contacting WPML support, I’m happy to help you with this issue.
I suggest you go to WPML > Settings > Custom Fields Translation > Set the custom field preference to "Translate". Note: you may need to click on "Show system fields" to search for the field if the field name has the underscore (_) as the first character.
Then edit the post > Click on Update and re-translate the post to see if it helps.
The seetings where indeed correct, but the issue remains. Below we send you some screenshots to understand our situation better, is wpml fully compatible with jetengine custom post types fields(including checkboxes as is in our case)?
The settings look correct, 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 have a testing site where the issue is replicated. Your next reply is set to private to share the info.
❌ IMPORTANT: Please backup your database and website before proceeding ❌
You can use this plugin to create the backup: https://wordpress.org/plugins/duplicator/
✙ I would need your permission to de-activate and re-activate Plugins and the Theme to change configurations on the site if needed. This is also a reason the backup is critical.
Unfortunatly we have already tried this, if you look closely you will see that we have already translated to norwegian most of the words but if you go to each room in the norwegian language they are still in english in the Romfasiliteter( room amenities ) section
I understand the issue in the frontend. The field preference is set to Translate, but it isn't available in Advanced Translation Editor. You need to edit the post in the Norwegian language > Select the field options and save. Then you can see the translation field in the frontend, please check the attached screenshots.
this solved the problem, it worked okay but after deleting a specific field from the post type custom fields, now the norwegian is broken( i dont know if the deletion caused this but it was after it that we notice it). As you can see there is nowhere the norwegian translation although if you go to string translation there is. And they are all uncheck except for the ones where they have the same name for english and norwegian. Although Greek seems to be fine.
If you delete the field from the post type settings, you might need to re-update the post to fix the broken in the frontend.
Regarding the translation field, let me explain about your case. The field preference is set to "Translate", which means the field needs to be translated (select) to display in the second language. You manually select the field in Norwegian to translate it.
If the field value is the same across languages, the checked items will be displayed in the second language. If not, it will be unchecked.
You can use the field preference to "Copy" to copy all checked items into second languages but you have to keep the same field value in second languages and only translate the field label. However, Elementor only supports showing the field value in the frontend.
So the better way is to translate the field value and label, manually translate the field in second languages.
my problem i think is that i can not see the translated fields in others languages like i could before. I dont know how in your screenshot you can see all the fields in norwegian, in me i can see in english only.
I can still see the translation field label in the admin area. Can you share your admin account in the next reply so I can check this on my end?
❌ IMPORTANT: Please backup your database and website before proceeding ❌
Also, please check if the translation field is displayed in the frontend.
after some digging it was because my account language was english and not site default, now i have reverted to using site default settings on user language and the problem is resolved, maybe you should pass to the developer team because this sounds like a bug I think it should not happen. Generally we will not need further assistance. Thank you for your time.
