You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 9, 2024. It is now read-only.
I'm setting up a multisite craft project with site groups. Every group is another location and has other contact information (address, email, phone, ...). I'm using the craft-fields plugin to create the necessary fields to provide this contact information through the CMS. Since every location (site group) has different contact details, i'm setting the "Translation method" to "Translate for each group site group". For the NSM Address and NSM Email fields this seems to work as expected, but when choosing this method for the NSM Telephone field it doesn't work correct. The phone number isn't updated for each site in the group when, the one site is updated and the other sites in the group have just a blank phone field.
Could you look into this please?
Thanks in advance,
Thomas
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi all,
I'm setting up a multisite craft project with site groups. Every group is another location and has other contact information (address, email, phone, ...). I'm using the craft-fields plugin to create the necessary fields to provide this contact information through the CMS. Since every location (site group) has different contact details, i'm setting the "Translation method" to "Translate for each group site group". For the NSM Address and NSM Email fields this seems to work as expected, but when choosing this method for the NSM Telephone field it doesn't work correct. The phone number isn't updated for each site in the group when, the one site is updated and the other sites in the group have just a blank phone field.
Could you look into this please?
Thanks in advance,
Thomas
The text was updated successfully, but these errors were encountered: