Unable to configure or delete block grid area in Umbraco 15.1.0

[stephen-sherman]

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

15.1.0

Bug summary

The umb-block-area-config-entry element does not render any contents, making users unable to customise the width of a block grid area or delete previously created block grid areas.

Specifics

No response

Steps to reproduce

1. Install a new Umbraco 15.1.0 solution
2. Configure a block grid data type to include a block with an area of non-default width

Expected result / actual result

Expected result

• When creating a block, be able to
  • Create an area
  • Set the width of an area (i.e.: 12 columns)
  • Be able to delete an area

Actual result

• Areas can be created, but the user interface for setting the width of an area or deleting an area is missing.

[github-actions]

Hi there @stephen-sherman!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[nielslyngsoe]

Hi @stephen-sherman

Thanks for spotting this, we did though already know about this and have it fixed, but there was an accidental too early release of 15.1. :-(

A Patch including this fix is on its way, it will then be versioned as 15.1.1. This will be out later today.

Sorry for the inconvenience