內容簡介
Self Destructing Posts 外掛讓編輯者可以將文章標記為短暫性內容，設定文章的消失方式與時間，並在發佈後首次合格的讀者打開文章時，自動銷毀。這是一個內容生命週期工具，並非安全或保密產品。
【主要功能】
• 文章自毀面板，支援區塊編輯器與經典編輯器
• 設定合格閱讀觸發條件
• 可配置的寬限期，決定自毀時間
• 支援多種銷毀行動，如移至垃圾桶或永久刪除
• 自毀後的 URL 回應選項，如 410 Gone 或自訂訊息
• 管理員/編輯者豁免，減少意外銷毀風險
外掛標籤
開發者團隊
原文外掛簡介
Self Destructing Posts lets an editor mark a post as ephemeral. Turn on Enable self-destruct, choose how and when the post should disappear, and publish. The first qualified reader opens it, and the post self-destructs after your chosen grace period.
This is a content-lifecycle tool, not a security or secrecy product. It cannot prevent screenshots, copying, browser cache, search-engine indexing, or a recipient sharing the URL. Treat it as “this post is meant to be temporary,” not “this post is secret.”
What it does
A Self-Destruct panel in the block editor (and a classic-editor meta box) to enable and configure per post.
First qualified read trigger — a real reading event, not a crawler or link preview.
A configurable grace period between the qualifying read and destruction.
Destructive actions: Move to Trash, Draft, Private, Replace with a message, or Permanently delete.
Destroyed-URL responses: 410 Gone (default), 404, redirect, or a custom message — served even if the post was permanently deleted.
Atomic arming so exactly one reader arms a post under concurrent traffic.
No-store cache headers and noindex/nofollow/noarchive on self-destruct posts.
Exempts administrators/editors, and filters known bots, previews, prefetch, HEAD, REST and feed requests to reduce accidental destruction.
A repair tool that completes destructions if WP-cron ran late, and an emergency pause that halts all pending destructions.
A minimal audit log of state transitions that never stores the destroyed post’s content.
What it deliberately does NOT do
Guarantee secrecy or DRM.
Prevent screenshots, copy/paste, saved pages, reader mode, or browser history.
Remove content already cached or indexed by search engines, CDNs, social networks, or browsers.
Track the identity of individual readers.
An already-cached page cannot be reliably “unread.” Caching is the single biggest practical risk — the plugin sends no-store headers and integrates with common cache plugins on a best-effort basis, but it cannot promise universal cache bypass.