Use vendor updates instead of GPL Times for a specific plugin

By default, Manage GPL pulls updates for premium plugins and themes from the GPL Times catalog. If you've licensed a specific plugin directly from its vendor — and the vendor publishes updates through WordPress's normal update channel — you can tell us to step aside on that one slug and let the vendor's feed flow through instead.

Common case: you bought Gravity Forms with an active license. Your WordPress install talks to gravityforms.com on its own update-check schedule and learns about new versions there. With this opt-out enabled, Manage GPL uses Gravity Forms' update URL when you click Update — not our catalog's URL.

Per-site or globally

You can opt out two ways:

• Per-site — open the site's Plugins or Themes tab. Find the plugin row. Look for the small swap-arrows button (only shown for items in our GPL Times catalog). Click it and confirm. Affects this one site only.
• Globally (all your sites) — open Plugins in the main left sidebar (the cross-site view). Find the slug. Click the same swap-arrows button on its row. Affects every site you own. Per-site opt-outs you've already set are not changed.

The first time you click the toggle, you'll see a confirmation dialog explaining what will happen. Tick Don't ask me again for this action if you're going to flip a bunch of these in one sitting; future clicks will skip the confirmation until you clear your browser storage.

What changes when you opt out

For the affected slug:

• The category badge moves from "Premium" to "Other" in the plugin/theme list.
• The Update button uses the vendor's own download URL (the one your WP site picked up from the vendor's update channel) instead of our GPL Times URL.
• The can_update plan paywall doesn't apply — opted-out items aren't classified as premium for our gating purposes. Even Free-plan accounts can run these updates because we're acting as a passthrough, not a catalog.
• If the site doesn't have an active vendor license (no package_url reported by WP's update transient), the Update button simply disappears for that item — there's no update path we can use.

What does NOT change

• The plugin file on disk is the same. Just the future-update source changes.
• Your other plugins are unaffected. The opt-out is per-slug.
• Per-site overrides aren't created when you toggle from the global view, and vice versa. They're independent settings.

Reverting back to GPL Times

Click the same swap-arrows button again. The confirmation dialog asks you to confirm the reverse direction ("Switch back to GPL Times?"). On confirm, the slug returns to Premium classification and updates flow through our catalog again.

When you'd actually want this

• You bought the vendor license and want to keep their support channel open. Some vendors invalidate support if you've also installed a non-licensed copy from a redistributor.
• The vendor pushes pre-release / beta channels through their own feed and you want those, not the stable version we mirror.
• The vendor is faster to ship security patches than we are to refresh our catalog.

When you'd want to leave it on (default)

• You don't have a license — GPL Times is your only update path.
• You manage the site for a client whose vendor licenses come and go; the GPL Times path doesn't depend on a license being active.