Features

Three modules, each one worth switching on

Editloft is a small plugin with a clear job. It shows you what is planned, records what happened, and controls who can publish. Here is what each part does and where it stops.

By Christopher Ross. Last updated .

Also included

The details that make it usable

One settings screen

Switch each module on or off. Disabled modules load nothing.

Post type support

The calendar and the audit trail work with any public post type, and the rules can be applied to posts and pages by default.

Capability aware

The calendar respects a view capability you can change with a filter, and the audit trail is only shown to people who can edit the post.

Signed calendar feed

The iCal feed is off by default and signed with HMAC-SHA256 when you turn it on.

Script friendly

WP-CLI and scheduled publishes are never blocked by the rules, and they are recorded like any other change.

Made for teams

Designed around the roles WordPress already has, so there is nothing to map or migrate.

Straight talk

What Editloft does not include

Edit Flow had more modules than Editloft has today. Editloft's first release carried several of them, and on 2026-09-20 I retired custom post statuses, editorial comments, editorial metadata, notifications, the dashboard widget and Cloud Sync. None of them had real content behind it on the site I built Editloft for, and unused code is a liability.

That means there are no custom post statuses beyond the ones WordPress ships, no private editorial comments, no editorial metadata fields, no email notifications and no story budget. If your team depends on those, read the comparison before you switch. The retired code is kept in the repository's legacy folder, and modules can return if there is a real need.

Free, open source, GPLv2

Try Editloft on a staging copy of your site

It is free, it takes a minute to install, and you can switch each module off again from one settings screen.