- Issue created by @djdevin
- 🇺🇸United States DigantDj
We ran into the same issue after Drupal core & module update, this will definitely. It would be helpful to solve for even if not at the per-entity level, at least at the root level for someone who wants to keep the legacy behavior of publish by default.
- 🇸🇮Slovenia deaom
I'm not sure I understand the issue (or maybe it was solved in the meantime). When I go to clone a content block, there is the option of "Save cloned Content block as published", if that is checked the cloned block is published. The core is handling the publish/unpublish checkbox field (status is there, just not added to UI). If the checkbox is not checked when cloning, once the core issue will be merged, the status will be possible to update/change, until then, don't think this falls under this module as the status can be updated in code for the specific block (or block can be removed and cloned again with the publish option checked).