Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.On a fresh Acquia BLT install, create a new content type.
Create a new page of this content type.
Go to content/admin. The page doesn't show.
Uninstall lightning_workflow, the page appears in the list.
This is a relatively new issue as it was working fine on acquia/lightning 2.0.1
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 2858566-9.patch | 10.06 KB | balsama |
Comments
Comment #2
extravioar CreditAttribution: extravioar commentedAnd when I try to reinstall lightning_workflow, I get:
Unable to install Lightning Workflow, core.entity_form_display.scheduled_update.multiple_node_embargo.default, core.entity_form_display.scheduled_update.node_embargo.default, field.field.scheduled_update.multiple_node_embargo.field_moderation_state_1, field.field.scheduled_update.node_embargo.field_moderation_state, field.storage.node.scheduled_update, field.storage.scheduled_update.field_moderation_state, field.storage.scheduled_update.field_moderation_state_1, scheduled_updates.scheduled_update_type.multiple_node_embargo, scheduled_updates.scheduled_update_type.node_embargo, views.view.moderation_history already exist in active configuration.
Comment #3
balsamaI think this is related to the "Has unpublished edits" field being a little too presumptuous. The quick fix is to remove that field and the latest revision relationship from the admin/content view (it's called "has forward revisions" in the backend).
Is moderation enabled for your new content type? I think the latest revision relationship is required. Enabling moderation or removing the required flag from the relationship might be less intrusive short-term solutions.
Comment #4
extravioar CreditAttribution: extravioar commentedThanks for the quick reply. Indeed, enabling moderation and re-saving the nodes solves the issue.
I had tried to remove the fields from the admin/content view but it didn't make a difference.
Comment #5
jacov CreditAttribution: jacov commentedconfirmed bug. we are seeing this behavior as well.
Comment #6
jacov CreditAttribution: jacov commentedComment #7
jacov CreditAttribution: jacov commented@johnkennedy fyi, raising priority, customer impacting.
Comment #8
balsamaThis is on our radar @jacov. No need to misuse the priority field :)
For now, there is a workaround in #3. We hope to have a permanent fix before 2.0.4 comes out (tomorrow or next Wednesday).
Comment #9
balsamaAvailable in PR 289: https://github.com/acquia/lightning/pull/289
Equivalent patch attached.
Comment #11
balsama