- Issue created by @alecsmrekar
- 🇮🇹Italy plach Venezia
This is working well in our project, we "just" need to add test coverage now :)
Automatically closed - issue fixed for 2 weeks with no activity.
When a translation is added for an entity, the workspaces module will attach the translation to the default revision, and that operation will run outside of a workspace. That is problematic, because all code that reacts to the event will run its logic in the live workspace. One such example is Drupal\path\Plugin\Field\FieldType::postSave that will create a path alias in the live workspace.
1. On a multilingual site create an unpublished node in the Live workspace
2. Create a new workspace
3. Add a manual path alias to the english/default language of the node, and publish the node
4. Add a translation for the node (language of your choice)
5. Notice that two path aliases (instead of one) get created in the selected language
Instead of attaching the translation to the main revision in the live WS, do it in the current WS.
Post a MR
Needs work
11.0 🔥
workspaces.module
This is working well in our project, we "just" need to add test coverage now :)
Automatically closed - issue fixed for 2 weeks with no activity.
