Skip to content

WordPress Plugin

Loopress ships as a single WordPress plugin, built in two editions from the same codebase:

  • Loopress Light (on the WordPress.org directory): connects your site to the Loopress CLI. Exposes the REST API that powers lps acf pull/push/list for ACF field groups and lps seo pull/push/list for SEO settings (RankMath or Yoast SEO).
  • Loopress Full (also free, loopress.dev only): everything in Loopress Light, plus code snippet sync, integrates with Code Snippets and WPCode, powers lps snippet pull/push/list, plus form sync with WPForms powering lps form pull/push/list, plus custom REST API routes deployed from version-controlled PHP files with lps api pull/push/list, plus Composer dependency management: search Packagist, install and audit PHP packages from the admin, and sync composer.json/composer.lock with lps composer push/pull.

Loopress Full costs nothing, it is not a paid upgrade. It is not distributed through the WordPress.org directory for two separate reasons, not pricing: directory guidelines forbid a plugin from installing executable PHP code from external registries such as Packagist (Composer dependency management), and separately forbid a plugin whose REST API can deploy arbitrary PHP/JS/CSS into another plugin such as Code Snippets or WPCode for later execution (snippet sync), regardless of the authentication in front of those endpoints. Installing Loopress Full deactivates Loopress Light automatically, since Loopress Full is a full replacement, not an add-on; the two editions never run side by side.

Feature Loopress Light Loopress Full
Distribution WordPress.org directory loopress.dev
Automatic updates ✓ (via WordPress.org) ✓ (via GitHub Releases)
ACF sync (field groups, post types, taxonomies, options pages)
lps acf pull / push / list
SEO sync (RankMath or Yoast SEO: settings, post meta, redirects)
lps seo pull / push / list
Snippet sync (Code Snippets / WPCode)
lps snippet pull / push / list
Form sync (WPForms)
lps form pull / push / list
Custom API routes (deploy REST endpoints from PHP files)
lps api pull / push / list
Single-page apps (ship a built Vue, React or Svelte bundle, mount with a shortcode)
lps app pull / push / list / remove
Plugin and theme lockfile (pin WordPress.org plugins and themes, install via Composer + WPackagist)
lps plugin / lps theme pull / push / add / status
Composer dependency management (Packagist search, install, remove, update)
Security audit (known CVEs, abandoned packages)
Platform diagnostics (PHP version mismatches)
lps composer push / pull
Crash reporting (opt-in, Sentry)
  • ACF sync: pull and push field groups, post types, taxonomies, and options pages as JSON with lps acf pull/push. Requires ACF active on the site, options pages require ACF PRO
  • SEO sync: pull and push settings, post meta, and redirects as JSON with lps seo pull/push, for whichever of RankMath or Yoast SEO is active
  • REST API for the CLI: everything runs over loopress/v1, restricted to the manage_options capability (administrator role)

Everything above, plus:

  • Snippet sync: pull the site’s snippets as files with lps snippet pull, push edits back with lps snippet push, and keep them in Git
  • Works with Code Snippets and WPCode: Loopress Full talks to whichever is active
  • Form sync: pull and push WPForms forms as JSON with lps form pull/push/list
  • Custom API routes: version-control REST API endpoints as plain PHP files with lps api pull/push/list, each file becomes one route
  • Single-page apps: ship a pre-built Vue, React or Svelte bundle to the site with lps app push and mount it in any page with a shortcode
  • Plugin and theme lockfile: pin WordPress.org plugins and themes in loopress.json and install the identical set on every environment with lps plugin push / lps theme push, via Composer and WPackagist
  • Dependency management: search, install, remove and update Composer packages from Packagist, with automatic detection of outdated packages
  • Security audit: surfaces known CVEs and abandoned packages among your installed dependencies
  • Platform diagnostics: catches PHP version mismatches before they cause a broken install
  • CLI sync: powers lps composer push and lps composer pull
  • Crash reporting: opt-in banner to send Loopress’s own errors to Sentry so bugs get fixed faster, no data from your theme, other plugins, or site visitors is included. The Settings tab lets you change your answer anytime, or reset all Loopress settings to default

Loopress Full stores your project’s Composer dependencies in wp-content/loopress/, separate from the plugin itself, so they survive plugin updates.

Plugins listed on the WordPress.org Plugin Directory go through a review by the WordPress.org plugins team before their first release, and every update is scanned afterward. In exchange, a hosted plugin gets:

  • Discoverability: found by searching Plugins → Add New from inside any WordPress admin, no external download needed
  • Automatic updates: WordPress checks WordPress.org for new versions and can update the plugin in place, the same as any other installed plugin
  • A trust signal: install counts, ratings, and a public source history are visible to anyone considering the plugin

The tradeoff is a strict set of guidelines, and Loopress ran into two of them:

  • Rule 8 forbids a plugin from sending or installing executable code from a third-party system, which includes package registries such as Packagist. That is exactly what Loopress Full’s Composer dependency management does, so it cannot be hosted on WordPress.org regardless of implementation quality.
  • Separately, the review team classified snippet sync itself, REST endpoints that let arbitrary PHP/JS/CSS be submitted remotely and stored in another plugin (Code Snippets or WPCode) for later execution, as a remote code-deployment mechanism. This holds regardless of the authentication and capability checks in front of those endpoints: they establish who is allowed to call the endpoint, not whether the code submitted through it is safe. Every submission of Loopress Light that shipped snippet sync was rejected on this basis, and a subsequent appeal was rejected too, explicitly and finally.

Loopress Light no longer ships snippet sync as a result: it now covers only ACF and SEO configuration, plain JSON data with no executable-code angle, and is published on the WordPress.org directory in that form.

This is why the plugin ships as two editions instead of one: Loopress Light is on the WordPress.org directory, installed and updated in place like any other plugin from there. Loopress Full carries both rejected capabilities (Composer and snippet sync), so it is downloaded directly from loopress.dev, but it still updates itself through the normal Plugins page: it checks GitHub Releases for a newer loopress-full.zip and, once found, WordPress downloads and installs it the same way it would a WordPress.org-hosted plugin.

  • WordPress 6.0+
  • PHP 8.2+
  • manage_options capability (administrator role)
  1. In your WordPress admin, go to Plugins → Add New and search for Loopress Light
  2. Click Install Now, then Activate, then find Loopress in the sidebar

Or install it from the WordPress.org page. Either way, updates arrive automatically like any other directory plugin.

  1. Download loopress-full.zip using the button above
  2. In your WordPress admin, go to Plugins → Add New → Upload Plugin
  3. Upload and activate the plugin, then find Loopress in the sidebar

Installing Loopress Full deactivates Loopress Light automatically. From then on, updates show up on Plugins like any other plugin, since Loopress Full checks GitHub Releases for a newer loopress-full.zip and lets WordPress install it in place.

  • Composer (Loopress Full): dependency management, security audit, platform diagnostics
  • API Routes (Loopress Full)