Skip to main content

Multisite Compatibility

Benecaster works on WordPress multisite installations with one important limitation: it must be activated per-subsite. Network-wide activation is not supported.

Per-Subsite Activation

On a WordPress multisite network, activate Benecaster from each subsite’s Plugins screen individually — not from the network admin. Each subsite runs its own independent Benecaster installation with its own settings, shows, subscribers, and license.

This is the intended and fully supported way to run Benecaster on multisite. Every subsite behaves exactly as it would as a standalone WordPress install.

Network-Wide Activation Is Not Supported

If you attempt to network-activate Benecaster from the network admin, the plugin will show an admin notice and decline to activate. Network-wide activation does not set up the database tables Benecaster needs on each subsite, so activating this way would result in errors on every subsite in the network.

Activate on each subsite individually instead.

Licenses on Multisite

Each subsite that runs Benecaster requires its own license activation. Your license plan determines how many sites you can activate:

Plan Activations
Launch, Starter, Growth, Pro 1 site
Multi-Show 3 sites
Studio Unlimited

A multisite subsite counts as one activation — the same as a standalone WordPress install. If you’re running Benecaster on three subsites, you need a Multi-Show or Studio license.

To activate Benecaster on a subsite, go to Benecaster → License on that subsite and enter your license key. Each subsite activates independently using the same key, subject to your activation limit.

Data Isolation

Each subsite is fully isolated:

  • Shows, episodes, subscribers, and feed tokens on one subsite are not visible to or accessible from any other subsite
  • Settings, tier mappings, and email templates are per-subsite
  • Feed URLs are scoped to the subsite’s domain or path
  • License validation runs independently per subsite

Subdomain and Subdirectory Networks

Benecaster works on both subdomain networks (show1.network.com, show2.network.com) and subdirectory networks (network.com/show1/, network.com/show2/). Feed URLs follow the subsite’s URL structure automatically.