Description
Reprint Server connects your WordPress site to the open-source Reprint command-line client. The client can download the site’s database and files, build a local copy, and synchronize files with the source site.
Transfers stream in chunks and can resume after interruption. You do not need to create one large backup archive on your hosting account.
The plugin provides the server API and its settings page. You need the separate Reprint client to run transfers. There is no hosted Reprint account or subscription requirement.
Authentication
On hosts with OpenSSL, enroll the client’s Migration Token under Tools > Reprint Server. The client keeps the private key and signs its requests. Hosts without OpenSSL use a connection token instead.
The WordPress.org build provides downloads only and does not include file-push or database-push implementations. The GitHub build also supports push.
New keys and connection tokens authorize downloads only. In the GitHub build, file push requires a separate administrator grant. While enabled, an authorized client can upload, replace, and delete files in the site’s document root, except excluded paths. Hosting providers can manage this permission centrally.
Push requires PHP 7.2 or newer and is not supported on multisite networks.
The WordPress.org package requires PHP 7.2 or newer. The GitHub package supports downloads on PHP 5.6.20 or newer. Use a maintained PHP version when your host allows it.
Site data and privacy
The plugin sends site data to the Reprint client you authorize. Exported databases and files may contain personal data, password hashes, and configuration secrets. Treat client credentials and downloaded site copies as private. Use HTTPS for remote transfers, and remove client access when it is no longer needed.
On multisite, network administrators manage access. Enrolled keys or the network connection token can authorize downloads from sites in that network. See the multisite documentation before transferring a network or an individual site.
Source and build instructions
The maintained PHP source, license, and build tools are available in the Reprint repository. GitHub release builds downgrade a copy of the server’s PHP syntax for older hosting environments. The WordPress.org build keeps the maintained PHP 7.2 source. Both bundle the server package with Composer. No build tools are required on the installed site.
Build the GitHub package with bin/build-server-plugin.sh after installing the Composer dependencies in tools/php56-build. For the downloads-only directory package, run bin/build-server-plugin.sh reprint-wordpress-org.zip wordpress-org; that target uses the maintained PHP 7.2 source and does not need the downgrade tool. See reprint-server-wp/README.md in the repository for integration and hosting configuration.
Screenshots
Installation
- Install Reprint from the WordPress.org plugin directory, or download a plugin ZIP from the GitHub releases.
- In WordPress, open Plugins > Add New > Upload Plugin, upload the ZIP, and activate Reprint Server. On multisite, network-activate the plugin.
- Download reprint.phar from the same release. The client requires PHP 7.4 or newer; file push from the client requires PHP 8.1 or newer.
Run the pull command below. On a host with OpenSSL, the client prints the Migration Token to enroll and stops. Enroll it under Tools > Reprint Server, then run the same command again. On multisite, use the network settings page.
php reprint.phar pull https://example.com –state-dir=./state –fs-root=./files
On a host without OpenSSL, save a connection token in the plugin settings and pass it to the client with –secret=TOKEN. See the client documentation for command options and credential storage.
FAQ
-
Does activating the plugin start a transfer?
-
No. Configure client access, then start the transfer from the Reprint client. Activation alone does not authorize a client.
-
Can I migrate this site to another host?
-
Yes. Downloads are enough to copy this site to another host or a local development environment.
-
How do I revoke access?
-
Remove an enrolled Migration Token in Tools > Reprint Server. On a host using connection tokens, clear or replace the token. Credentials supplied by your host through public-keys.php, secret.php, or managed configuration must be changed by the host.
-
What happens when I deactivate or delete the plugin?
-
Deactivation keeps the settings. Deleting the plugin through WordPress removes its stored credentials, push grants, and activation transient, including legacy settings. It does not delete migrated site files, downloaded client copies, or host-configured files and private transfer directories outside the plugin directory.
-
Where can I report a problem?
-
Use the Reprint issue tracker for reproducible bugs and feature requests. Do not include private keys, connection tokens, private site data, or database credentials in a public report. Do not post security vulnerability details in a public issue.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Reprint” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Reprint” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
See the GitHub release notes for the changes in each release.