Multisite
Network-activate, one folder per site, and why bootstrap is not a rebuild.
Tivlo Static Site is network-aware (Network: true). Network-activate
it so every site can generate static HTML without activating the plugin
per site — the same idea as network-activating any other must-have
plugin.
Each site still gets its own snapshots, its own queue, and its own folder. One dentist site cannot overwrite another dentist site. That would be a memorable incident.
Quick start
Network Admin → Plugins → Network Activate Tivlo Static Site.
Network Admin → Settings → Tivlo Static Site.
Click Bootstrap all sites (queue tables, cron, output dirs). Bootstrap is housekeeping. It does not export HTML. Nobody’s About page appears until a rebuild.
Use Full rebuild — all enabled sites, or open each site’s Settings → Tivlo Static Site and rebuild there if you like doing one site at a time.
Per-site behavior
| Concern | Behavior |
|---|---|
| Settings | Stored per blog (wp_X_options) |
| Queue table | {blog_prefix}tivlo_ssg_queue |
| Cron | Scheduled per site |
| Output dir | wp-content/tivlo-static/{site-slug}/ |
| Asset URL | {network_origin}/wp-content/tivlo-static/{site-slug}/ (not under the blog path) |
| Public base URL | Per site |
| Content hooks | Run in the blog where content changed |
Folder slug: Export Folder Slug in site settings, otherwise the
subdirectory path (/tivlo-dental/ → tivlo-dental), subdomain label,
or main for the primary site.
wp-content/tivlo-static/
main/
tivlo-dental/
another-site/Asset URLs look like
https://network.example.com/wp-content/tivlo-static/tivlo-dental/assets/...
— not /tivlo-dental/wp-content/tivlo-static/.... WordPress keeps
wp-content in one place; Tivlo follows that habit.
Network admin
Network Settings → Tivlo Static Site:
| Control | Effect |
|---|---|
| Automatically bootstrap Tivlo when a new site is created | New sites get table, cron, folder |
| Allow site admins to change per-site Tivlo settings | Off → only network admins can save site settings |
| When bootstrapping, write default settings if none exist | Seed defaults |
| Bootstrap all sites | One-time setup on every site. Does not export HTML |
| Full rebuild — all enabled sites | Queues URLs; does not clear existing files |
| Process all site queues now | Drain every site’s queue |
| Invalidate cache — all sites | Bump cache validators network-wide |
| Sites table | ID, site, slug, enabled, static files, queue, output, link to site settings |
Clear existing files and single-site rebuilds are site admin only. The network screen will not vacuum a subsite’s folder for you. That is on purpose.
Site overrides locked
If the network disables site overrides, rebuild and queue actions
remain available to site admins with manage_options. Saves show a
denial banner. You can still reprint pages; you just cannot rewrite
the recipe.
Site admin
Each site still has Settings → Tivlo Static Site for clear/rebuild, Public Base URL, CSS options, and CDN. Use each site’s Public Base URL when that site’s HTML is hosted on a different domain than the network.
How is this guide?