Staging¶

The wp staging pull CLI command synchronises selected production data — posts, postmeta, terms, options, and files — into a staging or local environment.

The command is registered by Modules\Staging\CLI\CommandsProvider and only runs when WP_ENV is development or staging.

Required environment variables¶

Usage¶

wp staging pull

What gets copied¶

Database¶

Default post types copied:

nav_menu_item, shop_coupon, product, product_variation,
page, post, attachment, cancellation_reason, elementor_library

Options copied:

page_on_front, template, stylesheet, theme_mods_*, elementor_*

URL replacement¶

After copying, all occurrences of the production domain are replaced with the staging domain in:

• wp_options table
• wp_posts.post_content
• Elementor serialised data (via wp elementor replace-urls)

Override replacements per table with:

add_filter('staging/db-replacements/wp_options', function (array $replacements): array {
    $replacements['https://old.example.com'] = 'https://new.example.com';
    return $replacements;
});

Files¶

Synced from STAGING_PULL_SOURCE_SHARED_DIR to STAGING_SHARED_DIR for these folders:

• languages
• uploads (with blacklist: dao-labels-bulk, csv_exports, elementor, etc.)

Lifecycle hooks¶

Hooks fire before and after each major operation:

staging/pull/posts/before      staging/pull/posts/after
staging/pull/postmeta/before   staging/pull/postmeta/after
staging/pull/terms/before      staging/pull/terms/after
staging/pull/options/before    staging/pull/options/after
staging/pull/files/before      staging/pull/files/after

Use them to add custom pre/post-processing:

add_action('staging/pull/posts/after', function () {
    // e.g. clear a custom cache after posts are replaced
});

Extending the pull¶

To copy additional post types:

// Hook into the command before it runs to modify the post_types array
add_filter('staging/pull/post-types', fn(array $types) => array_merge($types, ['my_post_type']));