WordPress Multisite

• Introduction
• What a network looks like on Staatic Cloud
• Getting a network
• Working with subsites
• Limits

Introduction

The Staatic plugin works on any WordPress Multisite network. It publishes each site in the network separately, the same way it publishes a single WordPress site. That is not what this page is about.

This page covers WordPress Multisite networks hosted on Staatic Cloud. In that setup, every site in the network is also a site on Staatic Cloud, with its own publishing, destination and credentials.

What a network looks like on Staatic Cloud

A network on Staatic Cloud is always a subdomain network. The primary site and every additional site (a subsite) has its own hostname. Subdirectory networks, where sites share a hostname and differ by path, are not supported.

Each subsite is a separate site in the Staatic portal, with its own publishing, destination, preview, custom domain and API credentials, like any other Staatic Cloud site. Subsites share one WordPress installation: the same plugins, themes and user table, as on any WordPress network.

flowchart TD
    WP[One WordPress installation<br/>plugins, themes, users]
    WP --> P[Primary site<br/>yoursite.wp.onstaatic.com]
    WP --> A[Subsite<br/>yoursite-blog.wp.onstaatic.com]
    WP --> B[Subsite<br/>yoursite-shop.wp.onstaatic.com]
    P --> PS[Staatic site<br/>own destination and domain]
    A --> AS[Staatic site<br/>own destination and domain]
    B --> BS[Staatic site<br/>own destination and domain]

The primary site’s WordPress stays at its usual address, for example yoursite.wp.onstaatic.com. Each subsite gets an address next to it, for example yoursite-blog.wp.onstaatic.com. You use these addresses for WordPress Admin. Visitors see each site’s destination or custom domain.

Each subsite counts as an additional site on your account.

Getting a network

Networks are set up on request. Contact support and we will convert an existing Staatic Cloud site into the primary site of a new network, or import an existing WordPress Multisite network for you.

A subsite can also publish somewhere other than Staatic Cloud, such as Netlify or Amazon S3. Ask for this when you request the network.

Importing an existing network is done for you. We move the network’s database and files into your instance and connect each site. The self-service import described in Importing a WordPress Site only accepts single-site backups.

Domain mapping on the WordPress side (a sunrise.php setup) is not supported. Use a custom domain on each subsite instead.

Working with subsites

Because each subsite has its own address, a WordPress login does not carry over between subsites. You may have to sign in again when you switch. The Sites screen in the network admin lists all of them.

Publishing is per subsite. Each one has its own Publish button, its own destination and its own scheduled publications.

Backups cover the whole network. A backup includes every subsite’s files and database. You cannot back up or restore a single subsite on its own. See WordPress Backups for the schedule and the restore procedure.

Removing a subsite is permanent. The subsite’s WordPress content and its Staatic site are deleted together. Take a backup first if you may need the content later.

Limits

• The WordPress import flow does not accept multisite backups. See Importing a WordPress Site for the supported formats.
• Previews are only available for subsites that publish to Staatic Cloud. A subsite that publishes elsewhere has no preview.