WP Manifestindependent plugin directory
manifest / updates / wp-sync-tool

LivePull

Pull the content your client adds or edits on the live site into your local copy, without overwriting your own work. Install on both sites, then go to Tools → LivePull (or run `wp livepull` in the terminal).

★ 0stars

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/alexmciver/wp-sync-tool/archive/refs/heads/main.zip
Updates itself. It ships its own updater, so new versions appear under Dashboard → Updates.

Pull your client's content changes from a live WordPress site into your local copy — without overwriting your own work.

You're building or fixing something on a local or staging copy. Meanwhile the client keeps adding posts, pages, products and images on the live site. Normally you either work on stale content or copy the whole database down again and lose your changes. LivePull gives you a third option: bring across just what changed on live, and leave anything you've changed locally alone.

  • Pull changes – new and edited posts, pages, custom post types, media, categories/tags, custom fields, menus and key site settings.
  • Never overwrites your work – if something changed on live and locally, it's left alone and flagged as a conflict for you to decide.
  • Copy everything from live – a full database + uploads copy when you want to start fresh, with URLs rewritten safely.
  • Undo – a backup is taken before every pull and copy; restore from the dashboard.
  • Works from WordPress or the terminal – Tools → LivePull, or wp livepull (WP-CLI).
  • Read-only on live – nothing is ever written to the live site.

LivePull is tested end to end on every change (see Tested with), but every site is different. It backs up your local site before every pull, and it's worth trying it on a copy first. See Limitations.

The LivePull screen on a local site


Requirements

  • WordPress 6.2 or newer, PHP 7.4 or newer
  • Installed on both sites: the live site (the one you pull from) and your local/staging copy (the one you pull into)
  • The live site must be reachable from your local site over the internet (HTTPS recommended)
  • Optional: WP-CLI for the terminal commands

Install

