Able to schedule a node in past

Created on 16 January 2025, 5 months ago

Problem/Motivation

If you change the label of the title field for a content type, then validation to restrict publishing in past date does not work.

Steps to reproduce

  1. Create a new content type.
  2. In the "Title field label" field, change Title to something else.
  3. Enable the scheduled publishing.
  4. Chose any sub-setting of "Action to be taken for publication dates in the past"
  5. Save content type.
  6. Scheduled publish a node and chose a past date
  7. Based on what action has been set for "Action to be taken for publication dates in the past", the expected behavior doesn't happen
🐛 Bug report
Status

Active

Version

2.2

Component

Code

Created by

🇮🇳India er.garg.karan Chandigarh

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

Merge Requests

Comments & Activities

  • Issue created by @er.garg.karan
  • Merge request !222Update scheduler.module. → (Open) created by er.garg.karan
  • Pipeline finished with Failed
    5 months ago
    Total: 6671s
    #397883
  • 🇬🇧United Kingdom jonathan1055

    Hi garg.karan, thanks for creating the MR. I need to replicate the problem first, then can review your solution. Is it possible that you could add test coverage for this, to demonstrate the problem and prove the fix. We have the 'test only changes' job in the pipeline which works very nicely to run updated tests on the original unchanged code.

  • Status changed to Needs review 12 days ago
  • 🇮🇳India karavkars@gmail.com

    Hi garg.karan, thanks for creating the MR. this works well with version:2.2.1.
    Adding a patch file using your MR here for use.

  • 🇬🇧United Kingdom jonathan1055

    I have tried, but not been able to replicate this problem, using Core 11.1 and Scheduler 2.2.1.

    To be honest, I do not see any way that the label of the title field could affect the validation constraints anyway, but I am willing to try it, and be proved wrong. But until I can replicate the problem and ensure that it is a Scheduler bug it won't get much further. Maybe there is some unintended interaction with another module which is removing your validation constraints?

Production build 0.71.5 2024