WP Crontrol

Beschrijving

WP Crontrol enables you to take control of the cron events on your WordPress website. From the admin screens you can:

  • View all cron events along with their arguments, recurrence, callback functions, and when they are next due.
  • Edit, delete, pause, resume, and immediately run cron events.
  • Nieuwe cron events toevoegen.
  • Bulk verwijderen van cron gebeurtenissen.
  • Aangepaste cronschema’s toevoegen en verwijderen.
  • Export and download cron event lists as a CSV file.

WP Crontrol is aware of timezones, will alert you to events that have no actions or that have missed their schedule, and will show you a helpful warning message if it detects any problems with your cron system.

Gebruik

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

Andere plugins

Ik onderhoud verschillende andere plugins voor ontwikkelaars. Bekijk ze eens:

Privacyverklaring

WP Crontrol is private by default and always will be. It does not send data to any third party, nor does it include any third party resources. WP Crontrol’s full privacy statement can be found here.

Toegankelijkheidsverklaring

WP Crontrol aims to be fully accessible to all of its users. WP Crontrol’s full accessibility statement can be found here.

Schermafbeeldingen

  • Crongebeurtenissen kunnen worden gewijzigd, verwijderd en uitgevoerd

  • New cron events can be added

  • Er kunnen nieuwe cron schema's worden toegevoegd, waardoor ontwikkelaars van plugins meer opties krijgen bij het plannen van evenementen

FAQ

Werkt deze plugin met PHP 8?

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

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 website.

Waarom missen sommige cron events hun schema?

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

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 het veilig om cron events te verwijderen?

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.

Waarom kan ik sommige cron gebeurtenissen niet verwijderen?

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 website.

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 website.

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.

What’s the use of adding new cron schedules?

Cron schedules are used by WordPress and plugins for scheduling events to be executed at regular intervals. Intervals must be provided by the WordPress core or a plugin in order to be used. As an example, many backup plugins provide support for periodic backups. In order to do a weekly backup, a weekly cron schedule must be entered into WP Crontrol first and then a backup plugin can take advantage of it as an interval.

Hoe maak ik een nieuw cron event aan?

There are two steps to getting a functioning cron event that executes regularly. The first step is telling WordPress about the hook. This is the part that WP Crontrol was created to provide. The second step is calling a function when your hook is executed.

Stap één: de hook toevoegen

In the Tools → Cron Events admin panel, click on “Add New” and enter the details of the hook. You’re best off using a hook name 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.

Stap twee: schrijven van de functie

Dit deel vindt plaats in PHP code (bijvoorbeeld in het functions.php bestand van je thema). Om je hook uit te voeren, voert WordPress een actie uit. Daarom moeten we WordPress vertellen welke functie moet worden uitgevoerd wanneer deze actie wordt uitgevoerd. De volgende regel zorgt daarvoor:

add_action( 'my_hookname', 'my_function' );

De volgende stap is het schrijven van je functie. Hier is een eenvoudig voorbeeld:

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

Hoe maak ik een nieuw PHP cron event aan?

In the Tools → Cron Events admin panel, click on “Add New”. In the form that appears, select “PHP Cron Event” and enter the schedule and next run time. 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 “PHP 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).

Creating, editing, and running PHP cron events is subject to restrictive security permissions. You can read all about the features and security of PHP cron events on the WP Crontrol website.

Welke gebruikers kunnen cron-evenementen en -schema’s beheren?

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

Welke gebruikers kunnen PHP cron events beheren? Is dit gevaarlijk?

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 website.

Zijn er WP-CLI opdrachten beschikbaar?

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 website.

How can I report a security bug?

You can report security bugs through the Patchstack Vulnerability Disclosure Program. The Patchstack team helps validate, triage, and handle any security vulnerabilities. Report a security vulnerability here.

Wie heeft de foto in de headerafbeelding van de plugin gemaakt?

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

Beoordelingen

9 maart 2024
Use this tool to run my own php script to maintain my uploaded webcam images. Thanks a lot for this plugin.
9 maart 2024
Why people are heartless and rate something so good and yet free be given poor rating? These guys have no respect for the opensource and the people who dedicate their time for the great cause. I love your plugin and i can't say enough that its worth 5 stars rating and nothing less. This is the 4th review that i am writing for plugins which are great but some idiots give them poor rating. God bless you guys for sparing your valuable time for those who believe in the Open-source and its spirit of unity from across the world breaking all the barriers. Cheers.
20 november 2023
Thank you a lot, helped me understanding how WP-Cron works. Thanks! 😄
6 november 2023
One of the best plugin to manage and keep track of crons. been using it for years. Thank you!
Lees alle 149 beoordelingen

Bijdragers & ontwikkelaars

“WP Crontrol” is open source software. De volgende personen hebben bijgedragen aan deze plugin.

Bijdragers

