WP Crontrol


WP Crontrol permite visualizar e controlar o que está acontecendo no sistema WP-Cron. A partir das telas administrativas você pode:

  • Veja todos os eventos Cron juntamente com seus argumentos, recorrência, funções de callback e quando será sua próxima execução.
  • Editar, excluir e executar imediatamente qualquer evento Cron.
  • Adicionar novos eventos Cron.
  • Bulk delete cron events.
  • Adicione, edite e remova agendamentos Cron personalizados.

A tela administrativa mostrará uma mensagem de aviso se o seu sistema Cron não estiver funcionando corretamente (por exemplo, se o seu servidor não puder se conectar a si mesmo para disparar eventos Cron agendados).


  1. Go to the Tools → Cron Events menu to manage cron events.
  2. Go to the Settings → Cron Schedules menu to manage cron schedules.

Imagens de tela

  • New cron events can be added, modified, deleted, and executed

  • New cron schedules can be added, giving plugin developers more options when scheduling events


Qual a utilidade de adicionar novos agendamentos Cron?

Os agendamentos Cron são usados por plugins WordPress para o agendamento de eventos para que sejam executados em intervalos regulares. Os intervalos devem ser fornecidos pelo próprio WordPress ou um plugin para que seja usado. Por exemplo, muitos plugins de backup oferecem suporte a backups periódicos. Para fazer um backup semanal, primeiramente um agendamento de Cron semanal deve ser inserido no WP Crontrol, e então um plugin de backup pode aproveitar isto como um intervalo.

How do I create a new cron event?

Existem duas etapas para obter um evento Cron funcional executado regularmente. O primeiro passo é informar o WordPress sobre o gancho. Esta é a parte para a qual o WP Crontrol foi criado. O segundo passo é chamar uma função quando o seu gancho for executado.

Passo 1: Adicionando o gancho

In the Tools → Cron Events admin panel, click on the “Add Cron Event” tab and enter the details of the hook. You’re best off having a hookname that conforms to normal PHP variable naming conventions. The event schedule is how often your hook will be executed. If you don’t see a good interval, then add one in the Settings → Cron Schedules admin panel.

Passo 2: Escrevendo a função

This part takes place in PHP code (for example, in the functions.php file from your theme). To execute your hook, WordPress runs an action. For this reason, we need to tell WordPress which function to execute when this action is run. The following line accomplishes that:

add_action( 'my_hookname', 'my_function' );

O próximo passo é escrever sua função. Veja aqui um exemplo simples:

