I'm encountering some complications with content synchronization and lock icons on translated pages while using WPML and ACF plugins on my website. Both plugins have premium version installed on the website. Here are the key details:
I've set up a global ACF field group with multiple layouts, fields, and repeater fields nested within it to customize content across my site. As recommended in WPML documentation, I've configured the translation options for this field group to "Same fields across languages." See the attached screenshot.
However, when I save changes to this global field group in the backend, lock icons appear on translated pages, preventing me from editing content. Additionally, encounter content loss issues in translated pages when saving changes to the default language page.
Oddly, repeatedly saving the global field group eventually removes the lock icons from the translated pages. However, this action also causes content mismatch between the default language and its translations.
In summary, despite setting the "Same fields across languages" option, I'm experiencing content synchronization issues and lock icons on translated pages.
Any insights or solutions would be greatly appreciated.
While waiting for one of my colleagues to help you, please note that if you are using the option ""Same fields across languages."" this means that you are copying the fields from the default language to the translation.
In this case even if you were able to edit the translation fields they would be overwritten again with the values of the default language.
See the following descriptions from our documentation:
Same fields across languages – This option is best when you want to translate your content and keep your field values the same in all languages, like in the example for product descriptions on a tech website.
Different fields across languages – You can opt for this translation option if you want different content, a different number of fields, or a different layout in each language, as seen in the tutoring website example.
In your case, you might want to use Different Fields across languages, or possible using the 'expert' option
We want to inform you that we've attempted using the "Different fields across languages" setting for this ACF field group as well. However, even with this setting, we've encountered lock icons on the ACF fields within translated pages. We're experiencing the same content loss issues in translated pages when saving changes to the default language page, and we're unable to update content for these fields.
Once you fix this, please try to resave the translations and see if the issue is solved.
If not, please send me screenshots with the affected fields' configuration (notice there is a limit of 1M per image) and explain in details what you're trying to achieve.
As you mentioned above we need to increase the memory limit but this has already been done.
My main objective is to maintain identical fields and layouts on both the default and translated pages, with only the content adjusting based on the language. Despite opting for the "Different fields across languages" option for the field group, I'm still encountering lock icons on the ACF fields within the translated pages. Screenshots for both scenarios have been provided for reference.
I see a multiple checkbox field there, in this case if you use "same fields across languages" it's set to copy and it's expected you can't edit it. Values should be copied from original after saving, if it doesn't happen we need to investigate why.
For other fields I can't tell what is the expected behavior. I should access the site and see the settings.
If you're okay with this, please provide me with the credentials. Also please tell me which fields are you expecting to edit and the field group they belong to.
It seems to me it's working as expected. The field with the lock have "copy once" as translation preference which means you can change them after you save the page for the first time.
This is because you set "different fields across language"
If you want to use "same fields across languages" try changing the setting and update the home page so I can check the issue again and see if it's behaving as expected
According to WPML documentation, if we select the "different fields across language" translation option in the ACF field group, we can't set translation preferences (Translate, Don’t translate, Copy, and Copy once) on individual fields. These options are only available in the EXPERT translation option.
As you mentioned in the above reply, the "copy once" translation preference is applied to the lock field, but I'm unable to locate where this translation preference is configured for this field group because the "different fields across language" option does not provide the ability to set translation preferences.
Additionally, even after updating the translation page, I still observe lock icons on the fields.
Could you please provide more insights?
If feasible, we would appreciate scheduling a call with your technical team to address the matter promptly. We need to resolve this issue asap.
The preferences are set in the plugin's files directly. If you use either "Same fields" or "Different fields" you aren't supposed to configure anything so we do not display the translation preferences. It would be confusing since you can't edit them anyway.
I'm asking if seeing the lock on "copy once" fields is expectd or a bug. In any case, it would be just a cosmetic one since the behavior is the one you should have (= you can edit the fields after they're saved once).
Unfortunately, we don't do calls, all the support comes through the forum.
The challenge is that we maintain separate instances for development (dev), staging, and production. Our deployment process involves making changes on the staging instance first and then syncing the full staging instance to the production instance. However, we often encounter difficulties when transferring numerous settings from staging to production.
Could you provide guidance on minimizing changes required on the production instance or suggest any automatic settings that can streamline the syncing process from staging to production?
Allow me to clarify that during the process of copying the entire staging instance to the live instance, we consistently encounter the need to update certain settings.
This includes indicating whether it is the original or copied site through a checkbox. Additionally, we must update the site key obtained from the WPML plugin since the site key for the staging instance differs from that of the live instance.
Managing these settings each time poses significant challenges for the client. Is there a method by which we can copy the staging instance to the live instance with minimal adjustments required?
New threads created by Laura and linked to this one are listed below:
Since this is a different issue, I split the ticket.
Please confirm the initial problem is solved.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
