When a node is published via Scheduler and a moderation state is set, the published revision always has two transitions. One to draft, then one to published.
This patch fixes it by;
- Make it easier to extend with implementations of
scheduler_workbench_scheduler_api(); 1483c - Receive
$nodeby reference for implementations ofhook_scheduler_publish_api(); 3e843 - Use Workbench Moderation's
$nodeproperties to triggerworkbench_moderation_moderate()viahook_node_update()instead of calling it directly. This keeps the history cleaner because the moderation state is not reverted to draft when_scheduler_publish()callsnode_save()but before_scheduler_workbench_publish()can set the new correct moderation state; 3e843
Item number 2 depends on a patch for Scheduler; #1660192: Expand options for integrating modules
This patch extends #1660208: Code style and line endings.
| Comment | File | Size | Author |
|---|---|---|---|
| single_transition.patch | 1.9 KB | Bevan |
Comments
Comment #1
wwhurley commentedTested and accepted. See at [a4db285]
Comment #1.0
wwhurley commentedAdding the patch's dependency.
Comment #2
istryker commentedThis patch breaks code. See situation in #2395013: Setting up Scheduler module first, then enabling Scheduler_Workbench breaks.. Leaving this issue close and working on solution in #2395013