function my_function() {
    wp_mail( 'hello@example.com', 'WP Crontrol', 'WP Crontrol rocks!' );

Como eu crio um novo evento do PHP Cron?

In the Tools → Cron Events admin panel, click on the “Add PHP Cron Event” tab. In the form that appears, enter the schedule and next run time in the boxes. The event schedule is how often your event will be executed. If you don’t see a good interval, then add one in the Settings → Cron Schedules admin panel. In the “Hook code” area, enter the PHP code that should be run when your cron event is executed. You don’t need to provide the PHP opening tag (<?php).

Which users can manage cron events and schedules?

Only users with the manage_options capability can manage cron events and schedules. By default, only Administrators have this capability.

Which users can manage PHP cron events? Is this dangerous?

Only users with the edit_files capability can manage PHP cron events. This means if a user cannot edit files on the site (eg. through the Plugin Editor or Theme Editor) then they cannot edit or add a PHP cron event. By default, only Administrators have this capability, and with Multisite enabled only Super Admins have this capability.

If file editing has been disabled via the DISALLOW_FILE_MODS or DISALLOW_FILE_EDIT configuration constants then no user will have the edit_files capability, which means editing or adding a PHP cron event will not be permitted.

Therefore, the user access level required to execute arbitrary PHP code does not change with WP Crontrol activated.

Há algum comando WP-CLI disponível?

Os comandos Cron que foram incluídos anteriormente no WP Crontrol agora fazem parte do WP-CLI (desde a versão 0.16), portanto esse plugin não fornece mais comandos WP-CLI. Veja wp help cron para obter mais informações.


19 de maio de 2020
This is a very handy tool to control your WordPress Cron Jobs. New interface in version 1.8.3 is great. A big thank you to the development team.
9 de maio de 2020
Perfect Plugin, does exactly what it should do and nothing more. This is what i like! You should use it only if you know what you are doing 😉
11 de dezembro de 2019
Great and simple plugin, practically a must for managing/adding cron events to WP.
Leia todas as 94 avaliações

Contribuidores e desenvolvedores

“WP Crontrol” é um software com código aberto. As seguintes pessoas contribuíram para este plugin.


“WP Crontrol” foi traduzido para 11 localizações. Agradecemos aos tradutores por suas contribuições.

Traduzir “WP Crontrol” para o seu idioma.

Interessado no desenvolvimento?

Navegue pelo código, dê uma olhada no repositório SVN ou assine o registro de desenvolvimento via RSS.

Registro de alterações


  • Fix an issue with the tabs in 1.8.4.


  • Add a warning message if the default timezone has been changed. More information.
  • Fixed string being passed to strtotime() function when the Now option is chosen when adding or editing an event.


  • Fix the editing of events that aren’t currently listed on the first page of results.


  • Bypass the duplicate event check when manually running an event. This allows an event to manually run even if it’s due within ten minutes or if it’s overdue.
  • Force only one event to fire when manually running a cron event.
  • Introduce polling of the events list in order to show a warning when the event listing screen is out of date.
  • Add a warning for cron schedules which are shorter than WP_CRON_LOCK_TIMEOUT.
  • Add the Site Health check event to the list of persistent core hooks.


  • Fix the bottom bulk action menu on the event listing screen.
  • Make the timezone more prominent when adding or editing a cron event.


  • Searching and pagination for cron events
  • Ability to delete all cron events with a given hook
  • More accurate response messages when managing events (in WordPress 5.1+)
  • Visual warnings for events without actions, and PHP events with syntax errors
  • Timezone-related clarifications and fixes
  • A more unified UI
  • Modernised codebase


  • Correct the PHP.net URL for the strtotime() reference.


  • Remove the date and time inputs and replace with a couple of preset options and a plain text field. Fixes #24 .
  • Ensure the schedule name is always correct when multiple schedules exist with the same interval. Add error handling. Fixes #25.
  • Re-introduce the display of the current site time.
  • Use a more appropriate HTTP response code for unauthorised request errors.


  • Remove the ability to delete a PHP cron event if the user cannot edit files.
  • Remove the Edit link for PHP cron events when the user cannot edit the event.
  • Avoid a PHP notice due to an undefined variable when adding a new cron event.


  • Fix a potential fatal error on the cron events listing screen.


  • Introduce bulk deletion of cron events. Yay!
  • Show the schedule name instead of the schedule interval next to each event.
  • Add core’s new delete_expired_transients event to the list of core events.
  • Don’t allow custom cron schedules to be deleted if they’re in use.
  • Add links between the Events and Schedules admin screens.
  • Add syntax highlighting to the PHP code editor for a PHP cron event.
  • Styling fixes for events with many arguments or long arguments.
  • Improvements to help text.
  • Remove usage of create_function().
  • Fix some translator comments, improve i18n, improve coding standards.


  • Show the hooked actions for each cron event.
  • Don’t show the Delete link for core’s built-in cron events, as they get re-populated immediately.
  • Correct the success message after adding or editing PHP cron events.
  • Correct the translations directory name.


  • Switch to requiring cron event times to be input using the site’s local timezone instead of UTC.
  • Add the ability for a PHP cron event to be given an optional display name.
  • Better UX for users who cannot edit files and therefore cannot add or edit PHP cron events.
  • Terminology and i18n improvements.


  • Display a less scary looking message when DISABLE_WP_CRON is defined.
  • Correct the example code for cron event arguments.


  • Improvements to the UI.
  • More error detection when testing WP-Cron functionality.
  • Improve the capability checks for single site and multisite.
  • Lots of escaping and sanitising.
  • Fix various issues with multiple events with the same hook name.
  • Removed the WP-CLI commands, as these have now been added to WP-CLI core (see wp help cron for more info)


  • Tweaks to i18n and date and args formatting
  • Properly escape the crontrol_message query var (props Julio Potier)


  • Added wp crontrol run-event and wp crontrol delete-event WP-CLI commands
  • Clarify language regarding hooks/entries/events


  • Correctly display the local time when listing cron events
  • Remove a PHP notice
  • Pass the WP-Cron spawn check through the same filter as the actual spawner


  • Added support for WP-CLI
  • Removed some PHP4 code that’s no longer relevant


  • Bug fixes for running cron events and adding cron schedules
  • Added a cron spawn test to check for errors when spawning cron
  • Various small tweaks
  • WordPress 3.4 compatibility


  • Input of PHP code for cron events
  • Non-repeating cron events
  • Handles cron events with arguments


  • Internationalization
  • Editing/deleting/execution of cron events
  • More text, status messages, etc.
  • Allow a user to enter a schedule event in a human manner
  • Looks better on WordPress 2.5


  • Fully documented the code.
  • Fixed the bug that the activate action wouldn’t be run if the plugin wasn’t in a subdirectory.
  • Now will play nicely in case any other plugins specify additional cron schedules.
  • Minor cosmetic fixes.


  • Super basic, look at what’s in WP-Cron functionality.