BookPress Readiness

A free WordPress plugin that checks whether BookPress can run your site.

It reads the plugins and theme installed on your site, changes nothing, and reports which of them run on BookPress.

Version 1.0.0, 57 KB, GPLv2 or later. WordPress 5.6 or later, PHP 7.2 or later.

Install it

1. Download the plugin.
2. In wp-admin, open Plugins, Add New, Upload Plugin.
3. Choose the zip, press Install Now, then Activate.
4. Open Tools, BookPress Readiness.
5. Press Run the scan.

You need an administrator account. With WP-CLI, one command replaces steps 1 to 3:

wp plugin install https://bookpress.io/readiness/bookpress-readiness.zip --activate

What it checks

• Active plugins, and inactive ones in a separate list that does not count against your result.
• Must-use plugins, which WordPress leaves off the Plugins screen.
• Drop-ins such as object-cache.php and db.php.
• The active theme and its parent.
• Which settings wp-config.php defines. It looks at the names, never at the values.
• WordPress core, against the checksums WordPress.org publishes.

The plugin reads the PHP installed on your site, so it covers custom and private plugins too.

What the result means

• Ready. The scan found nothing that would stop your site running on BookPress.
• Needs checking. The scan found nothing that breaks for certain, and it could not decide everything it read. A person should look.
• Not ready. Something on the site would not run. The report names each blocker with its file and the reason.

The report marks WordPress core OK, MODIFIED or UNKNOWN. A modified core makes the result Not ready.

What it does not do

We made the scan cautious on purpose.

• It cannot tell whether code is reachable. A call inside if (false) still counts.
• It makes no claim about calls assembled at run time, such as $fn() or call_user_func.
• If WordPress.org's checksum service does not answer, it reports core as unknown.

It writes no files and creates no tables. It stores one option, bpr_run_state, which holds the scan's result.

Each scan makes two requests:

• https://bookpress.io/readiness/policy.json, the list of what BookPress supports today. Our server sees your IP address, the time, and the user agent BookPressReadiness/1.0.0. The request carries no site URL and no cookie. The plugin holds no copy of the list, so if the fetch fails the scan does not start.
• https://api.wordpress.org/core/checksums/1.0/, with your WordPress version and locale. This one goes to WordPress.org.

Nothing else leaves your site unless you press a button. Send my result sends the email address you type, the verdict and the version of the support list the scan used. If you tick the box it also sends the blockers, the core check result, the names of your drop-ins and, on a network, its shape and site count. Send the inventory sends the name, version and active state of each plugin and theme, with your WordPress and PHP versions. The screen shows each payload before you send it.

Multisite

BookPress converts a network into separate sites. The report gives the site count, tells you whether the network uses subdomains, which convert, or subdirectories, which do not, and lists what changes: users become per-site, the super admin goes away, and network-activated plugins become each site's own.

After the scan

Try the demo, or start with one site for €1. The migration is one command. Render times by site type are on the speed page.

Remove the plugin

Under Plugins, deactivate BookPress Readiness, then delete it. Deactivating deletes the one option. The plugin creates no tables, transients, scheduled tasks or files, so nothing stays behind on a single site. On a multisite network, delete the option bpr_run_state on each sub-site where you ran a scan.