Skip to content
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

15-rc: Block Editors: Unable to create a Settings model in the flow of setting up a new block #17434

Open
sofietoft opened this issue Nov 6, 2024 · 1 comment · Fixed by umbraco/Umbraco.CMS.Backoffice#2518
Labels

Comments

@sofietoft
Copy link
Contributor

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

15.0.0-rc3

Bug summary

I wanted to set up some blocks (using the Block Grid) for testing, but run into what looks like a bug when attempting to create a Settings model for the block.

Specifics

No response

Steps to reproduce

  1. Create new data type
  2. Add the Block Grid property
  3. Add new block by creating a new one
  4. Add a settings model by creating a new one

When you get to this point, it will ask you to stay or discard changes. If you click "Discard changes" something weird happens - it closes some of the editors behind what's open in the infinite editing mode.

block-grid-bug.mp4

Expected result / actual result

No response

@sofietoft sofietoft changed the title Block Editors: Unable to create a Settings model in the flow of setting up a new block 15-rc: Block Editors: Unable to create a Settings model in the flow of setting up a new block Nov 6, 2024
@nielslyngsoe
Copy link
Member

This PR umbraco/Umbraco.CMS.Backoffice#2518
Fixes the root cause of this, but it results in the 'Create New Element Type' action going away. So this issue is still relevant, but less of an issue now. More of a feature request.

I have created a task for this in our next sprint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants