Integration

WordPress.

The most polished install. The plugin loads the runtime, exposes an “Edit with Glopzi” button on the admin bar, keeps a local cache of your bundle, and handles updates. Works on every major builder.

What the plugin does

The Glopzi WordPress plugin is a thin wrapper that:

  • Validates your license against our servers and stores the credentials securely.
  • Loads the Glopzi runtime on every front-end page, and your compiled animation bundle from our CDN (with a same-origin fallback cached on your server).
  • Adds an Edit with Glopzi button to the WordPress admin bar so admins can open the editor on any page in one click.
  • Hosts the editor inside a wp-admin page, so you never leave WordPress while you work.
  • Keeps itself updated through WordPress’s standard update mechanism.

Compatibility

  • WordPress: 6.0 or newer.
  • PHP: 7.4 or newer (8.x recommended).
  • Builders: Elementor, Bricks, Divi, Gutenberg, Beaver Builder. Animations target CSS selectors, so any builder that ships HTML works.
  • Themes: any. Glopzi doesn’t modify your theme.
  • Multisite: each site has its own license activation. Network-wide license sharing is on the roadmap.

Install

The full install walkthrough lives in Quickstart: WordPress. Short version:

  • Download the plugin ZIP from your dashboard.
  • Upload via WordPress Admin → Plugins → Add New → Upload Plugin.
  • Activate.
  • Open Glopzi Studio in the admin sidebar and paste your license key (GLPZ-XXXXX-XXXXX-XXXXX-XXXXX).
  • Done. The Edit button is now on the admin bar.

Sanesecurity false positive

A few security plugins flag minified animation libraries as suspicious. If your upload is rejected with a generic “file blocked” error, upload the unzipped folder via FTP into wp-content/plugins/ instead.

Builder-specific notes

  • Elementor. Class names are generated per element (.elementor-element-abc123). Use stable targeting for animations that must survive a section duplicate.
  • Bricks. Uses #brxe-xxx IDs on each element. Same advice: stabilize when needed.
  • Divi. Module classes follow .et_pb_module-XX patterns. The picker handles them; aliases make the sidebar readable.
  • Gutenberg. Block class names are stable across saves (.wp-block-heading). Less need for stabilization than the page builders.
  • Beaver Builder. Module classes are descriptive and reasonably stable. Same as Gutenberg.

Auto-updates

The plugin uses WordPress’s standard update channel. New releases appear in Plugins → Installed Plugins just like any other plugin update. We never push updates automatically without your consent; you click Update like you would for anything else.

Critical bug fixes are flagged in the changelog alongside the version. Major releases ship with release notes you can read before updating.

Next steps