class SchedulerUnpublishOnConstraintValidator in Scheduler 2.x

Validates the SchedulerUnpublishOn constraint.

Hierarchy

• class \Drupal\scheduler\Plugin\Validation\Constraint\SchedulerUnpublishOnConstraintValidator extends \Symfony\Component\Validator\ConstraintValidator

File

src/Plugin/Validation/Constraint/SchedulerUnpublishOnConstraintValidator.php, line 11

Namespace

Drupal\scheduler\Plugin\Validation\Constraint

class SchedulerUnpublishOnConstraintValidator extends ConstraintValidator {

  /**
   * {@inheritdoc}
   */
  public function validate($entity, Constraint $constraint) {

    // If the content type is not enabled for unpublishing then exit early.
    if (!\Drupal::service('scheduler.manager')
      ->getThirdPartySetting($entity
      ->getEntity(), 'unpublish_enable', FALSE)) {
      return;
    }
    $default_unpublish_required = \Drupal::config('scheduler.settings')
      ->get('default_unpublish_required');
    $scheduler_unpublish_required = \Drupal::service('scheduler.manager')
      ->getThirdPartySetting($entity
      ->getEntity(), 'unpublish_required', $default_unpublish_required);
    $publish_on = $entity
      ->getEntity()->publish_on->value;
    $unpublish_on = $entity->value;
    $status = $entity
      ->getEntity()->status->value;

    // When the 'required unpublishing' option is enabled the #required form
    // attribute cannot be set in every case. However a value must be entered if
    // also setting a publish-on date.
    if ($scheduler_unpublish_required && !empty($publish_on) && empty($unpublish_on)) {
      $this->context
        ->buildViolation($constraint->messageUnpublishOnRequiredIfPublishOnEntered)
        ->atPath('unpublish_on')
        ->addViolation();
    }

    // Similar to the above scenario, the unpublish-on date must be entered if
    // the content is being published directly.
    if ($scheduler_unpublish_required && $status && empty($unpublish_on)) {
      $this->context
        ->buildViolation($constraint->messageUnpublishOnRequiredIfPublishing)
        ->atPath('unpublish_on')
        ->addViolation();
    }

    // Check that the unpublish-on date is in the future. Unlike the publish-on
    // field, there is no option to use a past date, as this is not relevant for
    // unpublshing. The date must ALWAYS be in the future if it is entered.
    if ($unpublish_on && $unpublish_on < \Drupal::time()
      ->getRequestTime()) {
      $this->context
        ->buildViolation($constraint->messageUnpublishOnDateNotInFuture)
        ->atPath('unpublish_on')
        ->addViolation();
    }

    // If both dates are entered then the unpublish-on date must be later than
    // the publish-on date.
    if (!empty($publish_on) && !empty($unpublish_on) && $unpublish_on < $publish_on) {
      $this->context
        ->buildViolation($constraint->messageUnpublishOnTooEarly)
        ->atPath('unpublish_on')
        ->addViolation();
    }
  }

}

Members

Name	Modifiers	Type	Description	Overrides
SchedulerUnpublishOnConstraintValidator::validate	public	function