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

Single Block Mode Behavior in v14+ (not single enough) #18115

Open
krebil opened this issue Jan 24, 2025 · 1 comment
Open

Single Block Mode Behavior in v14+ (not single enough) #18115

krebil opened this issue Jan 24, 2025 · 1 comment
Labels

Comments

@krebil
Copy link
Contributor

krebil commented Jan 24, 2025

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

15.1.1

Bug summary

I've noticed that in v14 and later, the behavior of single block mode has changed a bit. Previously, it automatically removed the "Add" button and inserted the block directly when only one type was allowed.

I really value the option of using an element type as a single block—it's such a powerful feature, especially when paired with custom views for blocks. The new backoffice makes implementing these custom views a breeze, which is awesome!

It would be great to revisit how single block mode works to bring back some of the previous functionality.

For reference:
#17309
#13216

Specifics

Image

Image

Steps to reproduce

Steps To Reproduce
Steps to reproduce the behavior:

  1. Try to create a single block mode block list, by creating a block list with just one available block, min-max of 1-1, and Single Block Mode checked.
  2. Verify that the block is not created automatically and the add button is still showing on the content side

Expected result / actual result

Expected behavior
The add button is hidden and the one available block would be added automatically

Copy link

Hi there @krebil!

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 🤖 🙂

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

No branches or pull requests

1 participant