Working with Multisite

Simply Static ships with a dedicated multisite integration to make working within a network as smooth as possible.

Configure your subsite

Simply Static is configured per subsite, we do not provide settings on the network level.

That's because the settings are unique per website (think of deployment, forms, and even search results), so it wouldn't make sense to configure these things on the network level.

The configuration is the same as with a single WordPress installation.

There is only a tiny difference: we implemented an import and export tool to copy settings between subsites, which speeds up the configuration process.

To make subsites available in the import settings, configure the subsite first and save the settings.

Once completed, the site will be available for import, allowing you to speed up the configuration of the next subsite.

Run static exports

While you can run static exports from within the subsite (as with any WordPress installation), we recommend using the network-level integration to manage exports in a central place.

Go to your network settings and visit the Simply Static settings page:

You will see a list of all your subsites, with the option to start an export or access the settings.

Manage Exports:

Simply Static contains a queue system built explicitly for multisite networks, which automatically schedules exports sequentially if you try to run multiple ones at the same time.

You can see the current status of each export on the network settings (Idle, Queued, Running).

Parallelisation

You can also disable our queue system to allow multiple exports to run at the same time by using the following filter:

add_filter( 'ss_multisite_queue_enabled', '__return_false' );

With this in place, we will run exports in parallel, allowing you to run multiple exports of different subsites simultaneously.

This does require some fine-tuning of your server environment, as the number of jobs that can be run in parallel depends on the number of pm_children (child processes handled by your webserver) and is usually limited by the number of PHP workers available in your setup.

This is also not something we will help configure in our standard plugin support.