Kaleta 1.8 – own and move your site

Kaleta 1.8 is about owning your site: move it to a new host in a few clicks, keep an off-site copy of everything including media, and send signed events to other services.

Move a whole Kaleta site

On the old site create Import and export → Export of the whole site. Install Kaleta on the new host and choose Start from an export in the installer – it creates an empty site. Sign in, open Import and export → Import from Kaleta and upload the .zip (a large one over FTP into storage/import/).

The preview shows what the export holds. After you confirm, a database backup is made and the import runs in batches on its own. It brings pages, news, collections, components, shared classes, site parts, menus, pop-ups, redirects, the media library with its files, the site name, company details, languages and the look.

• Every row keeps its number, so links between pages, menus and components stay valid.
• Every build goes through the same checks as a save in the builder.
• User accounts, passwords, keys, tokens and the mail and backup settings are never in an export, so the new site keeps its own. Imported news belong to the administrator who imports them.
• The import works only on an empty site: a fresh install, optionally with a starter site.

This also works as a starter kit: an agency can export a prepared site and start every new project from it.

Backups include media

• Off-site copies (FTPS or S3) now copy the media/ folder to the same place as the database backups. Only new and changed files go, in the background, so even a large media library gets there bit by bit. Settings → Backups and updates shows whether the copy is complete.
• Automatic database backups now run every day something changed on the site, and at least once a week.
• The Backups tab and the guide have a short restore guide for when you lose the hosting.

Signed webhooks

The webhook addresses moved to a new tab, Settings → Webhooks.

• Calls are sent right after the page reaches the visitor, so a slow receiver never delays anyone.
• Every call is signed. X-Kaleta-Signature is sha256= HMAC-SHA256 of <X-Kaleta-Timestamp>.<body> with the signing secret shown on the tab. X-Kaleta-Event and X-Kaleta-Delivery tell the receiver what it is.
• The delivery log lists every call. A failed call is retried after 1, 5 and 30 minutes and after 2 and 12 hours, and a given-up call can be sent again with one click. Send a test call checks the connection.
• The payloads are unchanged, so existing Make, Zapier and n8n scenarios keep working.

Page export with its classes and components

Pages → Export now includes the shared classes the page uses and its components, including components inside components. Pages → Import adds the missing classes and components. A class the site already has keeps its own look, and a component imported earlier is reused.

Public API deprecated

The read-only JSON API (/api/novinky, the Public API extension) is deprecated and will be removed in Kaleta 2.0. Its responses carry a Deprecation header and System status warns while the extension is on.

Alternatives:

• /feed.json or RSS for news;
• the Claude connection (MCP) for working with the site;
• webhooks for events;
• the site export to take your content out.

Fixes

• Imports in batches (WordPress too) continue by themselves again. Before, every batch needed a click on Continue.
• The installer now notices when tables with the chosen prefix already exist.
• The site export also carries redirect types, media folders and all media details. Collection items in the trash are no longer included. The export format is now version 2 and its README is in English.

For contributors

• Core\SiteImport and Builder\PagePackage.
• The webhook queue in Core\Webhook.
• RemoteBackup::syncMedia.
• Database migration 31 (ka_webhook_deliveries).

Updating

Update from Settings → Backups and updates. After the update the webhook addresses are on the new Webhooks tab, and a signing secret is created the first time it is needed.