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

[v15 rc2] BlockEditorCustomView forContentTypeAlias property not working for block list #17316

Closed
warrenbuckley opened this issue Oct 18, 2024 · 3 comments
Labels
state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug

Comments

@warrenbuckley
Copy link
Contributor

warrenbuckley commented Oct 18, 2024

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

15.0.0-rc2

Bug summary

When following the tutorial for creating a BlockEditorCustomView that can be used in block list and block grid.
https://docs.umbraco.com/umbraco-cms/tutorials/creating-custom-views-for-blocklist

If you set the forContentTypeAlias property then block list does not load the custom element, as soon as you remove it then it will load.

Specifics

IMG_0009

Steps to reproduce

  • Create two properties on a doctype
  • One that is blocklist and the other a block grid
  • Create two or more element types and configure them to be used in the above editors
  • Follow documentation
  • use the forContentTypeAlias property and target a single elementtype alias
  • Add example content that uses both blocks in block list and block grid
  • Notice only the block grid will load the custom element
  • Remove the property from the manifest and now all element types will get the custom element as you would expect based on the manifest
  • This now includes the block list as well, so it does not work when you set the property to target an element type

Expected result / actual result

That the forContentTypeAlias property works with block list


This item has been added to our backlog AB#45398

Copy link

Hi there @warrenbuckley!

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

@bergmania bergmania added the state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks label Oct 31, 2024
@nielslyngsoe
Copy link
Member

Fixed by umbraco/Umbraco.CMS.Backoffice#2515

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug
Projects
None yet
Development

No branches or pull requests

3 participants