Remove cron_file if WP system cron disabled #927
Merged
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.
If a
cron_file
has already been created but then a user setsmultisite.cron: false
, thesecron
tasks should not skip. Rather, they should run with the parameterstate: absent
in order to remove thecron_file
.Example scenario: User discovers that the default of cron enabled for multisite is a problem due to a large number of sites. This PR empowers the user to disable the cron via a
multisite.cron: false
addition towordpress_sites
, rather than having to SSH and manually disable the cron.Related discussion in #802