DE

↑ ↓ select, Enter open, Esc close

Delete a scheduled WP-Cron event

cautionWP-CLIalle

Caution: This command changes the system. Understand what it does before you run it.

Adjust the values, the command updates live
user@server
wp cron event delete old_plugin_daily_event --path=/var/www/vhosts/example.com/httpdocs

Deletes all scheduled occurrences of the given hook from the WordPress cron list. Useful when tasks of a removed plugin keep showing up or an event fails permanently. wp cron event list shows the hook name.

Note: If the related plugin is still active, it usually reschedules the event on the next request.

Also searched as

  • orphaned cron jobs in wordpress
  • remove wp cron event
  • delete cron task from old plugin

Related one-liners

All in WP-CLI

Delete all post revisions

$wp post list --post_type=revision --format=ids --path=/var/www/vhosts/example.com/httpdocs | xargs -r wp post delete --force --path=/var/www/vhosts/example.com/httpdocs
destructiveWP-CLI

List scheduled WP-Cron events

$wp cron event list --fields=hook,next_run_relative,recurrence --path=/var/www/vhosts/example.com/httpdocs
harmlessWP-CLI

Run due WP-Cron events immediately

$wp cron event run --due-now --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Back up the WordPress database as a gzip file

$wp db export - --path=/var/www/vhosts/example.com/httpdocs | gzip > /var/www/vhosts/example.com/db-backup.sql.gz
harmlessWP-CLI

Change domain: replace the old domain in the database

$wp db export /var/www/vhosts/example.com/before-domain-change.sql --path=/var/www/vhosts/example.com/httpdocs && wp search-replace '//old.example.com' '//example.com' --all-tables --skip-columns=guid --path=/var/www/vhosts/example.com/httpdocs
destructiveWP-CLI

Change the role of a WordPress user

$wp user set-role editorial editor --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.