Update WP Crontrol plugin from 1.19.3 to 1.20.0

Author: bitpoke-bot

wp-content/plugins/wp-crontrol/SECURITY.md

@@ -1,4 +1,4 @@
-# Security Policy
+# WP Crontrol Security Policy
 
 ## How can I report a security bug?
 

wp-content/plugins/wp-crontrol/composer.json

@@ -26,21 +26,13 @@
 		}
 	},
 	"require-dev": {
-		"behat/gherkin": "< 4.13.0",
-		"codeception/module-asserts": "^1.0",
-		"codeception/module-db": "^1.0",
-		"codeception/module-webdriver": "^1.0",
-		"codeception/util-universalframework": "^1.0",
-		"dealerdirect/phpcodesniffer-composer-installer": "^0.7.0",
-		"johnbillion/plugin-infrastructure": "dev-trunk",
-		"johnbillion/wp-compat": "^1.2",
-		"lucatume/wp-browser": "3.2.1",
-		"phpcompatibility/phpcompatibility-wp": "2.1.6",
-		"phpstan/phpstan": "2.1.12",
-		"roots/wordpress-core-installer": "1.100.0",
-		"roots/wordpress-full": "*",
-		"szepeviktor/phpstan-wordpress": "2.0.1",
-		"wp-coding-standards/wpcs": "3.1.0"
+		"johnbillion/plugin-infrastructure": "2.1.7",
+		"johnbillion/wp-compat": "1.4.0",
+		"php-stubs/wordpress-stubs": "6.9.0",
+		"phpcompatibility/phpcompatibility-wp": "2.1.8",
+		"phpstan/phpstan": "2.1.33",
+		"szepeviktor/phpstan-wordpress": "2.0.3",
+		"wp-coding-standards/wpcs": "3.3.0"
 	},
 	"require": {
 		"php": ">=7.4",
@@ -51,6 +43,11 @@
 			"src"
 		]
 	},
+	"autoload-dev": {
+		"psr-4": {
+			"Crontrol\\Tests\\": "tests/integration"
+		}
+	},
 	"extra": {
 		"wordpress-install-dir": "vendor/wordpress/wordpress"
 	},
@@ -61,27 +58,43 @@
 		"test": [
 			"@composer validate --strict --no-check-lock",
 			"@test:phpstan",
+			"@test:phpcbf",
 			"@test:phpcs",
-			"tests-start",
+			"@test:start",
+			"@test:integration",
 			"@test:acceptance",
-			"tests-stop"
+			"@test:stop"
 		],
 		"test:acceptance": [
 			"acceptance-tests"
 		],
+		"test:integration": [
+			"integration-tests"
+		],
 		"test:phpcs": [
 			"phpcs -nps --colors --report-code --report-summary --report-width=80 --basepath=./ ."
 		],
