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
Working with multiple dimensions (eg. language) can lead to inconsistent node links between dimension especially regarding structural purposes (Shortcuts).
Example
Editor 1 is creating a Shortcut A in dimension EN. Editor 2 is not aware of the fact that Editor 1 already crated Shortcut A and creates a new Shortcut A in dimension US, instead of starting the "copy dimension" process.
Solutions
A solution would be the possibility to sync newly created Neos.Neos:Document nodes with a specific name (whitelisting) to all other configured dimensions.
Hint
As far a I know, Sitegeist is using something similar in their taxonomy package to sync taxonomies. But I'm not sure if this is a 100% match.
The text was updated successfully, but these errors were encountered:
A solution would be the possibility to sync newly created Neos.Neos:Document nodes with a specific name (whitelisting) to all other configured dimensions.
General
Working with multiple dimensions (eg. language) can lead to inconsistent node links between dimension especially regarding structural purposes (Shortcuts).
Example
Editor 1 is creating a Shortcut A in dimension EN. Editor 2 is not aware of the fact that Editor 1 already crated Shortcut A and creates a new Shortcut A in dimension US, instead of starting the "copy dimension" process.
Solutions
A solution would be the possibility to sync newly created Neos.Neos:Document nodes with a specific name (whitelisting) to all other configured dimensions.
Hint
As far a I know, Sitegeist is using something similar in their taxonomy package to sync taxonomies. But I'm not sure if this is a 100% match.
The text was updated successfully, but these errors were encountered: