compare · the built-in option
Loopress vs ACF Local JSON.
ACF can already save field groups as JSON in your theme. If field groups are all you need in Git, that may be enough. Loopress starts where it stops.
| ACF Local JSON | Loopress | |
|---|---|---|
| What's in Git | ACF field groups, post types, taxonomies, options pages | The same, plus menus, options, theme styles, and code with Full |
| Getting it live | Deploy the theme, then click Sync in each site's admin | lps acf push --env production |
| Changes made in wp-admin | Written to the JSON file of the site they were made on | lps acf pull brings them back from any environment |
| Undo | Revert the commit and sync again | lps acf rollback, to the snapshot taken before the push |
Same task, both ways
Ship a field group change to production.
ACF Local JSON
- Commit acf-json/ in the theme
- Deploy the theme to production
- Open Field Groups in wp-admin
- Click Sync on the changed group
Loopress
$ lps acf diff --env production $ lps acf push --env production
Pick ACF Local JSON when
ACF is the only configuration you care about, you already deploy the theme from Git, and a manual sync step on each site doesn't bother you.
Pick Loopress when
Field groups are one piece among menus and options, or you want to see the diff and ship from the terminal or CI instead of clicking Sync.
All comparisons · WP Staging and Duplicator · WP Migrate · Roots Bedrock · VersionPress