Problem/Motivation

When we install our install profile/distribution that adds a custom workflow, the "Editorial" workflow gets added and enabled along with the custom workflow.

When we add the editorial workflow configuration to our install profile (profile//config/install/workflow.workflow.editorial.yml) and set the status to false, nothing happens.

Proposed resolution

  • Prevent the editorial workflow getting added
  • Remove it if the status of the workflow configuration is false.

How to reproduce

The simplest way:

  1. add the attached workflows.workflow.uw_workflow.yml file to drupal/core/profiles/standards/config/install.
  2. modify drupal/core/profiles/standards/standards/info.yml and add content_moderation and workflow as dependencies.

Then browse to admin/config/workflow/workflows and you will see 2 workflows.

CommentFileSizeAuthor
#3 workflows.workflow.uw_workflow.yml1.4 KBistryker

Comments

iStryker created an issue. See original summary.

istryker’s picture

istryker commented
Title: Workflow shows up in Adminstration when status is false » Editoral Workflow shows up in Adminstration when status is false
istryker’s picture

istryker commented
Issue summary: View changes
StatusFileSize
new workflows.workflow.uw_workflow.yml1.4 KB
sam152’s picture

sam152 commented
Related issues: +#2872149: All configuration entities can be disabled but many don't actually define what, if anything, that that means

@amateescu helped me track down an issue I was looking for related to this. Adding it now.

I think it would be worth reviewing what happens to other config entities when they are disabled in this manner. Workflow entities already consider themselves disabled if they don't have any states, I'm not sure how we use that information elsewhere in workflows.

sam152’s picture

sam152 commented

@iStryker, it looks like this issue might solve the problem for your distribution: #2952307: Move workflow config into standard profile.

Do you think we can close this in favour of that?

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

sam152’s picture

sam152 commented
Status: Active » Closed (outdated)

I believe this should be addressed now.