內容簡介
考慮 WordPress 預設使用的 8 個文章狀態：
* Publish：任何人都可以查看。（publish）
* Future：計畫在未來的某個時間發佈。（future）
* Draft：未完成的文章，任何具備正確使用者角色的人都可以查看。（draft）
* Pending：等待擁有 publish_posts 權限的使用者（通常是分派 Editor 角色的使用者）發佈。（pending）
* Private：僅限 WordPress 網站管理員能夠查看。（private）
* Trash：位於回收桶中的文章擁有 trash 狀態。（trash）
* Auto-Draft：當您編輯文章時 WordPress 自動儲存的版本。（auto-draft）
* Inherit – 與子文章（如附件和修訂）一起使用，以決定從父文章繼承實際狀態。（inherit）
典型的出版工作流程如下：
自動草稿 > Draft > Pending > Future > Publish
然後呢？Trash？Private？這些似乎不適合。
這時，此外掛提供的「未發佈」（unpublish）文章狀態就派上用場了。
它允許內容發布者將想要不發佈的內容指定為專用狀態，並避免指定不適切的狀態。
外掛標籤
開發者團隊
原文外掛簡介
Consider the 8 default post statuses that WordPress uses by default:
* Publish: Viewable by everyone. (publish)
* Future: Scheduled to be published in a future date. (future)
* Draft: Incomplete post viewable by anyone with proper user role. (draft)
* Pending: Awaiting a user with the publish_posts capability (typically a user assigned the Editor role) to publish. (pending)
* Private: Viewable only to WordPress users at Administrator level. (private)
* Trash: Posts in the Trash are assigned the trash status. (trash)
* Auto-Draft: Revisions that WordPress saves automatically while you are editing. (auto-draft)
* Inherit – Used with a child post (such as Attachments and Revisions) to determine the actual status from the parent post. (inherit)
A typical publishing workflow would be:
Auto-Draft > Draft > Pending > Future > Publish
But what then? Trash? Private? These seem inadapted.
This is where the Unpublished (unpublish) post status provided by this plugin comes into play.
It allows content publishers to assign a dedicated status to content they desire not to be published, and avoid assigning a semantically inaccurate status.
