Broadcasts: Don't display next import date/time when event running #586
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
When the scheduled event to import ConvertKit Broadcasts to WordPress Posts is running, the timestamp for the next scheduled event is
1
, resulting in incorrect output on the description:This PR resolves by not outputting the next scheduled date/time when the event is running:
When the event is not running, the next scheduled date/time displays in the description.
Testing
BroadcastsToPostsCest:testBroadcastsManualImportWhenEnabled
: Test that the description does not display when using the manual import functionality.Checklist