Currently, you have to save a node to get access to the SCHEDULED PUBLICATION field. There's no reason why this should be happening in the first place and this is seriously impacting the UX. At a minimum this should be documented. See #2935093: Add documentation for the Lightning Scheduler module.

The ideal flow would be: select the publication date before creating the node and update it if required when editing the node.

It'd be easy to fall into the following trap: select the publication date on the workflow page (/node/NID) because it's directly related to the workflow status and we want to keep the node creation form as simple as possible. But if doing this, we would run into an issue if we'd decide to publish directly from the node creation form since this would bypass the second screen (workflow status at /node/NID) entirely.

Comments

anavarre created an issue. See original summary.

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
CreditAttribution: phenaproxima at Acquia commented
Project: Lightning » Lightning Workflow
Version: 8.x-3.x-dev » 8.x-1.x-dev
Component: Workflow » User interface
balsama’s picture

balsama
he/him
Primary language English
Location boston
CreditAttribution: balsama at Acquia commented
Version: 8.x-1.x-dev » 8.x-2.x-dev
Status: Active » Needs review

This feature is now available in the 2.x branch of Lightning Workflow. To test:

If you are using the Lightning Profile:

composer require drupal/lightning_workflow:"2.0.0-alpha1 as 1.1.0" --no-update
composer update drupal/lightning_workflow --with-dependencies
drush update:db

If you are using Lightning Workflow as a standalone module:

composer require drupal/lightning_workflow:^2.0 --no-update
composer update drupal/lightning_workflow --with-dependencies

Lightning Workflow 2.0 will automatically migrate your existing scheduled transitions in a database update.

balsama’s picture

balsama
he/him
Primary language English
Location boston
CreditAttribution: balsama at Acquia commented
Issue tags: +Release blocker
sam.spinoy@gmail.com’s picture

sam.spinoy@gmail.com CreditAttribution: sam.spinoy@gmail.com at Adapt commented

I have installed lightning 3.1.1. Composer gives me this warning: acquia/lightning 3.1.1 requires drupal/lightning_workflow ^1.2 -> satisfiable by drupal/lightning_workflow[1.x-dev, 1.2.0] but these conflict with your requirements or minimum-stability.
So the suggested fix does not work for me. Is there a patch I can apply instead?

mikemadison’s picture

mikemadison CreditAttribution: mikemadison at Acquia commented

I worked around ^^ by requiring

"drupal/lightning_workflow": "2.x-dev as 1.2.0"

and

"drupal/core": "8.5.x-dev",

mikemadison’s picture

mikemadison CreditAttribution: mikemadison at Acquia commented
Status: Needs review » Reviewed & tested by the community

confirming that the new fields are present on node creation with the most current dev!

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
CreditAttribution: phenaproxima at Acquia commented
Status: Reviewed & tested by the community » Fixed

This is merged in Lightning Workflow 8.x-2.x, so I'm marking this fixed.

  • phenaproxima authored 445c5dc on 8.x-2.x 
    Add a Drush command for running the Scheduler migration (#26)

Lightning...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.