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

Block Grid is not rendering the layout or contents in areas #17604

Open
mjamil4it opened this issue Nov 21, 2024 · 1 comment
Open

Block Grid is not rendering the layout or contents in areas #17604

mjamil4it opened this issue Nov 21, 2024 · 1 comment
Labels

Comments

@mjamil4it
Copy link

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

15.0.0

Bug summary

Umbraco 15.0.0 is not rendering blocks in areas. 
If I add a block in the root, it gets rendered fine. But if I add a block in the area then try to render, it does not work. 

I have tested this on the fresh install of Umbraco 15.0.0 or upgraded V14 to V15, but areas do not get rendered.
There is no error in the logs. 

It seems like Block Grid completely ignores the areas. 

Specifics

No response

Steps to reproduce

Create an element with RTE as a property, call this RTE Block
Create an element with no properties, call this container layout

Create Block Grid property, Add RTE block and allow in area only. Then add Container layout allow in Root only and in area tab create a 12 grid area. Area can be two, three or any number of columns.

Add this block grid property on the document type.

Create a page using this document type and in block grid add container and within container add RTE block with some text.
Save and publish.

Nothing get rendered.

This approach works from V12 to V14.

Expected result / actual result

Area should be rendered.

Copy link

Hi there @mjamil4it!

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