Integration with Content Scheduler to Check If the Node is Scheduled

Created on 16 January 2024, 10 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

  1. Create a node with scheduling using the Content Scheduler module and save the node
  2. 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

  • N/A

Data model changes

  • N/A

Release notes snippet

  • N/A
Feature request
Status

Active

Version

2.0

Component

Code

Created by

🇯🇴Jordan mahseri

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @mahseri
  • Status changed to Needs review 10 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

  • 🇦🇹Austria steponeloops

    Hi, I don't know if this is the right place or if I should open a new ticket.
    The patch makes the module work as it should (ie remember the selected queues also if not published) but I've got the following problem:

    Since the entity (article) is attached to the queue immediately on saving if an article is written and published in the same queue in the meantime on publishing the first (older) article (obviously) is on position 2 - but it should be on position 1 (think a newspaper: article 1 is scheduled for 10am, article 2 is written and published at 9am. On scheduled publishing at 10am article 1 should be on 1st position and should put article 2 on 2nd position).

    Now I understand that this cannot be achieved by entityqueue_form_widget as this module isn't called anymore when the scheduler runs - but has someone a idea how to achieve this? Thx in advance.

  • 🇯🇴Jordan Rajab Natshah Jordan

    Let us have a merge request to commit this nice new feature.

Production build 0.71.5 2024