- Issue created by @effortDee
- 🇩🇪Germany jurgenhaas Gottmadingen
My first thought is that the views module is producing those "rankings" at the render level, i.e. very late in the process. So, every approach that would try to shortcut that process would actually lose out that most important information. In other words, you need views to do the full processing and then afterwards hide those parts that you're not interested in.
That said, hiding the unwanted rows can either be done with some post rendering or with CSS. While manipulating an existing render array with ECA can become pretty complicated, if even possible, hiding the unnecessary rows with CSS might be the much simpler approach in this context. You would have to add some context related classes to the views rows, so that your css can make the decision on what to hide and what to show.
That approach should work with tables and other formatters, as long as the rows are identifiable by css selectors.
Unfortunately, that doesn't sound like a task for ECA.
- 🇬🇧United Kingdom effortDee
Thankyou, i appreciate the reply!
I was just seeing some vague ideas as how to implement this across the web with mentions of Rules so thought I would ask here as I have not used ECA yet.
Again, thanks!
- Status changed to Fixed
12 months ago 9:51am 10 April 2024 Automatically closed - issue fixed for 2 weeks with no activity.