Frequently asked questions

Not in 0.1.0. This release has no import path, and an automated test fails the build if one is added to it. Database restore is on the roadmap — see what's next.

In the meantime the archives are ordinary zip files containing an ordinary SQL dump, so you can restore from them with any tool you already use.

Not unless you tick the box for that specific backup. That file holds your database password and all eight authentication salts, so including it is a per-backup decision rather than a saved preference.

The .htaccess the plugin writes does nothing on nginx. Add this to your server block for a real deny rule, replacing the suffix with your own directory name:

location ~ ^/wp-content/fiction-drafts-[a-f0-9]{32}/ {
    deny all;
    return 404;
}

Without it, the protection is the unguessable directory name and the absence of a directory index. The download endpoint itself does not rely on this — it serves bytes through PHP behind a capability check and a single-use token.

No. The endpoint supports HTTP Range, so any download manager that resumes will resume. Compare the finished file against the SHA-256 shown for that volume to confirm it is complete.

Because you asked for a volume size, or because the default one applied. Very large single files are refused or truncated by a fair number of hosts and browsers. Each volume is a complete, independently checksummed zip.

Not yet. On a network install the screen and every endpoint require manage_network_options, so it will not half-work for a site administrator. Full multisite support is planned for a later version.

No. It makes no external requests of any kind — no telemetry, no account, no API calls, no remote fonts, scripts or images, and no key to register.

The work runs through Action Scheduler on background requests, in bounded slices. Nothing runs on your site's front end — the plugin registers no front-end hooks at all.

uninstall.phpremoves the plugin's own tables, options and storage directory. It deliberately leaves the actionscheduler_* tables alone, because those are shared with every other plugin that bundles the same library.

Action Scheduler (GPLv3) is bundled as this plugin's own Composer dependency, so background processing never depends on WooCommerce or any other plugin being installed. psr/container (MIT), react-router (MIT) and @tanstack/react-query (MIT) are also included. All are GPL-compatible. React itself is not bundled — the plugin uses the copy WordPress ships.