gem-hunter
Language: PHP
Tests, runs, and deletes WP-Cron events; manages WP-Cron schedules.
Tests, runs, and deletes WP-Cron events; manages WP-Cron schedules.
Quick links: Using | Installing | Contributing | Support
This package implements the following commands:
Tests, runs, and deletes WP-Cron events; manages WP-Cron schedules.
wp cron
EXAMPLES
# Test WP Cron spawning system
$ wp cron test
Success: WP-Cron spawning is working as expected.
Tests the WP Cron spawning system and reports back its status.
wp cron test
This command tests the spawning system by performing the following steps:
DISABLE_WP_CRON constant is set; errors if true
because WP-Cron is disabled.ALTERNATE_WP_CRON constant is set; warns if true.EXAMPLES
# Cron test runs successfully.
$ wp cron test
Success: WP-Cron spawning is working as expected.
Schedules, runs, and deletes WP-Cron events.
wp cron event
EXAMPLES
# Schedule a new cron event
$ wp cron event schedule cron_test
Success: Scheduled event with hook 'cron_test' for 2016-05-31 10:19:16 GMT.
# Run all cron events due right now
$ wp cron event run --due-now
Executed the cron event 'cron_test_1' in 0.01s.
Executed the cron event 'cron_test_2' in 0.006s.
Success: Executed a total of 2 cron events.
# Delete all scheduled cron events for the given hook
$ wp cron event delete cron_test
Success: Deleted a total of 2 cron events.
# List scheduled cron events in JSON
$ wp cron event list --fields=hook,next_run --format=json
[{"hook":"wp_version_check","next_run":"2016-05-31 10:15:13"},{"hook":"wp_update_plugins","next_run":"2016-05-31 10:15:13"},{"hook":"wp_update_themes","next_run":"2016-05-31 10:15:14"}]
Deletes all scheduled cron events for the given hook.
wp cron event delete [<hook>...] [--due-now] [--exclude=<hooks>] [--all] [--match-args=<args>]
OPTIONS
[<hook>...]
One or more hooks to delete.
[--due-now]
Delete all hooks due right now.
[--exclude=<hooks>]
Comma-separated list of hooks to exclude.
[--all]
Delete all hooks.
[--match-args=<args>]
Only delete events whose arguments match the given JSON-encoded array or scalar value. Argument types must match exactly (for example, `["123"]` vs `[123]`). Requires exactly one hook name.
EXAMPLES
# Delete all scheduled cron events for the given hook
$ wp cron event delete cron_test
Success: Deleted a total of 2 cron events.
# Delete a specific cron event by hook and arguments
$ wp cron event delete cron_test --match-args='["123"]'
Success: Deleted a total of 1 cron event.
Lists scheduled cron events.
wp cron event list [--fields=<fields>] [--<field>=<value>] [--field=<field>] [--format=<format>]
OPTIONS
[--fields=<fields>]
Limit the output to specific object fields.
[--<field>=<value>]
Filter by one or more fields.
[--field=<field>]
Prints the value of a single field for each event.
[--format=<format>]
Render output in a particular format.
---
default: table
options:
- table
- csv
- ids
- json
- count
- yaml
---
AVAILABLE FIELDS
These fields will be displayed by default for each cron event:
These fields are optionally available:
EXAMPLES
# List scheduled cron events
$ wp cron event list
+-------------------+---------------------+---------------------+------------+
| hook | next_run_gmt | next_run_relative | recurrence |
+-------------------+---------------------+---------------------+------------+
| wp_version_check | 2016-05-31 22:15:13 | 11 hours 57 minutes | 12 hours |
| wp_update_plugins | 2016-05-31 22:15:13 | 11 hours 57 minutes | 12 hours |
| wp_update_themes | 2016-05-31 22:15:14 | 11 hours 57 minutes | 12 hours |
+-------------------+---------------------+---------------------+------------+
# List scheduled cron events in JSON
$ wp cron event list --fields=hook,next_run --format=json
[{"hook":"wp_version_check","next_run":"2016-05-31 10:15:13"},{"hook":"wp_update_plugins","next_run":"2016-05-31 10:15:13"},{"hook":"wp_update_themes","next_run":"2016-05-31 10:15:14"}]
Runs the next scheduled cron event for the given hook.
wp cron event run [<hook>...] [--due-now] [--exclude=<hooks>] [--all] [--network]
OPTIONS
[<hook>...]
One or more hooks to run.
[--due-now]
Run all hooks due right now. Respects the doing_cron transient to
prevent overlapping runs.
[--exclude=<hooks>]
Comma-separated list of hooks to exclude.
[--all]
Run all hooks.
[--network]
Run hooks across all sites in a multisite installation.
EXAMPLES
# Run all cron events due right now
$ wp cron event run --due-now
Executed the cron event 'cron_test_1' in 0.01s.
Executed the cron event 'cron_test_2' in 0.006s.
Success: Executed a total of 2 cron events.
# Run all cron events due right now across all sites in a multisite
$ wp cron event run --due-now --network
Executed the cron event 'cron_test_1' in 0.01s.
Executed the cron event 'cron_test_2' in 0.006s.
Success: Executed a total of 2 cron events across 3 sites.
Schedules a new cron event.
wp cron event schedule <hook> [<next-run>] [<recurrence>] [--<field>=<value>]
OPTIONS
<hook>
The hook name.
[<next-run>]
A Unix timestamp or an English textual datetime description compatible with `strtotime()`. Defaults to now.
[<recurrence>]
How often the event should recur. See `wp cron schedule list` for available schedule names. Defaults to no recurrence.
[--<field>=<value>]
Arguments to pass to the hook for the event. <field> should be a numeric key, not a string.
EXAMPLES
# Schedule a new cron event
$ wp cron event schedule cron_test
Success: Scheduled event with hook 'cron_test' for 2016-05-31 10:19:16 GMT.
# Schedule new cron event with hourly recurrence
$ wp cron event schedule cron_test now hourly
Success: Scheduled event with hook 'cron_test' for 2016-05-31 10:20:32 GMT.
# Schedule new cron event and pass arguments
$ wp cron event schedule cron_test '+1 hour' --0=first-argument --1=second-argument
Success: Scheduled event with hook 'cron_test' for 2016-05-31 11:21:35 GMT.
Gets WP-Cron schedules.
wp cron schedule
EXAMPLES
# List available cron schedules
$ wp cron schedule list
+------------+-------------+----------+
| name | display | interval |
+------------+-------------+----------+
| hourly | Once Hourly | 3600 |
| twicedaily | Twice Daily | 43200 |
| daily | Once Daily | 86400 |
+------------+-------------+----------+
List available cron schedules.
wp cron schedule list [--fields=<fields>] [--field=<field>] [--format=<format>]
OPTIONS
[--fields=<fields>]
Limit the output to specific object fields.
[--field=<field>]
Prints the value of a single field for each schedule.
[--format=<format>]
Render output in a particular format.
---
default: table
options:
- table
- csv
- ids
- json
- yaml
---
AVAILABLE FIELDS
These fields will be displayed by default for each cron schedule:
There are no additional fields.
EXAMPLES
# List available cron schedules
$ wp cron schedule list
+------------+-------------+----------+
| name | display | interval |
+------------+-------------+----------+
| hourly | Once Hourly | 3600 |
| twicedaily | Twice Daily | 43200 |
| daily | Once Daily | 86400 |
+------------+-------------+----------+
# List id of available cron schedule
$ wp cron schedule list --fields=name --format=ids
hourly twicedaily daily
Unschedules all cron events for a given hook.
wp cron event unschedule <hook>
OPTIONS
<hook>
Name of the hook for which all events should be unscheduled.
EXAMPLES
# Unschedule a cron event on given hook.
$ wp cron event unschedule cron_test
Success: Unscheduled 2 events for hook 'cron_test'.
This package is included with WP-CLI itself, no additional installation necessary.
To install the latest version of this package over what's included in WP-CLI, run:
wp package install git@github.com:wp-cli/cron-command.git
We appreciate you taking the initiative to contribute to this project.
Contributing isn’t limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation.
For a more thorough introduction, check out WP-CLI's guide to contributing. This package follows those policy and guidelines.
Think you’ve found a bug? We’d love for you to help us get it fixed.
Before you create a new issue, you should search existing issues to see if there’s an existing resolution to it, or if it’s already been fixed in a newer version.
Once you’ve done a bit of searching and discovered there isn’t an open or fixed issue for your bug, please create a new issue. Include as much detail as you can, and clear steps to reproduce if possible. For more guidance, review our bug report documentation.
Want to contribute a new feature? Please first open a new issue to discuss whether the feature is a good fit for the project.
Once you've decided to commit the time to seeing your pull request through, please follow our guidelines for creating a pull request to make sure it's a pleasant experience. See "Setting up" for details specific to working on this package locally.
This project is licensed under the MIT License. See the LICENSE file for details.
GitHub issues aren't for general support questions. For support resources and next steps, see the WP-CLI Support page: https://make.wordpress.org/cli/handbook/support/
This README.md is generated dynamically from the project's codebase using wp scaffold package-readme (doc). To suggest changes, please submit a pull request against the corresponding part of the codebase.