Tried using this module with the workbench moderation module enabled and noticed when ever I edit an existing referenced entity even after saving new changes aren't reflected. Did some digging and discovered this is because the workbench moderation module creates the new saved content as a draft and there is no option from the inline entity edit form to change the moderation state. This would be a nice feature to have.


John Pitcairn’s picture

Category: feature » bug

>> active (no patch to review)

If Field Collection is anything to go by, support for Workbench Moderation could be difficult.

Ideally a new non-default revision of the referenced entity should be saved if the parent node entity is also saving a new non-published revision. The referenced entity's revision_id should be included, not just the entity id, so you see the difference between published and draft revisions when viewing the parent node.

This gets tricky because Workbench Moderation is a node module - it does not support Entity API's native is_default flag. Workbench Moderation also defers its processing until shutdown, and Field API has already saved the new field revision data as default (published) as a result.

See #1901892: Most recent Field Collection revision always appears in View when using Workbench Moderation and #1807460: Field collection doesn't play nice with workbench moderation (patch)

Kristen Pol’s picture

Issue summary: View changes

Updated issue summary.

John Pitcairn’s picture

Category: bug » feature
Status: Needs review » Active

And this would be a feature request, not a bug.

edutrul’s picture

Issue summary: View changes

I love this! and this needs to be in d8 as well!

edutrul’s picture

Version: 7.x-1.x-dev » 8.x-1.x-dev