Build Console
Full rebuild, queue, logs, CSV, cache invalidate, and the big clear button.
Open Settings → Tivlo Static Site → Build Console. Keep this tab
open during a run. It is the only place that will admit, in real time,
“still working on /about/.”
[IMAGE: build-console]
Screenshot of the Build Console: Build Actions, Live Publishing Status cards, progress meter, log panel, and Active Public Access URLs. Caption: “Build Console — status, actions, progress, and logs.”
Pretty permalinks
A red warning appears on every Tivlo SSG tab while WordPress is on Plain permalinks. Only the home page can export. Fix Settings → Permalinks, then Full Rebuild. The red bar is not decoration.
Status cards (Live Publishing Status)
| Card | Meaning |
|---|---|
| Static Files Generated | Count of HTML files, with Optimized / Unoptimized from your HTML setting |
| Queue Pending Tasks | Jobs waiting in {prefix}tivlo_ssg_queue. Zero is the happy number. |
| Direct Static Delivery | Active when both generation and Serve static HTML directly are on |
| Output Directory Path | Absolute path (copyable) under wp-content/tivlo-static/ |
| Last Export Timestamp | Last successful rebuild time, or Never (hello, first run) |
Build actions
| Action | When to use it |
|---|---|
| Full Rebuild | First setup, structural change, CDN/settings change, recovery |
| Clear existing static files before running a full rebuild | Toggle — wipe HTML first, then enqueue everything. Use when you shrunk the guest list. |
| Process Queue Now | Local/dev, or “I published two minutes ago and I am impatient” |
| Invalidate Cache | Bump ETags and briefly force browsers/proxies to recheck (also runs when an export finishes) |
| Clear Static Files | Delete generated HTML and the pending queue. Visitors get live WordPress until you rebuild. The panic button that is actually safe. |
Actions locked during export
While an export is in progress, buttons are disabled. That is Tivlo stopping you from starting a second rebuild on top of the first. Site admin ticks serialize one URL at a time and suppress overlapping cron so WordPress does not deadlock talking to itself.
Live progress (Pre-Serialization Cache)
During a run you see:
- Status: Idle, Export in progress, Export complete, or failed
- Progress bar and counts: completed / total · ok · failed · pending
- Current URL being fetched
If it looks stuck, wait a beat — a slow page can sit on one URL for the HTTP timeout. Then check Recent Failures.
Logs and failures
Export Execution Logs tails the on-disk log (path shown under the panel). Clear Log Console only clears the on-screen tail, not the file. Feel free to clear the screen; it is housekeeping, not amnesia.
Recent Failures lists URLs and last_error when jobs exhaust
retries (up to 3 attempts). The list is scrollable when it grows.
Active Public Access URLs
After a build, this list shows exported URLs. Export CSV downloads them. Copy buttons sit on each row. An empty list means no files yet — run a Full Rebuild. It is not hiding them out of spite.
Loopback timeouts (cURL 28)
Export uses wp_remote_get() back to the same site. If admin AJAX
ticks and spawn_cron() both process the queue, PHP workers wait on
each other and time out with cURL error 28 and 0 bytes received.
Translation: the site asked itself for a page, and nobody was free to
answer.
Tivlo serializes admin ticks, suppresses spawn_cron() while the
browser drains the queue, and takes an exclusive per-site lock so cron
cannot overlap. If it still happens, raise PHP-FPM / Local worker
count or increase HTTP Timeout. See
Troubleshooting.
How is this guide?