Add an integration with Content Scheduler to Check If the Node is Scheduled

Created on 16 January 2024, 5 months ago

Updated 17 March 2024, 3 months ago

Problem/Motivation

Saving the node as Unpublished or in Draft status while it is scheduled will result in the removal of all previously selected values. Consequently, users will need to edit the node again after it is published and reselect the desired values.

Steps to reproduce

Create a node with scheduling using the Content Scheduler module and save the node
Since the node is unpublished, all selected values will be removed

Proposed resolution

To check if the node is scheduled.

Remaining tasks

✅ File an issue
➖ Addition/Change/Update/Fix
➖ Testing to ensure no regression
➖ Automated unit testing coverage
➖ Automated functional testing coverage
➖ UX/UI designer responsibilities
➖ Readability
➖ Accessibility
➖ Performance
➖ Security
➖ Documentation
➖ Code review by maintainers
➖ Full testing and approval
➖ Credit contributors
➖ Review with the product owner
➖ Release notes snippet
❌ Release

API changes

Data model changes

Release notes snippet

✨ Feature request

Status

Needs review

Version

2.0

Component

Code

Created by

🇯🇴Jordan mahseri

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @mahseri
Comment 5 months ago →
🇯🇴Jordan mahseri
Status changed to Needs review 5 months ago2:53pm 16 January 2024
Comment 5 months ago →
🇯🇴Jordan mahseri
Comment 5 months ago →
🇯🇴Jordan Rajab Natshah Jordan
Comment 4 months ago →
🇯🇴Jordan Rajab Natshah Jordan
Comment 3 months ago →
🇯🇴Jordan Rajab Natshah Jordan
Thanks, Hamza, for reporting and patching.

Please, open a new merge request.
Drupal.org is not showing a way to commit with --author any more
They moved that to the Gitlab server https://git.drupalcode.org

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024