B Blengi docs
/

WordPress & WooCommerce

Plugin distribution

By default — with the Download URL left blank — every workspace's /app/integrations WordPress card shows a Download plugin button that streams your own branded plugin zip straight to the customer. Nothing to host: the server serves the latest build (and builds one on the first request if none exists yet). This is the recommended setup.

The two admin-editable knobs below only matter when you want to override that: point customers at an external mirror (a WordPress.org listing, an S3 bucket, a corporate file share) instead of the direct download, and/or replace the help blurb under the button.

Where to set them

Super-admin only. Sign in as a platform admin and visit /settings/system#integrations (the "Integrations" tab inside System settings — the WordPress plugin block lives there alongside the workspace-facing integration toggles). Two fields:

  • Download URL — absolute https:// link to the .zip (or to your WP.org listing). Becomes a "Download plugin" link rendered next to the existing "WordPress install & connect" doc link. Validated as a URL, max 500 chars.
  • Help text — short blurb that replaces the default "Need the plugin? Download it from your CodeCanyon receipt…" copy. Max 2000 chars. Leave blank to fall back to the default.

What customers see

On /app/integrations the WordPress card footer reads: 

{help_text} Download plugin · WordPress install & connect

When both fields are blank the page falls back to the original "Need the plugin? Download it from your CodeCanyon receipt, or read the setup guide:" copy. The "Download plugin" anchor is omitted entirely so we don't render a dead link.

Why customize this

  • You're hosting the plugin on WordPress.org and want customers landing through their wp-admin's plugin search instead of CodeCanyon.
  • You're running a Pitchbar fork under your own brand ("Replibar", "Whispbar", "Dirty Good") and the CodeCanyon reference is out of place.
  • You run a paid SaaS license + a separate plugin distribution channel (Gumroad, Lemon Squeezy, your own storefront) and want the workspace integrations page to deep-link there.

Security notes

  • The "Download URL" is rendered as a plain <a href> with target="_blank" + rel="noopener noreferrer". Validation rejects non-URL strings, but the link still goes wherever you point it — only super-admins can change this field.
  • Help text is rendered as plain text (no HTML escaping bypass). Putting markdown or HTML in there won't render — it shows as literal characters.

Build a white-labelled plugin zip

Super-admins build the actual .zip at /admin/integrations/wordpress → Build latest, then Download. The build is automatically branded with this install's identity — it reads your brand name from Settings → Branding (the site title) and your brand URL, then stamps them onto the plugin so the customer's WordPress admin shows your brand, not "Pitchbar":

  • The Plugin Name in the WordPress Plugins list, the Author, the description, and the author/plugin URLs in the plugin header.
  • The Settings menu label, the settings page heading, and every on-screen label, notice, and connection-test message.

Only display text is rebranded. Internal code identifiers (the PHP namespace, the pitchbar text domain, option keys, and script handles) are deliberately left unchanged so the plugin keeps working and upgrades cleanly. The install folder stays wp-content/plugins/pitchbar/. The downloaded file is named after your brand too — e.g. blengi-2.0.5.zip instead of pitchbar-2.0.5.zip.

You can grab the branded zip in three places, all serving the same build: the Download plugin button in Settings → System → WordPress plugin distribution, the Build / Download page at /admin/integrations/wordpress, and — for customers — the Download plugin button on their own /app/integrations WordPress card. The customer button always serves this direct branded download; the legacy "Download URL" field no longer changes it.

From the CLI you can pass an explicit brand instead of the install default: 

php artisan pitchbar:build-wp-plugin                     # brands from Settings → Branding when built via the UI
php artisan pitchbar:build-wp-plugin --brand="Blengi" \
    --brand-url="https://blengi.com" --author="Blengi"  # explicit white-label

This is independent of the Download URL / Help text knobs above — those point customers at where to get the zip; the branded build controls what the zip says.

Related