🕓 Versions (PRO)

All actions with blocks and tables — creation, updating, copying, and deletion — are automatically saved in the change history.
This allows you to restore previous versions of data at any time.

This is especially useful when working with nested tables — history is preserved for them as well:

⚙️ Disabling History

In the paid build versioning is enabled by default and saves all changes.
However, in some cases — for example, during development — you may want to disable it.

To disable history saving, set the system setting:

pageblocks_versioning = false

History will no longer be saved until this option is re-enabled.

In the free build it is off, and nothing is missing

The history grid is paid, so the free build ships pageblocks_versioning as false — the trait that writes snapshots is mixed into every data model, and leaving it on would pile up a history the site owner has nowhere to look at.

It is switched off by that default value and not by cutting the table out: the pb_versions table stays in place, so buying the paid build does not run into a missing schema. Turning the setting on without the paid files gets you snapshots and no grid to read them in.