The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.To get a 1.0 stable release of Edit out the door, a scope has been determined:
- support for in-place editing nodes
- support for using Edit in combination with Panels pages to do page layouts
Otherwise, Edit would probably be in a perpetual beta, in order to test against all entity types in Drupal 7. Drupal 7's Entity API was a contrib afterthought, not part of Drupal core, hence there are lots of subtle problems — Edit has helped consolidate Entity API in Drupal 8.
Thank you for your understanding.
Comments
Comment #1
wim leersThis is at least major.
Comment #2
wim leers#2168909: Don't set attributes on fields of unsupported entity types prevents Edit from breaking things for sites that use other entity types than just Node.
We have #2159211: Add support for user profiles to add support for in-place editing user profiles and #2084199: Add support for Drupal Commerce entity types for Drupal Commerce entities. That doesn't mean we plan to implement those first in the future, or only, it just means that we only have issues for those entity types for now.
Finally, #1889798: Panelizer support (use Panels' render pipeline to re-render edited field panes in Panels) and #2105843: Add support for Display suite are related to the second bullet in the issue summary: Edit 1.0 will only support Panels pages, they're about supporting Panel nodes and Display Suite.
Comment #3
damienmckennaGiven that 1.0 is out the door, lets reopen this.
Comment #4
damienmckennaHow about adding a value to the entity / bundle definition via hook_entity_info() and hook_entity_info_alter() for entities that are supported?
Comment #5
wim leers#4: that could indeed help significantly. Would you like to provide a patch? :)
Comment #6
wim leersComment #7
anton-staroverov commented+1 must-have feature
Comment #8
mpotter commentedWondering what the status is on this, especially regarding working with panels pages. Not sure if Panelizer is part of this, but I noticed what when I panelize a page and move the body field over to the sidebar, when I try to quickedit the body field in the panel pane I get the following problems:
1) Editing the text in the inline wysiwyg does not cause the "Save" button to show up in the quickedit ribbon.
2) If I click the X button for quickedit, it seems to notice that a change has been made but clicking Save doesn't actually save the next text.
I'd be interested in using QuickEdit in Open Atrium if it could play nicer with Panels.
Once nice thing I noticed was it *does* work well with editing paragraph fields. I got a new page containing the field instead of a popup but that might be a different config problem. But I was able to change a paragraph field that was in a panel pane and save it. So maybe it's just WYSIWYG related?
Comment #9
vladimirausThank you for your contributions. 🎂
Drupal 7 is no longer supported. 🚀
Marking as outdated.