Deactivate & Uninstall
What Tivlo keeps (the HTML) and what it removes (settings, queue, cron).
Uninstall does not delete static HTML
Generated files under wp-content/tivlo-static/ are left in place so a
reinstall can reuse them. Delete that folder yourself if you want them
gone. Tivlo will not vacuum your snapshots on the way out — that
surprised enough people that we put it in a yellow box.
Deactivate
Go to Plugins and deactivate Tivlo Static Site (or network deactivate on a network).
Serving hooks stop. The site is live WordPress again for every visitor. Nothing “breaks” — you just went back to cooking every plate to order.
Scheduled cron events tivlo_ssg_process_queue and
tivlo_ssg_full_rebuild are cleared for that site (every site, if
you network-deactivated).
| Persists after deactivate | Removed on deactivate |
|---|---|
| Settings options | Queue cron events |
| Queue table and rows | Serving (plugin code is not loaded) |
wp-content/tivlo-static/ HTML |
Uninstall (delete the plugin)
WordPress runs uninstall.php when you Delete the plugin. That is
the Plugins screen delete, not deactivate.
Per site (and every site on a network):
- Options:
tivlo_ssg_settings,tivlo_ssg_last_build,tivlo_ssg_full_rebuild,tivlo_ssg_progress,tivlo_ssg_installed,tivlo_ssg_cache_version,tivlo_ssg_cache_bust_until - Cron:
tivlo_ssg_process_queue,tivlo_ssg_full_rebuild - Table:
{prefix}tivlo_ssg_queue
On multisite, network options tivlo_ssg_network_settings and
tivlo_ssg_network_action_lock are removed, plus leftover keys from
older remote-promo builds.
Not removed: wp-content/tivlo-static/ (all HTML).
Leave wp-content/tivlo-static/ in place. After you install again,
run a Full Rebuild if the files are stale.
How is this guide?