Title: Loopress Light Author: jeansmaug Published: 6 de setembre de 2026 Last modified: 12 d'octubre de 2026 --- Cerca extensions ![](https://ps.w.org/loopress-light/assets/icon.svg?rev=3735644) # Loopress Light Per [jeansmaug](https://profiles.wordpress.org/jeansmaug/) [Baixa](https://downloads.wordpress.org/plugin/loopress-light.2026.15.0.zip) * [Detalls](https://ca.wordpress.org/plugins/loopress-light/#description) * [Ressenyes](https://ca.wordpress.org/plugins/loopress-light/#reviews) * [Instal·lació](https://ca.wordpress.org/plugins/loopress-light/#installation) * [Desenvolupament](https://ca.wordpress.org/plugins/loopress-light/#developers) [Suport](https://wordpress.org/support/plugin/loopress-light/) ## Descripció Loopress Light connects your WordPress site’s configuration to your development workflow. It reads and writes ACF (Advanced Custom Fields) field groups, post types, taxonomies, and options pages, WPForms forms, navigation menus, custom post types, taxonomies, post meta keys and user roles declared as JSON files, and the WordPress options you choose to track, exposing all of it to the Loopress CLI (`lps`) as JSON so it can live in Git like any other code. Features: * Sync ACF field groups, post types, taxonomies, and options pages: `lps acf pull`/` lps acf push` / `lps acf list` * Sync WPForms forms: `lps form pull` / `lps form push` / `lps form list` * Sync navigation menus and their items: `lps menu pull` / `lps menu push` / `lps menu list` * Declare custom post types as JSON files, like CPT UI but in Git: `lps cpt pull`/` lps cpt push` / `lps cpt list` * Declare taxonomies the same way, attached to your post types (their terms stay content): `lps taxonomy pull` / `lps taxonomy push` / `lps taxonomy list` * Declare the meta keys of each post type (type, default, REST exposure; their values stay content): `lps meta pull` / `lps meta push` / `lps meta list` * Declare custom user roles and their capabilities, identical on every environment( which users have them stays content): `lps role pull` / `lps role push` / `lps role list` * Sync the WordPress options listed in your project (Settings screens, plugin settings):` lps option pull` / `lps option push` / `lps option list` * Keep configuration in Git: history, diffs, code review, rollbacks * Move configuration between environments (local, staging, production) * REST API restricted to administrators, authenticated with WordPress application passwords Need code snippet sync (Code Snippets, WPCode) or Composer dependency management too? [Loopress Full](https://docs.loopress.dev/wordpress-plugin/) is the full edition, free of charge, downloaded directly from loopress.dev instead of wordpress.org ( see FAQ for why). ## Instal·lació 1. Upload the plugin folder to `/wp-content/plugins/`. 2. Activate the plugin through the **Plugins** screen in WordPress. 3. Install and activate ACF and/or WPForms, if you have not already. 4. Open the **Loopress** menu item in the admin sidebar and follow the CLI pairing instructions. ## PMF ### What is the difference between Loopress Light and Loopress Full? Loopress Light (this plugin) syncs ACF, WPForms forms, menus, custom post types, taxonomies, post meta keys, user roles, and tracked options. Loopress Full adds code snippet sync (Code Snippets, WPCode), Composer dependency management, a security audit, and platform diagnostics. Loopress Full costs nothing, it is not a paid upgrade: it is downloaded directly from loopress.dev instead of wordpress.org. Directory guidelines do not allow a plugin that installs executable code from external registries such as Packagist, and separately do not allow a plugin whose REST API can deploy arbitrary PHP/JS/CSS into another plugin such as Code Snippets or WPCode; both capabilities live in Loopress Full instead, not because of pricing. Installing Loopress Full deactivates Loopress Light automatically: it is a full replacement, not an add-on. See [the documentation](https://docs.loopress.dev/wordpress-plugin/) for the full feature comparison and download link. ### Which ACF versions are supported? Advanced Custom Fields (options pages require ACF PRO). You keep using its interface as usual. SEO plugin settings (Yoast, Rank Math) are a single option each, tracked like any other option. ### Does the plugin execute code by itself? No. Loopress Light only reads and writes ACF field group definitions, form definitions, menus, custom post type, taxonomy, post meta and role arguments, and options through the WordPress and plugin APIs, exactly as when you edit them by hand in their interface. It never accepts or stores arbitrary code: script tags, inline event handlers, and` javascript:` URLs are stripped from pushed ACF and form values, and a custom post type, taxonomy, post meta or role file only holds `register_post_type()`, `register_taxonomy()` or `register_post_meta()` settings or a role’s name and capabilities, any argument that would run code (a callback, a REST controller class) is refused. ### Which options can be synced? Only the options your project lists. By default, options whose name looks like a stored secret (API keys, tokens, passwords) are refused on read. This is best-effort matching on names and can miss some secrets (`stripe_sk`, for example), so do not track an option that holds a credential: its value would end up in the JSON you keep in Git. Options that change who can access the site or where it loads from (` siteurl`, `home`, `default_role`, `users_can_register`, `cron`, Loopress’s own settings) are refused on write by default. Developers can change both lists with the `loopress_option_readable` and `loopress_option_writable` filters. ### Who can access the REST API? Only authenticated users with the `manage_options` capability (administrators). The CLI authenticates with a WordPress application password that you can revoke at any time. ### Do I need the CLI? The plugin is the site-side companion of the Loopress CLI (`lps`, installable from npm). Without the CLI, it does nothing beyond showing its admin page. ## Ressenyes No hi ha ressenyes per a aquesta extensió. ## Col·laboradors i desenvolupadors «Loopress Light» és programari de codi obert. La següent gent ha col·laborat en aquesta extensió. Col·laboradors * [ jeansmaug ](https://profiles.wordpress.org/jeansmaug/) [Traduïu «Loopress Light» a la vostra llengua.](https://translate.wordpress.org/projects/wp-plugins/loopress-light) ### Interessats en el desenvolupament? [Navegueu pel codi](https://plugins.trac.wordpress.org/browser/loopress-light/), baixeu-vos el [repositori SVN](https://plugins.svn.wordpress.org/loopress-light/), o subscriviu-vos al [registre de desenvolupament](https://plugins.trac.wordpress.org/log/loopress-light/) per [fisl de subscripció RSS](https://plugins.trac.wordpress.org/log/loopress-light/?limit=100&mode=stop_on_copy&format=rss). ## Registre de canvis #### 2026.7.6 * The plugin now builds two editions from the same codebase. Loopress Light (this plugin) keeps snippet synchronization; Composer dependency management moved to the separate Loopress Full plugin, distributed from loopress.dev. #### 2026.7.5 * Fixed all issues reported by the WordPress Plugin Check tool: escaped dynamic exception messages, added the missing direct access guard, and bumped «Tested up to» to 7.0. #### 2026.7.4 * Fixed `lps snippet pull` failing to delete a locally removed snippet, and excluded trashed snippets from sync. #### 2026.7.3 * Plugin management now relies entirely on WordPress core’s REST API instead of a custom endpoint. #### 2026.7.2 * Added a diagnostics tab to the admin UI. * Unified the snippet REST route. * Switched the integrity hash from md5 to sha256. #### 2026.7.1 * Improved compatibility of the WPCode sidecar file with the WPCode API. #### 2026.7.0 * Initial release: basic UI for Composer dependency installation, and REST endpoints for the Loopress CLI. ## Meta * Versió **2026.15.0** * Darrera actualització **fa 2 setmanes** * Instal·lacions actives **Menys de 10** * Versió del WordPress ** 6.2 o posterior ** * Provada fins a **7.1.3** * Versió del PHP ** 8.2 o posterior ** * Idioma * [English (US)](https://wordpress.org/plugins/loopress-light/) * Etiquetes * [acf](https://ca.wordpress.org/plugins/tags/acf/)[advanced custom fields](https://ca.wordpress.org/plugins/tags/advanced-custom-fields/) [git](https://ca.wordpress.org/plugins/tags/git/)[menus](https://ca.wordpress.org/plugins/tags/menus/) [sync](https://ca.wordpress.org/plugins/tags/sync/) * [Vista avançada](https://ca.wordpress.org/plugins/loopress-light/advanced/) ## Valoracions Encara no s'ha enviat cap ressenya. [La vostra ressenya](https://wordpress.org/support/plugin/loopress-light/reviews/#new-post) [Visualitza totes les ressenyes](https://wordpress.org/support/plugin/loopress-light/reviews/) ## Col·laboradors * [ jeansmaug ](https://profiles.wordpress.org/jeansmaug/) ## Suport Teniu quelcom a dir? Necessiteu ajuda? [Visualitza els fòrums de suport](https://wordpress.org/support/plugin/loopress-light/)