Background of the issue:
I am trying to use WPML to translate my WordPress site. The custom field boxes do not appear in the block editor for translated versions.
Symptoms:
Custom fields not showing in translated version on editor.
Questions:
Why are the custom field boxes not appearing in the block editor for translated versions?
1) Make sure that the ACF Field Groups are set to "Different fields acrosss languages" when editing the groups in ACF.
2) Set WPML > Settings > Post Type Translation > ACF Field Groups to "Not translatable".
When using the WordPress-Editor for translating the content, then the only way to translate custom fields, is by editing manually on the translated content.
If you would like to use the "Expert" mode for your ACF Groups, you should set the custom fields to "Copy once" in such case, which will copy them only once and they then can get edited on the translated post or page while using the WordPress Editor.
Could you please increase the WordPress memory limit (WP Memory Limit) to at least 256 MB? WPML requires a minimum of 128M.
Your current values are:
PHP Memory Limit 400M
WP Memory Limit 40M
To do this, you need to connect to your website's server and open the wp-config.php file in a text editor. The file is located in the WordPress root directory.
Add this code to the wp-config.php file to increase WordPress memory:
define ('WP_MEMORY_LIMIT', '256M');
Add this just before this comment:
// That's all, stop editing! Happy blogging.
The current values can be viewed under WPML > Support > WordPress.
These settings can be restricted directly by your hosting provider. Therefore, I recommend contacting them and asking them to change them directly if the changes are not applied immediately.
Thank you. I followed the 2 steps (screenshots attached). But unfortunately still there are no custom field settings in the block editor (screenshot attached) when editing the translated version.
I would like to offer to take a closer look into this issue and request temporary access (wp-admin and FTP) to the site to investigate the issue further.
The required fields are below the comment 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 the site and database before granting us access.
If you can't see the "wp-admin / FTP" fields, your post and site login details 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" here to create a copy of the site that I can use to investigate the issue further.
However, I would also be very grateful if you could provide a staging site or copy of the website from your server for this purpose.
If you have any questions about creating such a staging site, you can consult your hosting provider. Please note that WPML must also be registered on this staging site at https://wpml.org/de/account/websites/.
If you are not able to provide such a copy of the website for testing, please let me know on this ticket.
The private reply form looks like this: hidden link
The next time you reply, click on "I still need assistance".
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We are not allowed to access any credentials that were not specifically submitted on this ticket in the private response form.
My apologies, but the ACF Fields are not even showing up on your original portfolio items, even if I disable WPML. This means, the issue is not caused by WPML.
I suggest you keep disabling plugins or switch the theme to identify what is causing the issue.
Hello. We do see them on the original Portfolio items. I showed this in the video.
For example, you can go here to edit this original portfolio item: hidden link
And you should see the custom fields on the right. I have attached a screenshot.
My apologies, I was not checking the sidebar and expecting the fields to show up beneath the content.
The fields are also available on the translated portfolios. See screenshot.
Possibly I misundertood you. Are you expecting the original field values to be copied when translating the portfolios with the WordPress Editor?
If so, then the current field groups setting "Different fields across languages" should copy the values only once for images but not for text. This is explained in detail here:
I have now tested this with a new portfolio and the images are copied as expected, the text fields are empty. This is expected.
If you expect the original text field values to be copied when creating the translation, then I suggest you set the ACF Field Group to "Export" mode and set the text fields to "Copy once". This will copy the text values only once, when translating them for the firs time. After that you will be able to edit the translations manually.
