Numbers in brackets show the issue number in https://github.com/wp-document-revisions/wp-document-revisions/issues/

5.8.3

• Activating the plugin for the first time no longer shows a false "You do not have the edit_documents capability" warning. On WordPress Playground, including the Live Preview on WordPress.org, the plugin activates on every visit, so every session showed it. (#887, #890) Thanks to @NeilWJames for reporting it.
• When the server can't read a document's file, for example after a PHP upgrade changes the account PHP runs as, opening the document now shows a message explaining that the file isn't readable, instead of a blank error page. (#885, #889)
• The plugin no longer bundles its Norwegian (Bokmål), Polish and Turkish translations. WordPress now installs these from translate.wordpress.org language packs, so nothing changes on sites using those languages. (#894)
• Code examples on the WordPress.org plugin page now display as code. (#901)

5.8.2

• Security: WordPress's embed lookup (oEmbed) gave out the stored file name of a document's files. Document files sit in the uploads folder by default, so on sites that don't block that folder, anyone could use the name to download the file of a password-protected document, or any earlier version of a published one. The embed lookup now refuses document files, and visitors who can't edit a document see the document's title instead of a file's stored name (GHSA-5452-pc3q-85f6).
• Security: on sites that turn on documents in the REST API with the document_show_in_rest filter (off by default), a Contributor could make another user's document go back to serving one of its older files the next time that document was saved. If a document is serving an old file, upload the current file again (GHSA-c47p-xwvp-x5rm).
• Security: REST term counts for document taxonomies included draft, pending and private documents, so anyone could see how many non-public documents carry each workflow state or custom document taxonomy term. They now count only published documents, unless the user can already see every document (GHSA-vp9c-qx2m-x9r8). Thanks to Andrew Melek for reporting it.
• A document URL with a malformed revision value, such as ?revision=abc, now gets the normal not-found response instead of a server error. (#874) Thanks to Andrew Melek for reporting it.
• The plugin now stops sending uploads to the document folder in the same place it marks a document upload as finished, so that redirect can't stay on for the rest of the request when its file-name step is skipped. (#862)

5.8.1

• Uploading a new version of a document now replaces the document's file in a few rare cases where it didn't, such as an image or audio file with an embedded title, or a site using the document_internal_filename filter. Before, the upload appeared to succeed, but clicking Update put the document back on its old file. If a document got stuck on its old file, upload the new version again. (#858) Thanks to @cvladan for reporting it.

For complete changelog, see GitHub

🚀 Automatic Install (Recommended)

1. Log into WordPress Admin - Login to your WordPress site as an Administrator, or if you haven't already, complete the WordPress installation
2. Go to Plugins - Navigate to Plugins > Add New from the left menu
3. Search - Search for "WP Document Revisions"
4. Install - Click "Install Now" next to WP Document Revisions
5. Activate - Click "Activate" to enable the plugin

📦 Manual Install

1. Download - Get the latest version from WordPress.org or GitHub Releases
2. Upload - Unzip the file and upload the "wp-document-revisions" folder to your /wp-content/plugins/ directory
3. Activate - Log into WordPress admin, go to Plugins, and activate "WP Document Revisions"

💻 Developer Install

For development or contributing:

git clone https://github.com/wp-document-revisions/wp-document-revisions.git
cd wp-document-revisions
composer install --no-dev

⚙️ Requirements

• WordPress: 5.0 or higher
• PHP: 7.4 or higher
• File Permissions: WordPress must be able to write to the uploads directory

🎯 Next Steps

After installation, you'll find a new Documents menu in your WordPress admin. Start by:

1. Creating your first document - Go to Documents > Add New
2. Setting up workflow states (optional) - Go to Documents > Workflow States
3. Configuring permissions - Review Settings > Document Revisions

Need help? Check our FAQ or get support.

Every document keeps a complete, audited revision history — who changed what and when, each with a summary and one-click restore.



Manage all your documents in one place — see each document's owner, workflow state, and who currently has it checked out, and filter by state or owner.



Model your team's review process with fully customizable workflow states.