WordPress 5
Monitoring the sites still on WordPress 5 and PHP 7.4
Many client sites stay on WordPress 5 because a theme or plugin cannot take the update, or because the host still runs PHP 7.4. They need watching like the others, or more.
The problem
Old versions have different APIs.
WordPress's date and time zone APIs arrived in 5.3. An agent that relies on them with no fallback gets times wrong or stops on earlier versions.
And the longer a site stays put, the more known vulnerabilities pile up in its core and plugins.
How it works
Tested on every 5.x release.
- 1
Real installs
WordPress 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8 and 5.9 with PHP 7.4.
- 2
The same checks
Connection, events, one-click login, core integrity, scanning, backup and restore on every version.
- 3
Updates
Real core updates with the WordPress installer: one notification per update.
In detail
In detail.
- Core integrity with the official checksums: from 1,488 files on 5.0 to 2,373 on 5.9
- Known core and plugin vulnerabilities from Wordfence Intelligence
- Correct event times even before the APIs introduced in 5.3
- Agent updates before 5.5 too, with the native installer
- Encrypted backups and restores of database and files
FAQ
Frequently asked questions
Do I need PHP 8?
No, the WordPress agent runs from PHP 7.4. The PHP version must also suit the installed WordPress version.
What about WordPress 4?
No, support starts at 5.0.
Related features
Goes well with
Try it on your clients' sites.
During the beta we let in a few agencies at a time and set up the first sites with you.