PRC Revisions

Canonical docs: docs/plugins/prc-revisions/

Public revision versioning and fork/merge workflow for PRC Platform. Enables editors to mark specific WordPress revisions as publicly accessible via versioned URLs, and to create draft forks of published posts that merge back on publish.

What it does

• Registers a /version/{letter} rewrite endpoint on all permalinks; visiting /post-slug/version/a serves the revision content in place of the current post content
• Lets editors toggle individual WordPress revisions as "public" from the block editor sidebar, assigning sequential version letters (a, b, … z, aa, …)
• Protects public revisions from deletion by WordPress's revision pruning
• Provides a "fork" workflow: duplicate a published post as a draft, edit it independently, and merge it back into the parent on publish
• Lets editors discard (trash) a pending future revision from the post status panel without merging
• Enforces one active fork per post at a time (409 on duplicate fork attempts)
• Excludes fork posts from publication listing queries (prc_platform_pub_listing_default_args)
• Injects version and isBasedOn properties into article structured data when viewing a versioned URL; adds hasPart to the parent post schema listing all public versions
• Copies attachments from a revision to the parent post on revision_applied
• Renders a yellow admin-bar banner on fork post previews, with optional scheduled-publish date
• Badges DataViews All Posts rows: Future Revision on fork drafts, Has Future Revision on the published parent

Key files

Filters / hooks

Actions

Filters

REST API endpoints

All routes are under the prc-revisions/v1 namespace.

Example: toggle a revision public

curl -X POST https://example.com/wp-json/prc-revisions/v1/toggle/42/789 \
  -H "X-WP-Nonce: {nonce}"
# Response: { "action": "added", "version": "a", "url": "https://example.com/my-post/version/a" }

Example: create a fork

curl -X POST https://example.com/wp-json/prc-revisions/v1/fork/42 \
  -H "X-WP-Nonce: {nonce}"
# Response: { "fork_id": 99, "edit_url": "https://example.com/wp-admin/post.php?post=99&action=edit" }

Example: discard (trash) a pending future revision

# Parent or fork ID both work:
curl -X DELETE https://example.com/wp-json/prc-revisions/v1/fork/42 \
  -H "X-WP-Nonce: {nonce}"
# Response: { "trashed": true, "fork_id": 99, "parent_id": 42 }

Block

prc-revisions/list

Renders a <ul> of all public revisions for a post, with linked version labels and optional dates. Intended for use in templates or post content where a version history list should appear.

Attributes

The block reads postId from block context. It renders nothing if the post has no public revisions.

Post meta

Enabling on additional post types

The plugin enables revision features on post and page by default. The chart custom post type (chart) opts in via @prc/chart-builder (Content_Type::register_revisions_support() on init priority 11).

To enable on other post types, call add_post_type_support from your plugin or theme:

add_action( 'init', function () {
    add_post_type_support( 'my-post-type', 'prc-revisions' );
} );

Plugin::get_enabled_post_types() returns all public post types currently supporting prc-revisions. This list drives fork meta registration and write-permission checks.

Version letter sequencing

Version letters are assigned automatically in alphabetical order: a, b, … z, aa, ab, … Removing a version letter does not reclaim it; the next assignment always increments past the highest letter currently in use.

Fork/merge lifecycle

1. Editor calls POST /prc-revisions/v1/fork/{post_id} — creates a draft with post_name set to {parent-slug}__fork, copies all meta (excluding the blocklist) and taxonomy terms.
2. Editor makes changes on the fork and publishes it.
3. prc_platform_on_publish fires at priority 5 — Future_Revisions::merge_fork() copies fork meta and taxonomy to parent first, then updates parent title/content/excerpt, re-parents attachments and child posts, fires revision_applied, marks fork as merged, and trashes the fork.
4. If merge fails, the fork is reverted to draft status.

Dependencies

• PHP 8.2+, WordPress 6.7+
• Requires plugin: prc-platform-core
• Uses \PRC\BlockUtils\load_blocks for block registration
• Schema integration requires prc-schema-seo filters (prc_schema_seo_article_schema, prc_schema_seo_schema_data) to be present; degrades silently if absent
• Fork post exclusion requires prc_platform_pub_listing_default_args filter to be consumed by the listing layer

Build

# Build blocks and inspector panel
npm run build -w @prc/revisions