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
Currently, when publishing, deleting and publishing a page in a different dimension an error is thrown:
After reloading the whole page, there are two unpublished changes.
When publishing the changes, and using the dimension switcher to switch to german, it shows the following error:
No content collection of type Neos.Neos:ContentCollection could be found in the current node (/[99f81405-8781-4f3b-a6ba-8606a8be66d6]/neosdemo) or at the path "teaser". You might want to adjust your node type configuration and create the missing child node through the "flow structureadjustments:fix --node-type Neos.Demo:Document.LandingPage" command.
Expected Behavior
The page should be copied and the UI should show the 'new' page.
Steps To Reproduce
discovered on Neos Demo
Go to page 'Features'
Click on 'German' in dimension Dropdown to create new page in different dimension
Choose 'Create and copy' to create new page
Publish to live workspace
Delete 'Features' in the current german dimension
Switch back to English dimension and go to 'Features' page
Click on German in dimension dropdown to create new page in german
Chose 'Create and copy' to create new page in german
Environment
- Flow:
- Neos: 9.0
- PHP: 8.2
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
Currently, when publishing, deleting and publishing a page in a different dimension an error is thrown:
After reloading the whole page, there are two unpublished changes.
When publishing the changes, and using the dimension switcher to switch to german, it shows the following error:
Expected Behavior
The page should be copied and the UI should show the 'new' page.
Steps To Reproduce
discovered on Neos Demo
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: