Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.In Panopoly 1.x, both the "Content item" and "Content list" widgets were views. In Panopoly 2.x, implementing a "Content list" as a view still makes sense, but we'd like for the "Content item" widget to be a custom plugin, ideally, in CTools, but we could implement our own if necessary.
We need to wait on all the fields and view modes to be available to create the "Content list" view.
We need to check out what's available in CTools before starting on the "Content item" block.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | panopoly_widgets-content-item-list-2729249-8.patch | 19.29 KB | dsnopek |
| #6 | panopoly-content-item-list-2729249-6.patch | 368 bytes | dsnopek |
| #6 | panopoly_core-content-item-list-2729249-6.patch | 615 bytes | dsnopek |
Comments
Comment #2
dsnopekI think this issue qualifies as being necessary for the MVP, so making a child of #2549709: [meta] Panopoly 2.x for Drupal 8 battle plan
Comment #3
dsnopekOr, maybe "Content Item" could be a custom block? It'd just be an entity reference field that renders the item in a particular view mode. Although, then that becomes "reusable" and that really never makes any sense...
Anyway, neither CTools or core has a decent "Content item" widget. We could create our own, I just worry about the reference field. I wonder if Drupal 8 FAPI has a reference field?
Comment #4
dsnopekHere's the start of the "List of content" view, however, it doesn't totally work because what 'ctools_views' gives us isn't sufficient: we can't keep the whole exposed form in the block configuration. Maybe there's a patch that does that, but the current ctools in Panopoly doesn't :-(
Comment #5
dsnopekHm, it looks like #2657060: Add Configure Filter functionality to block views configuration. is the CTools issue attempting to make using the exposed filters as block configuration, and it looks as though it's no where near a resolution :-/
It might make sense to split this into two issues if it seems like we could finish "Content item" before getting "Content list" working
Comment #6
dsnopekHere's a pile of patches that gets "Content list" more working. Actually, it's probably working enough to commit, given that we're still in -alpha. We can make more issues about making it work better :-)
"Content item" still needs to be implemented
Comment #7
dsnopekHere's a patch that also includes a "Content item" block. Not sure this is the best way forward, but it's worth trying and seeing if there's a compelling reason not to do it like this
Comment #8
dsnopekThis patch fixes a bunch of bugs in the "Content item" block. This is probably good enough to commit an initial version. I'll compare the D7 and D8 versions and create some follow-up issues
Comment #10
dsnopekCommitted!
Here's the follow-ups:
#2854948: Port features/UX of "Content item" widget from D7 to D8
#2854950: Port features/UX of "Content list" widget from D7 to D8