[Resolved] I'm having some issues with WPML on our site (hidden link).
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing issues with WPML on their site. Specifically, the translated values of custom fields are not showing in the default WordPress editor, despite being set to translate in the settings. Additionally, registered shortcodes in WPML > Settings > Custom XML Configuration are not automatically translated. Solution: For the custom fields issue, we recommend the following steps: 1. Navigate to WPML > Translations. 2. Select all posts checkboxes. 3. From the Bulk Actions dropdown menu, select "Approve translation reviews". 4. Apply this action to all posts. After these steps, the translated fields should be visible in the WordPress editor for secondary languages. It is crucial to use only one editor consistently; if you have used WPML's translation editor, avoid editing directly using the WordPress editor and vice versa. For the shortcode translation issue, we have created a separate support ticket to address this specifically. You can follow the progress and find solutions here: https://wpml.org/forums/topic/split-taxonomy-translations/edit/
Please note that the solution provided 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.
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'm having some issues with WPML on our site (hidden link).
I am trying to:
1. Custom Fields: The translated values of custom fields aren't showing in the default WordPress editor, even though they are set to translate in the settings. However, the translations for the custom fields do show up in the Advanced Translation Editor.
2. Shortcodes: I've registered shortcodes in WPML > Settings > Custom XML Configuration, but they are not automatically translated. Link to a page where the issue can be seen: hidden link
hidden link
Symptoms:
Custom Fields: The translated values of custom fields aren't showing in the default WordPress editor, even though they are set to translate in the settings. However, the translations for the custom fields do show up in the Advanced Translation Editor. Shortcodes: I've registered shortcodes in WPML > Settings > Custom XML Configuration, but they are not automatically translated.
Questions:
Why aren't the translated values of custom fields showing in the default WordPress editor?
Why are the shortcodes not automatically translated even after registering them in WPML > Settings > Custom XML Configuration?
New threads created by Lucas Vidal de Andrade and linked to this one are listed below:
Regarding issue #01: Can you please provide more details?
How do you reproduce the issue, step-by-step?
Please note that automatic translation only works with WPML's Advanced Translation Editor, it doesn't work if you have the WordPress Editor activated, if that might be the case.
Regarding issue #02: I've created a new ticket for it. This way, we can ensure both issues will be addressed and that they can be looked into in parallel. You can access it here: https://wpml.org/forums/topic/split-shortcodes-custom-xml/
I'll answer you there. Thanks in advance,
Lucas Vidal
we have entered the English values for those custom fields and translated everything. but after switching the language, the translated value are not populating in the custom field, although its showing the wpml advanced translation editor
Thank you for sharing the details. Please provide me with a link of a page, where I can see this issue.
###
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.
You will find the needed fields for this below the comment area when you log in to leave your next reply. 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. Let me know if this is ok with you.
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. If you do not, please ask me to enable the private box. The private box looks like this:
First and foremost, I need to know exactly which fields are showing the issue and how I can reproduce the error from scratch (the steps you followed to create the ACFs, as well as your WPML settings).
As for the access, if you can't give full admin access, please send me a copy of your website. You can use Duplicator to create it and share the zip file with us via Google Drive. Here you can find more details:
Unfortunately, I wasn't able to install the Duplicator Package you provided. There seems to be a problem with the naming of the file. The file-name is a secure individual name provided by the plugin, which seems to be incorrect.
Can I login and create a copy from scratch? I will try again with Duplicator, in case it does not work, I will use All In One WP Migration.
I've enabled the private fields, so you can share the credentials privately.
I checked the local copy of your website and noticed that almost all the CPT Product translations were in “in review” status. To solve, I followed these steps:
1. Go to WPML > Translations;
2. Select all posts checkboxes;
3. On the Bulk Actions dropdown menu, select “Approve translation reviews”;
4. Do that for all posts;
Thereafter, I was able to still see the fields inside the WordPress editor, in secondary languages. Please note, that it's essential to use only one editor. That means, if you translated the page using WPML's translation editor, you should never edit directly using the WordPress editor. Use either one or the other. Otherwise, you might have problems.
