[Waiting for user confirmation] ACF fields don't all show up on translator editor

We did not change any settings for any field groups or fields between the languages. They should be identical, unless WPML changes any settings or requires additional steps for the settings to be identical.

Hello,

To address your message:

In ACF, when clicking to a field group, I always select "Same fields across languages."

If I leave that page where the three options are, or refresh the page, it just goes back to asking me to select again. It is not clear how to save this as a WPML setting.

I have now clicked "Save Changes" to the ACF field group (although no changes were made to the field group). For now, this seems to have kept the setting of "Same fields across languages" within the WPML dialogue box on the page.

******
--> This might have been the root cause of the issue. After clicking to "Save Changes" it appears that all the fields are now in the WPML Translation Editor.

Can the following be reported as an issue?

It would help if your user interface could include a big note or way to save the "Multilingual set up" settings in the WPML dialogue box, within the ACF field group page, so that future cases like this don't recur.

This is because, once a WPML method is selected, a WPML confirmation appears, which makes it seems like it was saved, even though it wasn't.

After the WPML confirmation appears, the "Save Changes" button, which is part of the ACF user interface, not WPML, appears to be applicable only if changing fields. But in this case, no fields are being changed at all.

Since WPML seems to be 'injecting' it's settings into ACF, it seems natural that it would have it's own "Save" button.

Please see screenshot attached.

******

Regarding your other comments:

I am definitely using WPML Translation Editor. It is set as our translation editor under WPML > Settings. I only used the WordPress Editor to complete the translations because some of the fields did not show up in the WPML Translation Editor, while some did. This solved my problem. There was no other way to do it...

I selected to only allow WordPress editing for the individual posts where I needed to publish the fields, and not for all future posts. The issue persisted.

See screenshots attached.

-----------

We are not using the same field name more than once in field groups. We only have one field group.

Screenshot is attached.

--------

Regarding this part of your message:

"You should never mix those methods - they can not be used at the same time. If you edit translation on the WordPress Editor while having the WPML Translation Editor set as the translation method, your edits will get lost once you translate again with the WPML Translation Editor."

We would love to only use the WPML Translation Editor as our one place to enter the translations. However, we had no way of adding the ACF field translations that did not appear in the WPML Translation Editor.

This was confusing. Even if we *did* need to save the setting to use the same field group across all fields, it doesn't make sense that only some of the field groups showed up in the WPML Translation Editor, and not all of them.

It is also strange that your plugin would behave this way. We need flexibility to translate with both the Translation Editor and WordPress Editor, such as in this case and others. Is there a way to allow both types of editing? Is this on the WPML roadmap?

---------

Could you please explain this part of your message:

"- The ACF Field Groups need to be set to "Not translatable" at WPML > Settings > Post Type Translation.
- If you earlier translated the field groups, please remove their translations."

I set the Post Type to "Not translatable" to see if this would fix the issue. However, after I did that, there was no option to translate the posts at all, let alone the missing ACF field groups...

We needed to translate the posts and *all* the fields in the field group. Could you explain why we would set them to be not translatable to fix this issue? The post type in question, with the ACF fields tied to it, is "Faculty." It is now set back to "Translatable - only show translated items." It is now allowing to translate the posts and field groups. Is this not right?

If we translated the field groups before, and now remove them, how will this help to be able to translate ALL the field groups, and not just some of them, in the WPML Translation Editor going forward?

Would we have to re-enter all of those fields in the WPML translation editor?

-----------

Thank you.

Thank you for the clarification. The ACF Field groups are set to "Not translatable" and this option is 'greyed out' so that we can not change it. I have attached a screenshot to confirm.

I understand that ACF changes require clicking on "Save Changes". However, the confusion is that it does not appear that clicking "Save Changes" is necessary with WPML's options on that screen, since WPML gives another confirmation message to indicate that it's own settings have been saved.

I understand they don't have their own save button.

I am pointing out that when you click one of the options in the screenshot you showed me, a confirmation message appears. You can see it in a screenshot I provided above.

This confirmation message makes the user think that the setting has been saved. This is confusing, because it is not saved when that confirmation message appears.

Yes, but what you are saying here: "there is only an overview about which mode is currently set " - this is not correct. It is not "set" until someone clicks to "Save Changes."

I am just saying that in UI design, when someone clicks an option, and then they get a message that makes it appear like their option is now "set", the brain may not think there is another step to "set" it.

If they click on an option, and nothing happens (i.e. no message appears at all), then it would trigger a thought to click on "Save Changes" so their option can be "set."

At the very least I think WPML should consider adding a note in that confirmation box that the settings need to be saved by clicking on "Save Changes."

This is especially the case since the WPML settings on that screen are not part of the native ACF UI. It a separate box discussing WPML's integration with the plugin.