manifest / content / prc-post-publish-pipeline

PRC Post Publish Pipeline

WordPress plugin: PRC post publish pipeline (consumer mirror of prc-platform).

by Seth Rubenstein · github.com/pewresearch/prc-post-publish-pipeline · website

★ 0stars

0forks

Install

No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:

wp plugin install https://github.com/pewresearch/prc-post-publish-pipeline/archive/refs/heads/trunk.zip

Readme

PRC Post Publish Pipeline

Canonical docs: docs/plugins/prc-post-publish-pipeline/

Standalone PRC Platform plugin that provides standardized, lifecycle-aware WordPress hooks for tracking posts through creation, saving, publishing, updating, unpublishing, and trashing.

Consumed by many prc-* plugins; declared as a Requires Plugins dependency by every plugin that hooks into the pipeline. Force-loaded on VIP via client-mu-plugins/plugin-loader.php immediately after prc-platform-core.

What it does

The pipeline normalizes the chaotic WordPress post status transition hooks into a clean, predictable set of actions. It guards against WP-CLI execution (intentionally — pipeline hooks are for web/REST contexts only).

Available hooks

Sync tier (runs during the save request)

Hook	Fires when
`prc_platform_on_post_init`	A new post is first created
`prc_platform_on_incremental_save`	A post is saved while in `draft` or `publish`
`prc_platform_on_publish`	A post transitions to `publish`
`prc_platform_on_update`	An already-published post is updated
`prc_platform_on_unpublish`	A post transitions away from `publish`
`prc_platform_on_trash`	A post is trashed
`prc_platform_on_untrash`	A post is restored from trash
`prc_platform_on_status_transition`	Catch-all: fired on every observed status change. Args: `($post, $current, $prior, $has_blocks)`

Use the sync tier for post mutations, cache invalidation, and anything the editor or frontend must see immediately after save.

Async tier (deferred via Action Scheduler)

For each terminal lifecycle event above, the pipeline enqueues one Action Scheduler job (prc_platform_post_publish_pipeline_async_dispatch, group prc-post-publish-pipeline) that fires parallel async hooks with a freshly loaded post:

Hook	Fires when
`prc_platform_async_on_publish`	Async follow-up to a publish transition
`prc_platform_async_on_update`	Async follow-up to a published-post update
`prc_platform_async_on_unpublish`	Async follow-up to an unpublish transition
`prc_platform_async_on_untrash`	Async follow-up to an untrash transition
`prc_platform_async_on_trash`	Async follow-up to a trash transition
`prc_platform_async_on_incremental_save`	Async follow-up to an incremental save (`draft`/`publish` ↔ `draft`/`publish`)

Use the async tier for notifications, external API calls, and other deferrable side effects. prior_status is not available on async hooks.

The pipeline does not auto-enqueue incremental_save. Consumers enqueue it from sync prc_platform_on_incremental_save when work should be deferred.

Per-post-type variants exist for both tiers: prc_platform_on_{post_type}_publish, prc_platform_async_on_{post_type}_publish, etc.

Other plugins can enqueue async tier events directly:

\PRC\Platform\Post_Publish_Pipeline\enqueue_async_event( $post_id, 'publish' );

Supported events: publish, update, unpublish, untrash, trash, incremental_save.

JS pipeline actions

JS action	Fires when
`prc-platform.onPostInit`	First save of a new post
`prc-platform.onIncrementalSave`	Save while in `draft`
`prc-platform.onPublish`	Transition `draft` -> `publish`
`prc-platform.onUpdate`	Re-save while `publish`
`prc-platform.onUnpublish`	Transition `publish` -> `draft`
`prc-platform.onStatusTransition`	Catch-all: fires whenever post status changes between saves
`prc-platform.onSiteEdit`	Save in the Site Editor

Each action receives { edits, postId, postType, postStatus, priorStatus, isSiteEditor } where applicable.

Allowed post types

By default the pipeline tracks: post, feature, quiz, fact-sheet, short-read, events, mini-course, press-release, block_module, collections.

Extend via filter:

add_filter( 'prc_platform_post_publish_pipeline_post_types', function( $types ) {
    $types[] = 'my-cpt';
    return $types;
} );

WP Post object extension

Other platform components can attach additional data to the WP post object via the prc_platform_wp_post_object filter (priority 1). Use this to scaffold fields early and populate them lazily for performance.

Key files

File	Purpose
`prc-post-publish-pipeline.php`	Plugin entry point
`includes/class-bootstrap.php`	Pipeline hooks, REST fields, asset registration, and post type gating
`src/`	Block editor JS pipeline integration
`build/`	Compiled editor assets

Hooks

Hook	Direction	Description
`enqueue_block_editor_assets`	Action	Enqueues JS pipeline integration
`prc_platform_post_publish_pipeline_post_types`	Filter	Extend tracked post types
`prc_platform_post_publish_pipeline_should_process`	Filter	Return `false` to skip all sync-tier `prc_platform_on_*` hooks and async-tier enqueue for a write (e.g. bulk relationship sync). Args: `$should_process`, `$post_id`, `$post_obj_now`, `$is_update`, `$post_obj_before`
`prc_platform_wp_post_object`	Filter	Extend the WP post object shape

Notes

Pipeline hooks do not fire in WP-CLI context — this is intentional
REST API requests are tracked (is_rest is set but does not block execution)

Read the full README on GitHub →