Skip to main content
9 events
when toggle format what by license comment
S Oct 11, 2022 at 9:57 history suggested TheodorosPloumis CC BY-SA 4.0
Add version for DO file since HEAD does not exist, fix minor typo
Oct 11, 2022 at 7:34 review Suggested edits
S Oct 11, 2022 at 9:57
Nov 15, 2015 at 22:31 vote accept Libertardian
Nov 15, 2015 at 9:39 comment added 4uk4 I've read the core issue. Now I understand. The contextual filter in views is now based on the plugin context, so when the end user uses this in views, this is done with plugin context in the background. Otherwise it would not work in drupal 8 now. Great work.
Nov 15, 2015 at 9:17 comment added 4uk4 That is interesting, you can do a lot more with the plugin context. Coming from drupal 7 I would use a view block with a contextual filter to display fields of the current node. What is the drupal 8 way to do this?
Nov 15, 2015 at 9:11 comment added Berdir See drupal.org/node/2287073 for a core issue that adds context to views blocks. That for example allows the same views block to filter by a context, without hardcoding it to default to the current node. Again, very useful in page manager, where you can e.g. use the same views block to show content for different terms.
Nov 15, 2015 at 9:09 comment added Berdir No, plugin context is not only about visibility.Condition plugins are just one type of plugins that can use conditions. Any type of plugin can be made to work with them. Core just doesn't use it for that, but it works perfectly fine. I'm using it a lot together with page manager for example.
Nov 15, 2015 at 9:07 comment added 4uk4 Great explanation, the plugin context is about visibility. Libertardian should use a view block, as NoSssweat explained in the comment on the question. This will be invisible, if no node is in the current route, so context is not needed for the task.
Nov 15, 2015 at 8:57 history answered Berdir CC BY-SA 3.0