From WordPress.org (once it's listed): Plugins → Add New, search for LivePull, Install and Activate, on both sites.

From GitHub: download livepull.zip from the latest release (use this file, not GitHub's "Source code" zip). On both sites go to Plugins → Add New → Upload Plugin, choose the zip and click Activate. The GitHub download announces its own updates (Tools → LivePull → Check for updates, or the Plugins screen).

Update both sites so they stay on the same version.

Set up (2 minutes)

  1. On the live site: Tools → LivePull → Generate key, then Copy the Connection code.
  2. On your local site: Tools → LivePull → paste it into Connection code → Save and connect.

The screen now shows how many changes are waiting on live.

Starting point matters. LivePull records changes on live from the moment it's installed there. The easiest setup is:

  • Install on live first, then make your local copy (Local, WP Migrate, All-in-One, …) – or use Copy everything from live (below). LivePull detects that the database is a fresh copy and pulls only what changes after that.
  • Already had a local copy before installing? Do your first pull with More options → Pull all content from live (or catch up from the date you made the copy).

Everyday use

On your local site, Tools → LivePull:

Preview changes Shows what would be created, updated or deleted, and any conflicts. Changes nothing.
Pull changes Backs up this site, then pulls. Progress is shown; large pulls run in batches and can be cancelled and resumed.
Conflicts Items changed on both sides since the last pull. Choose Use live version or Keep mine.
Your local changes Everything you've edited locally since it was last pulled.
Undo a pull or copy Restore the backup taken before any pull or copy.

What gets pulled

Every pull Only with Copy everything from live Never
Posts, pages, custom post types (incl. WooCommerce products) Theme, Customizer and page-builder theme options WooCommerce orders
Media library + files (all sizes) Divi Theme Builder & Library, Elementor templates Logged-in sessions
Categories, tags, custom taxonomies Widgets, forms and other plugin settings Theme and plugin files (keep those in Git)
Custom fields (ACF etc.) and page-builder content Users
Menus and menu locations
Site title, tagline, homepage, posts page, sticky posts, site icon, logo

IDs that point at other content are re-pointed to the matching local items – featured images, galleries, ACF image/relationship/taxonomy fields, Gutenberg blocks, [gallery], Divi galleries, WooCommerce galleries/upsells, Elementor data, menu items, homepage setting. Live URLs are rewritten to your local URL.

If a live item isn't linked to anything locally yet, LivePull looks for the same thing (same post type + slug, same media file, same category slug) and links them instead of creating a duplicate.

Copy everything from live

Tools → LivePull → Copy everything from live replaces the local database with a copy of live and downloads missing or changed files from live's uploads folder.

  • Off by default on live, because it shares the whole database: on live, Tools → LivePull → Let other sites pull from this one → Allow for 1 hour (or Always allow).
  • Your local database is fully backed up first; everything loads into temporary tables and is switched in at the very end, so Cancel leaves your site untouched.
  • URLs and server paths are rewritten, including inside serialized and JSON data; a different table prefix is handled; a different WordPress version is reconciled automatically.
  • Kept from your local site: its URL, its LivePull connection, and "Discourage search engines".
  • Afterwards, log in with your live username and password.

Terminal (WP-CLI)

Run in your local site's folder.

wp livepull status                     # connection + what's waiting
wp livepull pull --dry-run             # preview
wp livepull pull                       # pull (backs up first)
wp livepull pull --since=2026-01-01    # catch up on everything changed since a date
wp livepull conflicts                  # list conflicts
wp livepull take <id> [--term]         # use live's version
wp livepull keep <id> [--term]         # keep yours
wp livepull local-changes              # what you've changed locally
wp livepull clone                      # copy everything from live
wp livepull backups                    # list backups
wp livepull restore [<file>]           # undo
wp livepull connect <connection-code>  # connect without the admin screen
wp livepull key                        # (on live) show the connection code

Security

  • The key only allows reading from live. It's compared in constant time and must be 32+ characters. Treat the connection code like a password.
  • Use https:// for the live site; LivePull warns if the key would travel over plain HTTP to a public host.
  • Copy everything is opt-in and can be time-limited; logged-in sessions are never copied.
  • Backups are kept outside the public web folder when the server allows (one folder per site), otherwise in wp-content/livepull-backups with deny rules and unguessable file names.
  • Files from live are only written inside uploads and never as executable or server-config files (.php, .phar, .htaccess, .user.ini…). Media is only downloaded from the live site or public addresses – never private, internal or cloud-metadata addresses.
  • Updates are only installed from this GitHub repository over HTTPS.
  • Deleting the plugin removes its settings, log, ID tags and backups.

Found a vulnerability? Please report it privately – see SECURITY.md.

Configuration

Everything works without configuration. Optional wp-config.php constants:

define( 'LIVEPULL_REMOTE', 'https://live.example' );          // instead of the connection screen
define( 'LIVEPULL_SECRET', '…' );                              // same key on both sites, instead of the screen
define( 'LIVEPULL_REMOTE_BASIC_AUTH', 'user:pass' );           // live/staging behind HTTP basic auth
define( 'LIVEPULL_SSL_VERIFY', false );                        // staging with a self-signed certificate
define( 'LIVEPULL_PAGE_SIZE', 20 );                            // smaller batches for huge page-builder pages
define( 'LIVEPULL_PULL_MENUS', false );                        // don't pull menus
define( 'LIVEPULL_PULL_OPTIONS', 'option_a,option_b' );        // pull extra options
define( 'LIVEPULL_EXCLUDE_POST_TYPES', 'my_cpt' );             // never pull these post types
define( 'LIVEPULL_EXCLUDE_TAXONOMIES', 'my_tax' );
define( 'LIVEPULL_DEFAULT_AUTHOR', 'alex' );                   // fallback author on local
define( 'LIVEPULL_BACKUP_DIR', '/absolute/path' );             // where backups go
define( 'LIVEPULL_ALLOW_FULL_COPY', true );                    // (live) allow Copy everything permanently
define( 'LIVEPULL_LOG_DAYS', 180 );                            // (live) days of change history to keep
define( 'LIVEPULL_AUTO_UPDATE', true );                        // install updates automatically
define( 'LIVEPULL_DISABLE_UPDATER', true );                    // never check GitHub for updates

Extending

If a theme or plugin stores a post/image ID somewhere LivePull doesn't know about, register it so it's re-pointed:

add_filter( 'livepull_meta_ref_keys', function ( $keys, $meta, $type ) {
    if ( 'post' === $type && isset( $meta['hero_image_id'] ) ) {
        $keys['hero_image_id'] = 'post';
    }
    return $keys;
}, 10, 3 );

Other filters: livepull_ignored_meta_patterns (plugin cache fields that shouldn't count as edits), livepull_walk_content (custom shortcodes), livepull_content_meta_keys (builder data), livepull_block_id_attributes, livepull_excluded_post_types, livepull_excluded_taxonomies, livepull_ignored_meta_keys, livepull_pulled_options, livepull_option_refs, livepull_backup_tables, livepull_full_copy_skip_tables, livepull_full_copy_skip_dirs. Actions: livepull_after_pull, livepull_imported_post, livepull_imported_term.

Tested with

Every release is checked by an end-to-end test suite that builds a real live site and a local site (with different IDs and table prefixes), pulls content across, edits it on live, pulls again and runs Copy everything. It currently covers:

Area Tested with
Editors / page builders Gutenberg core blocks, Elementor, Beaver Builder, SiteOrigin Page Builder, Spectra, Kadence Blocks, GenerateBlocks, Divi 4 (with Divi 4.27.9 installed) and Divi 5 content*
Shop WooCommerce simple and variable products, galleries, upsells, attributes
Fields / SEO / languages ACF (image, relationship, taxonomy fields), Yoast SEO, Polylang
Site structure Menus, menu locations, homepage and posts page, site title, logo, icon
Safety Conflicts (edited on both sides), deletions, undo, Copy everything

* Divi is a paid theme, so it isn't in the repo. Without it the suite checks Divi's saved content arrives intact; add LIVEPULL_TEST_THEME=/path/to/Divi.zip to also check pages display, Theme Builder and Theme Options. Divi 5 pages are checked for content only. Bricks, Oxygen, WPBakery and Brizy data is handled the same way but not yet covered by tests.

The suite runs automatically on GitHub on every change, on PHP 7.4, 8.0, 8.1, 8.2, 8.3 and 8.4, together with WordPress.org's Plugin Check.

Big sites. tests/perf.sh builds a live site with 10,000 posts, 1,500 images and 300 categories. Latest results:

Time Peak memory
First pull (11,800 items, 1,500 image files) 3 min 151 MB
Next pull (100 edits, 20 new, 10 deleted), including the backup 3 s 96 MB
Copy everything (89,000 database rows) 5 s 96 MB

To run the tests yourself (needs PHP, MySQL/MariaDB and WP-CLI; put plugin zips in a folder):

LIVEPULL_TEST_PLUGINS=~/plugin-zips DB_USER=root DB_PASS=secret tests/run.sh
tests/run.sh elementor woocommerce   # just some scenarios
tests/perf.sh                        # big-site test

Limitations

  • One direction. LivePull pulls live → local. Pushing local changes up to live isn't supported (yet) – deploy those your usual way.
  • Not supported yet: multisite, WPML (Polylang content works as normal posts/terms), comments/reviews, data in plugin-specific tables during normal pulls (e.g. Gravity Forms entries – use Copy everything).
  • Conflicts are per item (a whole post or term), not per field.
  • Must-use-plugin installs work but can't update themselves.

FAQ / troubleshooting

"Nothing to pull" but I changed something on live. On live, Tools → LivePull → Let other sites pull from this one → Recent changes recorded on this site. If your edit isn't listed, it's a kind of change normal pulls don't track (see the table above) – use Copy everything. If it is listed, check both sites run the same LivePull version.

"Invalid sync key". Copy the connection code from live again.

"The live site returned a web page instead of data". A page cache or firewall on live is answering instead of WordPress. Exclude /wp-json/ and URLs containing rest_route= from caching (host cache, cache plugin, Cloudflare rules). Quick check: open https://your-live-site/wp-json/livepull/v1/status – you should see "Invalid sync key.", which means LivePull is running and protected.

"Another pull is already running". If nothing is running (the tab was closed mid-pull), click Unlock and pull again. It also unlocks itself after 15 minutes.

Duplicate pages after a pull. Use Undo a pull or copy to restore the backup from before that pull, update to the latest version (it matches existing content), and pull again.

Contributing

Bug reports and pull requests are welcome – see CONTRIBUTING.md. Please include your WordPress, PHP and LivePull versions, and what you expected vs what happened.

Licence

GPL-2.0-or-later – see LICENSE. Made by Alex McIver / Alex M Web Design. LivePull is provided as-is, without warranty; always keep backups.