Multisite Support

Short answer: Super Speedy Coming Soon is built and tested for standard single-site WordPress. It is not officially tested on WordPress Multisite. It may well work per-site, but treat multisite as unsupported until you’ve verified it on a staging network. This article explains what to watch for.

What the plugin does that matters on a network

• Database table. On activation the plugin creates a sscs_signups table using the current site’s table prefix ($wpdb->prefix). It is a per-site table.
• Settings & data. Settings are stored with get_option()/update_option(), which are per-site on multisite. Each subsite has its own API key, spam settings, and signups — there is no network-wide configuration.
• No network-aware code. There is no special handling for network activation, new-site creation, or shared/global tables.

The main caveat: network activation and the table

WordPress runs a plugin’s activation hook once on network activation (for the main site), not once per subsite. Because the signups table is created in that activation hook, network-activating may not create the table on every subsite — so signups on a subsite without the table would fail to record locally.

Recommendation: if you use the plugin on multisite, activate it per individual site (Site → Plugins → Activate) rather than network-activating, so each site runs the activation hook and gets its own sscs_signups table. New subsites created after activation would each need the plugin activated on them too.

Practical guidance

• Use per-site activation, not network activation.
• Configure each site’s settings (API key, providers, spam protection) separately — nothing is shared across the network.
• After adding a new subsite, activate the plugin on it so its table is created.
• If you must network-activate, verify the {prefix}sscs_signups table exists on each subsite (it can be created by deactivating/reactivating on that site, which re-runs the activation hook).
• Test the full signup flow on a staging network before relying on it in production.

Planned enhancement

Proper multisite support — creating the per-site table on network activation and on new-site creation (e.g. via the wp_initialize_site hook), and a clear single-site-vs-network data model — is a potential future enhancement. If multisite support matters to your deployment, let us know so it can be prioritised.

Related

• Architecture — how and when the signups table is created (Developers).
• Viewing & Exporting Your Signups — the per-site table you’d verify exists.