Active
Project:
Entity Browser
Version:
8.x-2.x-dev
Component:
Widget selector plugins
Priority:
Normal
Category:
Plan
Assigned:
Unassigned
Reporter:
Created:
9 Mar 2019 at 10:42 UTC
Updated:
25 Apr 2019 at 21:06 UTC
Jump to comment: Most recent
Comments
Comment #2
oknateWhen I first started to look at these issues I wasn't aware of '#widget_context' on the entity browser element.
Check out #2761833: Widget context and validators not passed to Entity Browser element for more information on this feature.
Comment #3
oknateComment #4
oknateAfter testing again, I think 2832240 makes less sense than 2865928 and 3038854.
Url argument path parts are more fragile than getting target_bundle and parameter from original route. For example on node form, the path /node/add/article changes once the entity is saved. Also, with entity embed, the url path parts would need to be overridden to get the original pages path parts. This is why a hook or the contextual default value view plugin makes more sense.
Even though the module supports url path parts already, I don't think this is the most stable way to get contextual filter arguments to the view.
Comment #5
oknateComment #6
oknateComment #7
oknateComment #8
oknateComment #9
oknateComment #10
oknateComment #11
oknateComment #12
oknateComment #13
oknateAdded an updated patch to #3039038: Provide views filter that limits based based on allowed bundles that fixes exposed filters option.
Comment #14
oknateComment #15
oknateComment #16
oknateComment #17
oknateComment #18
oknate