WP Crontrol

FAQ

Does this plugin work with PHP 8?

Yes, it’s actively tested and working up to PHP 8.2.

I get the error “There was a problem spawning a call to the WP-Cron system on your site”. How do I fix this?

You can read all about problems spawning WP-Cron on the WP Crontrol wiki.

Why do some cron events miss their schedule?

You can read all about cron events that miss their schedule on the WP Crontrol wiki.

Why do some cron events reappear shortly after I delete them?

If the event is added by a plugin then the plugin most likely rescheduled the event as soon as it saw that the event was missing. To get around this you can instead use the “Pause this hook” action which means it’ll remain in place but won’t perform any action when it runs.

Is it safe to delete cron events?

This depends entirely on the event. You can use your favourite search engine to search for the event name in order to find out which plugin it belongs to, and then decide whether or not to delete it.

If the event shows “None” as its action then it’s usually safe to delete. Please see the other FAQs for more information about events with no action.

Why can’t I delete some cron events?

The WordPress core software uses cron events for some of its functionality and removing these events is not possible because WordPress would immediately reschedule them if you did delete them. For this reason, WP Crontrol doesn’t let you delete these persistent events from WordPress core in the first place.

If you don’t want these events to run, you can use the “Pause this hook” action instead.

What happens when I pause an event?

Pausing an event will disable all actions attached to the event’s hook. The event itself will remain in place and will run according to its schedule, but all actions attached to its hook will be disabled. This renders the event inoperative but keeps it scheduled so as to remain fully compatible with events which would otherwise get automatically rescheduled when they’re missing.

As pausing an event actually pauses its hook, all events that use the same hook will be paused or resumed when pausing and resuming an event. This is much more useful and reliable than pausing individual events separately.

What happens when I resume an event?

Resuming an event re-enables all actions attached to the event’s hook. All events that use the same hook will be resumed.

What does it mean when “None” is shown for the Action of a cron event?

This means the cron event is scheduled to run at the specified time but there is no corresponding functionality that will be triggered when the event runs, therefore the event is useless.

This is often caused by plugins that don’t clean up their cron events when you deactivate them. You can use your favourite search engine to search for the event name in order to find out which plugin it belongs to, and then decide whether or not to delete it.

How do I change the next run time or the recurrence of a cron event?

You can change the time and recurrence of a cron event by clicking the “Edit” link next to the event.

How can I create a cron event that requests a URL?

From the Tools → Cron Events → Add New screen, create a PHP cron event that includes PHP that fetches the URL using the WordPress HTTP API. For example:

wp_remote_get( 'http://example.com' );

You can read all about the features and security of PHP cron events on the WP Crontrol wiki.

Why do changes that I make to some cron events not get saved?

You can read all about problems with editing cron events on the WP Crontrol wiki.

Can I export a list of cron events?

Yes, a CSV file of the event list can be exported and downloaded via the “Export” button on the cron event listing screen. This file can be opened in any spreadsheet application.

Can I see a historical log of all the cron events that ran on my site?

Not yet, but I hope to add this functionality soon.

Can I see a historical log of edits, additions, and deletions of cron events and schedules?

Yes. The excellent Simple History plugin has built-in support for logging actions performed via WP Crontrol.

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

No painel administrativo em Ferramentas → Eventos Cron, insira os detalhes do gancho. É melhor ter um hookname em conformidade com as convenções normais de nomenclatura de variáveis de PHP. O agendamento do evento significa quantas vezes o gancho será executado. Se você não encontrar um bom intervalo, então adicione um no painel administrativo em Configurações → Agendamentos Cron.

Passo 2: Escrevendo a função

Esta parte acontece no código PHP (por exemplo, no arquivo functions.php do seu tema). Para executar seu gancho, o WordPress dispara uma ação. Por esta razão, nós precisamos dizer ao WordPress qual função será executada quando essa ação for disparada. A linha a seguir realiza isso:

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?

No painel administrativo em Ferramentas → Eventos Cron, clique na aba “Adicionar evento do PHP Cron” abaixo da tabela de eventos Cron. No formulário que aparece, informe nas caixas o agendamento e o horário da próxima execução. O agendamento do evento significa quantas vezes o gancho será executado. Se você não encontrar um bom intervalo, então adicione um no painel administrativo em Configurações → Agendamentos Cron. Na área de “Código do gancho”, digite o código PHP que deve ser executado quando o evento cron for disparado. Você não precisa fornecer a tag de abertuda do PHP (<?php).

You can read all about the features and security of PHP cron events on the WP Crontrol wiki.

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 via the WordPress admin area (i.e. through the Plugin Editor or Theme Editor) then they also cannot add, edit, or delete a PHP cron event in WP Crontrol. 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 adding, editing, or deleting 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.

You can read all about the features and security of PHP cron events on the WP Crontrol wiki.

Há algum comando WP-CLI disponível?

The cron commands which were previously included in WP Crontrol are now part of WP-CLI itself. See wp help cron for more info.

What happens when I deactivate the WP Crontrol plugin?

You can read all about what happens when you deactivate the plugin on the WP Crontrol wiki.

Who took the photo in the plugin header image?

The photo was taken by Michael Pardo and is in the public domain.