694 add scheduler module #729
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #694
For the Scheduler module to function properly, the scheduler module's cron job needs to be set up correctly. Currently, Drupal's cron is set to run every 3 hours. We likely don't want to wait that long for the scheduler cron to run. We might want to set it to run every 30 minutes or even every minute.
I'm also not sure where we would set the cron job. Publishing and unpublishing entities won't work if the cron job isn't set regularly. The module wasn't functioning correctly when I tested it, so I also had to install the Scheduler Content Moderation Integration module.
Permissions are set as follows
Currently allowed entities to use the Scheduler module are Books, Builder page, Webforms, and News Items.
For the News content type, I have configured it so that once content is published, the creation time of the news item matches the scheduled publish date. I'm not sure if we want to keep this setting. I did this because we use the node creation time in a Twig file to display the time. This setting is turned off for all other content types. Additionally, I have enabled the creation of new revisions when an entity is published.
