Releases: johnbillion/wp-crontrol
Releases · johnbillion/wp-crontrol
1.14.0
- Reverts the changes introduced in version 1.13 while I look into the problem with the deployment process for wordpress.org
1.13.2
- Fixes another issue with missing files in the release
1.13.1
- Fixes an issue with missing files in the 1.13.0 release
1.13.0
- Introduces the ability to pause and resume cron events from the event listing screen; see the FAQ for full details
- Implements an autoloader to reduce memory usage
- Bumps the minimum supported version of PHP to 5.6
1.12.1
- Corrects an issue where an invalid hook callback isn't always identified
- Various code quality improvements
1.12.0
- Fix the PHP cron event management.
- More "namespacing" of query variables to avoid conflicts with other cron management plugins.
1.11.0
- Introduced an
Export
feature to the event listing screen for exporting the list of events as a CSV file. - Added the timezone offset to the date displayed for events that are due to run after the next DST change, for extra clarity.
- Introduced the
crontrol/filter-types
andcrontrol/filtered-events
filters for adjusting the available event filters on the event listing screen. - Lots of code quality improvements (thanks, PHPStan!).
1.10.0
- Support for more granular cron-related error messages in WordPress 5.7
- Several accessibility improvements
- Warning for events that are attached to a schedule that is too frequent
- More clarity around events and schedules that are built in to WordPress core
- Add a Help tab with links to the wiki and FAQs
1.9.1
- Fix the adding of new cron events when
DISALLOW_FILE_EDIT
is true.
1.9.0
- Add filters and sorting to the event listing screen. Props @yuriipavlov.
- Replace the "Add New" tabs with a more standard "Add New" button on the cron event listing page.
- Switch back to using browser-native controls for the date and time inputs.
- Add an error message when trying to edit a non-existent event.
- Introduce an informational message which appears when there are events that have missed their schedule.
- Fire actions when cron events and schedules are added, updated, and deleted.