-
Notifications
You must be signed in to change notification settings - Fork 203
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
EZP-29531: Do not render layout when rendering selection and relation items #2205
Conversation
This comment has been minimized.
This comment has been minimized.
Ping :) It would help a lot if this could land into 7.0 final :) |
pong @lserwatka / @Nattfarinn |
I'm fine with this. I don't see any reason why layout should be used here. |
Hello @emodric, |
@webhdx Great! But since these are generic templates used basically everywhere, it should be fixed here too. |
@emodric But you pointed out AdminUI, not a frontend template. What other uses do you have? AdminUI was resolved in the given PR. |
I pointed out admin ui specifically, because we have frontensld templates overriden with this fix. But the issue stands. |
Right not, those templates are a bit outdated to be honest. Fixing one, does not solve all problems we have here. I would rather fix all of them as part of bigger story for 7.1 kernel. |
As you wish. My point is that we as most of our client override them to fix this issue. Hence the PR |
The thing is, that we are very late in the process now. We are tagging final tomorrow. We can prioritise story for basic field types core templates for next release and include fix like this. |
No problem, I understand :) |
Closing for now. We will get back to this change as part of bigger for story for core base templates. |
@lserwatka re-opening this, as this template is also used on front for field type rendering (the changes in content_fields.html.twig) making sure they correctly use the layout parameter is good both in terms of use as as well as making sure people don't think noLayout is what is supposed to be used on this side of things. Hence making sure the layout => noLayout parameter conversion works as intended. @emodric can you rebase on 7.2? |
bfe362c
to
9cee529
Compare
@andrerom Done. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
9cee529
to
6e8dbd0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, let's fix it. But why not for 6.7? ping @andrerom
This one should be for 6.7 now as the other PR was closed, you fix @emodric ? |
6e8dbd0
to
550d25b
Compare
6.7 is fine ofcourse :) Rebased. |
blocks to disable rendering the entire layout Part of the declined PR at ezsystems/ezpublish-kernel#2205
So, is this going in? :) |
🤕 Forgot about this one, sorry for the delay, but yes this is going in 👍 |
@andrerom Better late than never :) Is it going to end up in 7.3 final? |
Yes :) |
Without this fix, rendering relation and selection items in eZ Platform Admin UI v2 looks like this:
With the fix, it looks like this: