Broadcasts: DISABLE_WP_CRON
notice
#725
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.
Summary
Adds a notice in the Broadcasts settings of the Plugin if the
DISABLE_WP_CRON
constant is detected. This was the reason for this issue, where broadcasts were not importing for the creator.The WordPress Cron system is essential for importing broadcasts. Normally, it's triggered by site activity, such as visitors or user logins. However, some web hosts disable this default behavior by specifying the
DISABLE_WP_CRON
constant, opting instead to trigger it via crontab or similar methods (see more: https://help.dreamhost.com/hc/en-us/articles/360048323291-Disabling-WP-CRON-to-Improve-Overall-Site-Performance).The notice prompts creators to either ensure that their host is handling WordPress Cron manually or to remove the
DISABLE_WP_CRON
constant if Cron is not being triggered.Testing
Existing tests pass.
Checklist