-
Notifications
You must be signed in to change notification settings - Fork 57
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
IBX-426: Created additional UDW config for adding Location to Content #1772
Conversation
@@ -105,7 +105,7 @@ | |||
|
|||
{% macro table_header_tools(form_add, form_remove, can_add) %} | |||
<button | |||
data-udw-config="{{ ez_udw_config('single', {}) }}" | |||
data-udw-config="{{ ez_udw_config('add_location', {}) }}" |
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.
I'm not sure about this one. @Nattfarinn correct me if I'm wrong but changing config name here is a BC break in case someone already used custom configuration for single
.
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.
There is a tiny risk of bahavioral BC here, but I wouldn't bother much with it. I don't think anyone ever would change our generic single
configuration to be anything else but multiple: false
(and even if he did we don't change configuration itself [big BC], but configuration key used just for this use-case).
Could you please rebase PR against current 2.2 branch? This should fix issues reporeted by CI. |
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.
I'm no expert in UDW, but LGTM.
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.
QA Approved on Ibexa Content, Experience, Commerce v3.3.4 with diff.
You can merge it up now. |
Merged into |
Add location
action should not take into account anycontent/create
restrictions, it should allow every content to be used as a destination if the user cancontent/read
it.Checklist:
$ composer fix-cs
)