+		"test:phpcbf": [
+			"phpcbf -nps --colors --report-code --report-summary --report-width=80 --basepath=./ ."
+		],
 		"test:phpstan": [
-			"codecept build #",
 			"phpstan analyze -v --memory-limit=1024M"
+		],
+		"test:start": [
+			"tests-start"
+		],
+		"test:stop": [
+			"tests-stop"
+		],
+		"test:destroy": [
+			"tests-destroy"
 		]
 	},
 	"support": {
 		"issues": "https://github.com/johnbillion/wp-crontrol/issues",
 		"forum": "https://wordpress.org/support/plugin/wp-crontrol",
 		"source": "https://github.com/johnbillion/wp-crontrol",
-		"security": "https://patchstack.com/database/vdp/wp-crontrol"
+		"security": "https://wp-crontrol.com/security/"
 	},
 	"funding": [
 		{

wp-content/plugins/wp-crontrol/css/index.php

@@ -12,6 +12,14 @@ table.wp-list-table {
 	margin: 0;
 }
 
+.wp-list-table details summary {
+	cursor: pointer;
+}
+
+.wp-list-table details pre {
+	margin-top: 5px;
+}
+
 .wp-list-table code {
 	background: transparent;
 	padding: 0;
@@ -36,8 +44,8 @@ table.wp-list-table {
 	border-color: #d63638;
 }
 
-.wp-list-table tr.crontrol-inactive .column-crontrol_next,
-.wp-list-table tr.crontrol-inactive .column-crontrol_schedule,
+.wp-list-table tr.crontrol-disabled .column-crontrol_next,
+.wp-list-table tr.crontrol-disabled .column-crontrol_schedule,
 .wp-list-table tr.crontrol-paused .column-crontrol_next,
 .wp-list-table tr.crontrol-paused .column-crontrol_schedule,
 .wp-list-table tr.crontrol-paused:not(.crontrol-no-action) .column-crontrol_actions {
@@ -69,7 +77,7 @@ table.wp-list-table {
 	color: #d63638;
 }
 
-.status-crontrol-inactive .dashicons {
+.status-crontrol-disabled .dashicons {
 	background: #646970;
 	border-radius: 50%;
 	color: #fff;
@@ -108,3 +116,7 @@ input[type="time"][step="1"] {
 .crontrol-edit-event-php .crontrol-event-standard {
 	display: none;
 }
+
+#crontrol-event-not-found {
+	margin-top: 2em;
+}

wp-content/plugins/wp-crontrol/css/wp-crontrol.css

@@ -2,8 +2,8 @@
 
 Contributors: johnbillion, scompt
 Tags: cron, wp-cron, crontrol, debug, woocommerce
-Tested up to: 6.8
-Stable tag: 1.19.3
+Tested up to: 6.9
+Stable tag: 1.20.0
 License: GPL v2 or later
 Donate link: https://github.com/sponsors/johnbillion
 
@@ -143,7 +143,7 @@ There are two steps to getting a functioning cron event that executes regularly.
 
 *Step One: Adding the event*
 
-From the Tools → Cron Events menu, click on Add New Cron Event. Fill out the details of the event. You're best off using a hook name that conforms to normal PHP variable naming conventions. The schedule is how often the event will be executed. If you don't see a good interval, then add one in the Settings → Cron Schedules menu.
+From the Tools → Cron Events menu, click on Add Cron Event. Fill out the details of the event. You're best off using a hook name that conforms to normal PHP variable naming conventions. The schedule is how often the event will be executed. If you don't see a good interval, then add one in the Settings → Cron Schedules menu.
 
 *Step Two: Writing the function*
 
@@ -163,13 +163,13 @@ function my_function() {
 
 ### How can I create a cron event that requests a URL?
 
-From the Tools → Cron Events menu, click on Add New Cron Event. Select the "URL cron event" option, fill out the details, and press the "Add Event" button.
+From the Tools → Cron Events menu, click on Add Cron Event. Select the "URL cron event" option, fill out the details, and press the "Add Event" button.
 
 [You can read all about the features and security of URL cron events on the WP Crontrol website](https://wp-crontrol.com/docs/url-cron-events/).
 
 ### How do I create a new PHP cron event?
 
-From the Tools → Cron Events menu, click on Add New Cron Event. Select the "PHP cron event" option 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 menu. 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`).
+From the Tools → Cron Events menu, click on Add Cron Event. Select the "PHP cron event" option 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 menu. 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](https://wp-crontrol.com/docs/php-cron-events/).
 
@@ -212,6 +212,13 @@ The photo was taken by <a href="https://www.flickr.com/photos/michaelpardo/21453
 3. New cron schedules can be added, giving plugin developers more options when scheduling events
 ## Changelog ##
 
+### 1.20.0 (17 December 2025) ###
+
+* Confirms support for WordPress 6.9
+* Minor UI and UX improvements
+* Some architectural changes to prepare for future enhancements
+
+
 ### 1.19.3 (23 October 2025) ###
 
 * Corrects the handling of closures as cron event actions.
@@ -262,10 +269,6 @@ The photo was taken by <a href="https://www.flickr.com/photos/michaelpardo/21453
 * Confirms support for WordPress 6.5
 
 
-### 1.16.1 (16 November 2023) ###
-
-* Confirms support for WordPress 6.4
-
 ### Earlier versions ###
 
 For the changelog of earlier versions, <a href="https://github.com/johnbillion/wp-crontrol/releases">refer to the releases page on GitHub</a>.

wp-content/plugins/wp-crontrol/index.php

@@ -0,0 +1,25 @@
+<?php
+/**
+ * Feature flag context for WP Crontrol.
+ *
+ * @package wp-crontrol
+ */
+
+namespace Crontrol\Context;
+
+/**
+ * Interface for checking feature flags.
+ *
+ * Provides methods to check if various cron event features are enabled.
+ */
+interface FeatureContext {
+	/**
+	 * Check whether PHP cron events are enabled globally on the site.
+	 */
+	public function php_crons_enabled(): bool;
+
+	/**
+	 * Check whether URL cron events are enabled globally on the site.
+	 */
+	public function url_crons_enabled(): bool;
+}

wp-content/plugins/wp-crontrol/js/index.php

@@ -0,0 +1,76 @@
+<?php
+/**
+ * User capability context for WP Crontrol.
+ *
+ * @package wp-crontrol
+ */
+
+namespace Crontrol\Context;
+
+/**
+ * Interface for checking user capabilities.
+ *
+ * Provides methods to check if the current user has permission to perform
+ * various operations on different types of cron events.
+ */
+interface UserContext {
+	/**
+	 * Check if the user can create PHP cron events.
+	 */
+	public function can_create_php_cron_events(): bool;
+
+	/**
+	 * Check if the user can edit PHP cron events.
+	 */
+	public function can_edit_php_cron_events(): bool;
+
+	/**
+	 * Check if the user can delete PHP cron events.
+	 */
+	public function can_delete_php_cron_events(): bool;
+
+	/**
+	 * Check if the user can run PHP cron events.
+	 */
+	public function can_run_php_cron_events(): bool;
+
+	/**
+	 * Check if the user can create URL cron events.
+	 */
+	public function can_create_url_cron_events(): bool;
+
+	/**
+	 * Check if the user can edit URL cron events.
+	 */
+	public function can_edit_url_cron_events(): bool;
+
+	/**
+	 * Check if the user can delete URL cron events.
+	 */
+	public function can_delete_url_cron_events(): bool;
+
+	/**
+	 * Check if the user can run URL cron events.
+	 */
+	public function can_run_url_cron_events(): bool;
+
+	/**
+	 * Check if the user can create standard cron events.
+	 */
+	public function can_create_standard_cron_events(): bool;
+
+	/**
+	 * Check if the user can edit standard cron events.
+	 */
+	public function can_edit_standard_cron_events(): bool;
+
+	/**
+	 * Check if the user can delete standard cron events.
+	 */
+	public function can_delete_standard_cron_events(): bool;
+
+	/**
+	 * Check if the user can run standard cron events.
+	 */
+	public function can_run_standard_cron_events(): bool;
+}

wp-content/plugins/wp-crontrol/readme.txt

@@ -0,0 +1,28 @@
+<?php
+/**
+ * WordPress feature flag context implementation.
+ *
+ * @package wp-crontrol
+ */
+
+namespace Crontrol\Context;
+
+use function Crontrol\php_cron_events_enabled;
+use function Crontrol\url_cron_events_enabled;
+
+/**
+ * FeatureContext implementation that checks WordPress constants and options.
+ *
+ * This is the production implementation that reads from the WordPress environment.
+ */
+class WordPressFeatureContext implements FeatureContext {
+	#[\Override]
+	public function php_crons_enabled(): bool {
+		return php_cron_events_enabled();
+	}
+
+	#[\Override]
+	public function url_crons_enabled(): bool {
+		return url_cron_events_enabled();
+	}
+}