[WordPress] 外掛分享: Simple Revisions Delete

首頁外掛目錄 › Simple Revisions Delete
WordPress 外掛 Simple Revisions Delete 的封面圖片
10,000+
安裝啟用
★★★★
4.9/5 分(49 則評價)
8 天前
最後更新
100%
問題解決
WordPress 6.4+ PHP 7.4+ v2.0.1 上架:2015-01-04

內容簡介

Simple Revisions Delete 外掛允許使用者單獨或批量刪除文章的修訂版本,幫助保持資料庫的整潔。它與區塊編輯器和經典編輯器兼容,操作簡單,無需額外設定。

【主要功能】
• 單一文章修訂刪除
• 批量刪除多篇文章修訂
• 與區塊編輯器和經典編輯器兼容
• 無需額外設定頁面
• 透過 REST API 安全刪除修訂

外掛標籤

開發者團隊

⬇ 下載最新版 (v2.0.1) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「Simple Revisions Delete」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

Delete the revisions of your posts individually or all at once, either from the editor or through a bulk action. Works with both the block editor and the classic editor.
What does it do?
Simple Revisions Delete adds a discreet purge control next to the revisions counter of the post you are editing. One click and the revisions of that post are gone.
It helps you keep a clean database by removing unnecessary post revisions. Unlike most similar plugins, it lets you delete the revisions of a specific post rather than wiping every revision of your site at once.
The plugin blends into the WordPress admin, relies exclusively on core functions to delete revisions safely, and adds no settings page: there is nothing to configure.
How does it work?

In the block editor, a “Purge” button sits in the post status panel of the sidebar, right below the publishing options. It tells you how many revisions the post has and deletes them all in one request.
In the classic editor, the same control appears in the Publish metabox, and each revision listed in the Revisions metabox gets its own “Delete” button.
In the posts and pages list, a “Purge revisions” bulk action lets you clean up several posts at once.

Everything happens through the WordPress REST API, so no page reload is needed. Without JavaScript, the classic editor control falls back to a regular form submission and the bulk action keeps working.
What’s new in 2.0?
The block editor integration has been rewritten from scratch. The previous version relied on jQuery and on the internal markup of the editor, which stopped working when Gutenberg 7.1 reorganised its DOM. The purge control is now a genuine editor plugin (PluginPostStatusInfo) reading and writing through a dedicated REST API, so it no longer depends on class names that can change at any release.
The rest of the plugin has been rewritten too: one class per responsibility, no more inline

文章
Filter
Mastodon