“WP Crontrol” is vertaald in 18 talen. Dank voor de vertalers voor hun bijdragen.

Vertaal “WP Crontrol” naar jouw taal.

Interesse in ontwikkeling?

Bekijk de code, haal de SVN repository op, of abonneer je op het ontwikkellog via RSS.

Changelog

1.16.3

  • Corrects the displayed PHP cron event name if one is provided

1.16.2

1.16.1

  • Confirms support for WordPress 6.4

1.16.0

  • Allow persistent WordPress core hooks to be cleared if there’s more than one event with that hook
  • Add the number of matching events to the hook deletion link text
  • Scrap the Ajax request that checks if the current page of cron events has changed since loading
  • Make some improvements to sorting the cron event list table columns
  • Verhoog de minimaal ondersteunde PHP versie naar 7.4

1.15.3

  • Pass the $doing_wp_cron value to the cron_request filter so it matches WordPress core
  • Diverse verbeteringen van de codekwaliteit

1.15.2

  • Improves the terminology around pausing and deleting hooks and events
  • Improves accessibility of the event listing table for keyboard users
  • Removes an unnecessary SQL query when fetching the list of paused events
  • Adds an FAQ about deactivating the plugin

1.15.1

  • Bevestigt dat de plugin compatibel is met PHP 8.2
  • Increases compatibility with other plugins that include very old Composer autoloader implementations

1.15.0

  • Introduceert de mogelijkheid om cron evenementen te pauzeren en te hervatten vanuit het evenementenscherm; zie de FAQ voor volledige details
  • Adds the site time to the cron event editing screen
  • Implementeert een autoloader om geheugengebruik te verminderen
  • Verhoogt de minimaal ondersteunde versie van PHP naar 5.6

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

  • Herstelt een probleem met ontbrekende bestanden in versie 1.13.0

1.13.0

  • Introduceert de mogelijkheid om cron evenementen te pauzeren en te hervatten vanuit het evenementenscherm; zie de FAQ voor volledige details
  • Implementeert een autoloader om geheugengebruik te verminderen
  • Verhoogt de minimaal ondersteunde versie van PHP naar 5.6

1.12.1

  • Corrects an issue where an invalid hook callback isn’t always identified
  • Various code quality improvements

1.12.0

  • Herstel het beheer van PHP cron gebeurtenissen.
  • 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 and crontrol/filtered-events filters for adjusting the available event filters on the event listing screen.
  • Veel verbeteringen in de kwaliteit van de code (bedankt, PHPStan!).

1.10.0

  • Support for more granular cron-related error messages in WordPress 5.7
  • Verschillende toegankelijkheid verbeteringen
  • 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
  • Een help tabblad toevoegen met links naar de wiki en veelgestelde vragen

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.

1.8.5

  • Probleem met de tabbladen in 1.8.4 opgelost.

1.8.4

  • Een waarschuwing toevoegen als de standaardtijdzone is gewijzigd. Meer informatie..
  • Fixed string being passed to strtotime() function when the Now option is chosen when adding or editing an event.

1.8.3

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

1.8.2

  • Omzeil de controle op dubbele gebeurtenissen bij het handmatig uitvoeren van een gebeurtenis. Hierdoor kan een gebeurtenis handmatig worden uitgevoerd, zelfs als het binnen tien minuten moet gebeuren of als het te laat is.
  • Forceer slechts één gebeurtenis om af te vuren bij het handmatig uitvoeren van een cron gebeurtenis.
  • Voer polling van de gebeurtenissenlijst in om een waarschuwing te tonen wanneer het scherm met de gebeurtenissenlijst verouderd is.
  • 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.

1.8.1

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

1.8.0

  • Zoeken en pagineren voor cron gebeurtenissen
  • 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
  • Een meer uniforme UI
  • Gemoderniseerde codebase

1.7.1

  • Corrigeer de PHP.net URL voor de strtotime() referentie.

1.7.0

  • Remove the date and time inputs and replace with a couple of preset options and a plain text field. Fixes #24 .
  • Ervoor zorgen dat de naam van de planning altijd correct is als er meerdere planningen bestaan met hetzelfde interval. Foutafhandeling toevoegen. Herstelt #25.
  • De huidige tijd op de website opnieuw tonen.
  • Gebruik een geschiktere HTTP-antwoordcode voor onbevoegde aanvraagfouten.

1.6.2

  • Verwijder de mogelijkheid om een PHP cron event te verwijderen als de gebruiker geen bestanden kan bewerken.
  • 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.

1.6.1

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

1.6

  • Bulkverwijdering van cron events introduceren. Joepie!
  • Toon de naam van de planning in plaats van de interval naast elke gebeurtenis.
  • 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.
  • Verbeteringen aan de helptekst.
  • Remove usage of create_function().
  • Enkele vertaler reacties verbeteren, i18n verbeteren, coderingsstandaarden verbeteren.

1.5.0

  • 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.