Requirements
Minimum and recommended versions#
| Requirement | Minimum | Recommended |
|---|---|---|
| WordPress | 6.2 | 7.1 (the version the rules target; tested up to 7.1) |
| PHP | 7.4 | 8.1 or newer |
| User role | Administrator (manage_options) | Administrator |
| License | Not needed to scan | Active license key from your technoleet.dev account, for updates and support |
| Multisite | Supported (activate per site) | – |
| WP-CLI | Optional | Latest release, for the wp editor-readiness scan command |
| Action Scheduler | Optional | If another plugin (for example WooCommerce) provides it, background scan chunks use it instead of WP-Cron |
Server notes#
- The scan reads files in
wp-content/pluginsand your theme folders. PHP needs read access to them, which is the case on any working site. - Each scan chunk runs for at most 4 seconds in the browser (or half of PHP’s
max_execution_time, whichever is lower), so default PHP time limits are fine. - The scan takes a MySQL named lock (
GET_LOCK) so that two chunks never run at once. Standard MySQL and MariaDB hosting supports this. - Background chunks run through Action Scheduler when it is available, otherwise through WP-Cron. If WP-Cron is disabled on your host (
DISABLE_WP_CRON), keep the scan page open until the scan finishes, or make sure a system cron hitswp-cron.php.
Was this article helpful?
Tell us what was missing
