Builds
Full Rebuild, the queue, incremental updates, and how to check that HTML is real.
Exports run from Settings → Tivlo Static Site → Build Console. Tivlo
puts public URLs on a to-do list, visits each one the way a guest would
(X-Tivlo-SSG), and writes index.html files under
wp-content/tivlo-static/. WP-Cron processes the {prefix}tivlo_ssg_queue
table about every minute. On a quiet local site, click Process Queue
Now instead of waiting for a visitor to wake cron up.
Saving Plugin Settings or CDN settings does not rewrite files already on disk. After a settings change, run Full Rebuild (and clear existing files first if you narrowed export scope).
Build Console
Status cards, Full Rebuild, queue, logs, CSV, invalidate, and clear.
Incremental Rebuilds
Which edits queue which URLs, including related archives.
Day-to-Day Workflow
Publish as usual; drain the queue when you need the file right now.
Verify Your Export
Logged-out X-Tivlo-Static: hit and the matching file on disk.
When to Full Rebuild (and when not to)
| Situation | What to run |
|---|---|
| First setup, or no files on disk | Full Rebuild (optional clear first) |
| Publish or update a post/page | Incremental queue — no Full Rebuild. Go make tea. |
| Theme, Customizer, or menu change | Soft full rebuild is queued automatically |
| Export scope, Public Base URL, or CDN change | Save, then Full Rebuild |
| Queue stuck or HTML looks wrong | Troubleshooting, then Full Rebuild |
Pretty permalinks
Plain permalinks can only export the home page. Fix Settings → Permalinks before you rebuild, or you will rebuild a very small universe.
How is this guide?