A critical flaw in the Stacks module is that it does not support content workflows, so that every saved change to a stack widget is published immediately, which site maintainers have spent years battling with in Field Collection, EntityReference, Fieldable Panels Panes with Panelizer, etc, etc and is a huge oversight.

Comments

DamienMcKenna created an issue. See original summary.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

The similar module Bricks also failed to consider revisions in their architecture too so are in the same boat as Stacks: #2859679: Rewrite to use Entity Reference Revisions

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Title: Add support for revisions » Support entity workflows via revision tracking
dknisley’s picture

dknisley commented
Status: Active » Postponed

Thanks for bringing this up, including revisions is definitely an important piece that we'd like to include.

At the moment, Stacks is based on inline entity form which does not support revisions but they are working on a solution: https://www.drupal.org/node/2367235

Once that ongoing work gets added to that module's codebase we will be able to provide revisions support in Stacks.

rkeppner’s picture

rkeppner commented
Version: 8.x-1.x-dev » 3.x-dev

Following up on this, it seems that the inline_entity_form issue referenced above was resolved almost 5 years ago. Is this a feature that could possibly be addressed now? Our content workflow kind of hinges on being able to make revisions to an existing page and have them approved before publishing the new version, and I can't really see a way of accomplishing that without widget revisions.