Updated: Comment #0
Problem/Motivation
Edit.module's backport from Drupal 8 to Drupal 7 (see #2111667: Backport Drupal 8's Edit module to Drupal 7) has brought with it one huge, fundamental change: per-entity in-place editing, rather than page-wide. This is much better for usability, because it is abundantly clear at all times what you're editing. It also avoids the "an overwhelming sea of in-place editable things I can click on" problem. Per-entity in-place editing is triggered using a "Quick edit" contextual link.
A consequence though, exists for in-place editing of table/grid/… Views — i.e. fields that render individual fields (and hence use Views' render pipeline) rather than entire entities in a certain view mode (which uses the Entity/Field render pipeline, and hence of course already works just fine, even without this module).
That consequence is: there is no obvious way to start in-place editing of a given entity! Table or grid Views don't use contextual links for individual entities (there's only a contextual link for the entire View). But even if we'd have a contextual link for each entity in the View, then we still face significant problems:
- A given entity may consist of only a title. Then where do you display the contextual link for it?
- A given row in a table/grid/… View may contain fields of multiple entities (using Views' Relationships functionality)! So even a "Quick edit the entity in this row" solution is insufficient
- Many more things: #1962606-17: Quick Edit + "Field" Views (table, grid …).
- …
Proposed resolution
To be determined.
Remaining tasks
To be determined.
User interface changes
To be determined.
API changes
To be determined.
Comments
Comment #1
bgronek CreditAttribution: bgronek commentedI have to say that I was using the edit module using Views prior to it splitting out and I like the way it was. I found it very intuitive and simple to use and was quite disappointed to see it split out. In fact, I would say that the utility of the entire module has suffered substantially and to the point that I have since reverted to the old version until Views editing is re-implemented in a user friendly way again.
I saw the whole point of Edit as making it easy to edit content in Views on a complex layout page and I thought it did it quite well.
Comment #2
Wim Leers#1: it worked well for your use case, probably, but it was far too easy to break. A significant amount of real-world Views inherently did not work. So, it's great that it worked well for you, but it would've been impossible for us to *support* that, precisely because it'd be too easy to break!