-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maps not propagating #141
Comments
Just as a comment: The Map field should respect "translation method" |
Can confirm. The field will work on the default site but doesn't seem to work on entries for other sites in a multi site setup. |
Any updates on when this will be fixed? :) |
For a new project I came across the same bug. I would look forward to a bugfix, too. On the other hand, I have implemented a temporary workaround by adding the SiteId, under which the entries were originally entered, for the affected entry query . |
I started on a PR to fix this issue, but it proved too time-consuming. I did implement a working hotfix though – Maps are implemented as a custom Element type, so by listening to the Here's the code – this should be added to a custom Craft module or plugin. I can't promise that it's airtight, but it's working well on my end, for the moment. Note that the hotfix a) will always propagate the Map field value across sites for new elements, and b) does not account for all the different translation methods; simply whether the field is set to "Not translatable" (any changes to the field will also be propagated across sites) or not (the field will only be propagated when the element is first saved, not for any further changes to the field). |
Maps don't propagate across sites.
The text was updated successfully, but these errors were encountered: