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 entityqueue_form_widget-2.0.8

API changes

  • N/A

Data model changes

  • N/A

Release notes snippet

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

mahseri created an issue. See original summary.

mahseri’s picture

mahseri’s picture

Status: Active » Needs review
rajab natshah’s picture

Title: Integration with Content Scheduler to Check If the Node is Scheduled » Add an integration with Content Scheduler to Check If the Node is Scheduled
rajab natshah’s picture

rajab natshah’s picture

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

steponeloops’s picture

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.

rajab natshah’s picture

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

rajab natshah’s picture

Status: Needs review » Needs work

Needs an MR

mrinalini9 made their first commit to this issue’s fork.

mrinalini9’s picture

Status: Needs work » Needs review
rajab natshah’s picture

Issue summary: View changes
Issue tags: +entityqueue_form_widget-2.0.8

rajab natshah’s picture

Assigned: Unassigned » mohammed j. razem
rajab natshah’s picture

Assigned: mohammed j. razem » Unassigned
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

rajab natshah’s picture

Issue summary: View changes
rajab natshah’s picture

Issue summary: View changes

Status: Fixed » Closed (fixed)

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